Granola MCP server: meeting notes for every agent

Meeting context is useful when it answers a decision question. Ask which launch date was approved in last week’s review and request the source note URL. A list of meeting titles is only a discovery step; the agent should fetch the relevant meeting before saying what was decided.

Use get_account_info to check the active workspace and effective note-access scopes. Folder listings help narrow the search without opening every note. query_granola_meetings can return cited answers, but citations still need to support the statement the agent carries into another app.

A transcript request is broader than a summary request. It can expose side conversations or details that do not belong in the final task. For a follow-up assistant, meeting summaries may be enough, while transcript access stays hidden.

Granola MCP server: official vs AIPx

The Granola MCP help page describes vendor availability and plan limits. The community repository is a different implementation, not an official replacement with identical access. AIPx reuses the official tools and adds another service handling request data.

For one client that only needs notes, connect directly to Granola. AIPx is useful when notes inform Linear tickets, Notion pages or Things 3 tasks, each with its own write rules.

Connect Granola to Claude

Choose Granola and complete its official OAuth authorization. Check the active workspace after connection; access is tied to the authorized account.

1. Open the AIPx dashboard, choose Granola under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Granola; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Granola

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Granola is the only service you need.

Granola MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Authorize using /mcp, then list last week’s Granola meetings and check the active workspace. Fetch notes before stating a decision. Claude Code MCP setup explains server registration and sign-in.

Granola MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

After browser sign-in, let Cursor read the incident meeting summary needed for the code task. Keep transcripts hidden if summary context is sufficient. Cursor MCP setup covers the server configuration.

Granola MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Granola credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

Where ChatGPT supports custom MCP, add this endpoint and request a dated Granola meeting summary. Transcript eligibility still depends on Granola’s plan. The ChatGPT MCP guide explains separate client and workspace requirements.

Scope Granola per agent: read-only by default

For a meeting follow-up assistant, allow meeting lists, details and queries; hide transcripts unless exact wording matters. This is a privacy recommendation within an already read-oriented tool surface. The general product default for read tools is Allow, but a read can still reveal confidential information.

Keep MCP tool rules tied to the agent’s job. A coding agent may only need one incident meeting, while a personal assistant should not inherit the same workspace context merely because both use Claude.

Granola MCP in Claude Code

Use the Claude Code command below and verify the account before retrieving notes. For another meeting system, Fireflies offers its own transcript tools. Gmail, Apple Calendar and Google Calendar can help identify the meeting, but connecting them does not expand Granola’s note permissions.

Granola note history and transcript limits

Granola Basic limits available notes to the last 30 days, while transcript access requires an eligible paid Granola tier. Enterprise administrators can disable MCP. AIPx Free does not bypass any of those vendor conditions.

Workspace scopes also matter: do not assume the connection exposes every shared note or every meeting in an organization. If a requested meeting is missing, check the date range, active workspace and provider access before broadening the request. A missing transcript is not proof the meeting had no relevant discussion.

Browse all MCP integrations to choose another connection for this agent.

The Granola connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.