Granola MCP server for Claude, Codex and Cursor

What your AI apps can do with Granola

Search meeting notes
Read transcripts and summaries

Granola MCP tools

9 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`query_granola_meetings`	Ask Granola a question about your meetings and get an answer drawn from your notes
`list_meetings`	List accessible notes with ID, title, date and attendees (folder filtering needs a paid plan)
`get_meetings`	Read note content, including private notes and summaries
`get_meeting_transcript`	Return the raw transcript for a meeting ID (paid plans only)
`get_meeting_attachment`	Show screenshots of screens shared during a meeting, such as slides, charts or code
`list_meeting_folders`	List folders you can access, with note counts (paid plans only)
`get_account_info`	Return the connected account's email, active workspace and joined workspaces
`switch_workspace`	Change the active Granola workspace (only offered if you belong to more than one)
`sign_out`	Disconnect the AI tool from your Granola account

Suggested access for each AI app

The documentation this list comes from doesn't mark Granola's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Granola connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Granola to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Granola tool, give Cursor only the read tools, or keep Granola away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Granola MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Granola in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Granola endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http granola 'https://mcp.granola.ai/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "granola": {
      "url": "https://mcp.granola.ai/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Granola MCP documentation for what your client needs.

Before you connect

A Granola account. Sign-in uses your Granola permissions.

Server details

Detail	Value
Publisher	Granola
Endpoint	`https://mcp.granola.ai/mcp`
Authentication	Browser sign-in
Categories	Communication, Productivity
Tool list	9 tools, observed 29 October 2026 (docs)

Granola MCP documentation