Provider REST API

12 actions

Connect Claude to Granola

Read meeting notes, AI summaries and transcripts from Granola, and manage the webhooks that deliver them. Toolspoke puts 12 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 12
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Granola
Open the marketplace in your workspace, add Granola to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Granola shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Granola asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API keyRequired: Granola desktop app → Settings → Connectors → API keys → Create new key, then choose the note scopes. A personal key reads your notes and those shared with you; a workspace key (admins only) reads the workspace's public notes. Needs a Business or Enterprise plan.; grn_…

What Claude can do in Granola

12 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 9Reads
Writes: 0Writes
Destructive: 3Destructive

Reads

Fetches data and changes nothing.

list_notes
List notes this key can read, with id, title, owner and timestamps - no summary or transcript; call get_note for those. Granola only returns notes that already have a generated summary and transcript. Page with cursor while hasMore is true.
get_note
Read one note: AI summary and private notes (as text and markdown), attendees, calendar event, folders and web link. Set include to transcript to add the transcript; a very long one is refused with 413, and get_note_transcript pages it instead.
get_note_transcript
Read one note's transcript a page at a time - speaker, text and timestamps per line. Use for transcripts too long for get_note.
list_folders
List the folders this key can see. A folder id narrows list_notes and a webhook.
list_spaces
List the workspace spaces this key can see. A space id narrows list_notes.
list_audit_events
List workspace audit events from the last year, newest first. action matches an exact action or a dotted prefix (workspace returns every workspace.* event).
list_legal_holds
List legal holds on the workspace - the holds that keep notes from being deleted.
get_legal_hold
Read one legal hold - its name, description and whether it covers the whole workspace.
list_webhook_endpoints
List the webhook endpoints that receive note events, with their URL, scopes, events and folders.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

create_webhook_endpoint
Register a URL that Granola notifies about notes. Destructive rather than write: from then on, note events for the chosen scopes go to that address with no further call, which is a standing channel out of the workspace.
update_webhook_endpoint
Change a webhook endpoint - its URL, scopes, events or folders - or turn it on or off. Destructive for the same reason as creating one: pointing it at a new URL or widening its scopes sends notes somewhere new.
delete_webhook_endpoint
Delete a webhook endpoint. Events stop being delivered to it, and there is no undo.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 12 actions above are the whole of it. A call to any other name is refused before it reaches Granola rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Granola of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Granola: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Granola. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Granola's own rate limits. A call that Granola refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Granola?

12 named actions: 9 that only read and 3 that delete or permanently alter something. They include list_notes, get_note and get_note_transcript. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Granola connector need?

API key. The connector asks for api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Granola connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 12 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Granola connector not do?

The 12 actions above are the whole of it. A call to any other name is refused before it reaches Granola rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Granola of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Granola. An agent has to ask. Toolspoke does not retry, queue or back off around Granola's own rate limits. A call that Granola refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Granola's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Granola?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More productivity connectors

Browse all of them