What MCP can access
MCP connects as you and returns notes from your active workspace (the workspace currently selected in the Granola app).- If you belong to multiple workspaces, switch workspaces in Granola or ask your AI tool to switch for you. MCP only searches one workspace at a time.
- Notes created in another workspace aren’t included, even if they’ve been shared with you in your active workspace.
Which scopes and tools you get depends on your plan:
If you upgrade from Basic, the extra tools and higher rate limits take effect on your next query.
Setup guide
You’ll need a Granola account with meeting notes and an AI tool that supports MCP, such as Claude or ChatGPT.How to connect
Your AI tool and Granola don’t need to use the same email address. During sign-in, authenticate with the Granola account whose notes you want to access.Claude
Claude
- Open and sign in to Claude.
- Go to Settings > Connectors and search for Granola.
- Click Connect and sign in to your Granola account.
- Make sure the Granola connector is turned on in your chat.
ChatGPT
ChatGPT
- Open and sign in to ChatGPT.
- Go to Settings, search for Granola, and connect your account.
- Mention
@Granolaor ask ChatGPT about your meetings.
Claude Code
Claude Code
- Run
claudein your terminal. - Add the Granola MCP server:
- Open a new terminal tab and run
claudeagain. - Run
/mcp, choose granola, and select Authenticate. - Ask Claude about your meetings.
Cursor
Cursor
- Open Granola in the Cursor Marketplace, or search for Granola under Marketplace in Cursor.
- Click Install and sign in to your Granola account when prompted.
- Ask Cursor about your meetings.
Antigravity
Antigravity
- Open Antigravity and go to Customizations > Marketplace.
- Search for Granola and install the plugin.
- Sign in to your Granola account when prompted.
- Ask Antigravity about your meetings.
Perplexity
Perplexity
- Open Granola in Perplexity Connectors, or search for Granola in Perplexity’s connector settings.
- Connect and sign in to your Granola account.
- Ask Perplexity about your meetings.
Other AI tools, including your own
Other AI tools, including your own
Add
https://mcp.granola.ai/mcp as a custom MCP connection.Your AI tool needs to support:- Streamable HTTP transport from the MCP specification.
- OAuth 2.0 and metadata discovery, including opening a browser window so you can sign in to Granola and receive a bearer token.
Tools and descriptions
Your AI tool picks the right tools automatically based on what you ask, so you don’t need to name them. Which tools appear depends on your plan, your workspace’s admin controls, and the AI tool you use.Find and read meetings
Organize and edit notes
Available on paid plans, exceptlist_templates. Your AI tool should only run these when you ask.
Account and profile
Troubleshooting and FAQ
MCP can't find my notes, or a specific note
MCP can't find my notes, or a specific note
- Ask your AI tool: “Which Granola account am I signed in with?” It will return the email address and active workspace connected to MCP.
- Right email, wrong workspace: Switch workspaces in the Granola desktop app (click your workspace name in the bottom-left corner), or ask your AI tool to “Switch my Granola workspace to [workspace name].”
- Wrong email: Check which email your Granola account uses in Settings (⌘ + , on macOS, Ctrl + , on Windows) under your profile picture in the top left, then reconnect MCP with that email. If you use Claude, follow Signed into Claude with the wrong account below.
- Right account and workspace: Check that the note falls within your plan and workspace access scopes (for example, the 30-day window on Basic or your Enterprise admin’s scope settings).
MCP tools aren't working
MCP tools aren't working
If your AI tool reports that it can’t reach Granola or run MCP tools, disconnect Granola in your AI tool’s settings and sign in again to refresh the connection.
Claude shows "No tools available"
Claude shows "No tools available"
Reset the Granola connector in Claude to restore the tools:
- Open Claude connector settings in a browser (even if you use the Claude desktop app).
- Select Granola, open the three-dot menu in the top right, and choose Disconnect.
- Without refreshing or leaving the page, click Connect and sign in again.
Signed into Claude with the wrong account
Signed into Claude with the wrong account
A normal disconnect and reconnect keeps your existing Granola browser session active, so Claude skips the login screen. To switch accounts:
- Ask Claude to log out of Granola.
- Open the mcp-auth.granola.ai/api/logout link it returns to clear your Granola session.
- Reconnect Granola in Claude and sign in with the email address for your Granola account.
Rate limits
Rate limits
Each tool has its own rate limit, which depends on your plan. These are the standard limits; some accounts have lower ones, and limits may change over time.
- Paid plans: most tools allow 5 requests per second.
query_granola_meetingsallows 50 an hour, and tools that edit notes have lower limits, such as 10 summaries an hour. - Basic (Free):
query_granola_meetingsallows 15 requests an hour,get_meetings,get_meeting_attachment, andlist_templatesallow 10 an hour each, and other tools allow up to 2 a second.
Do I need a client ID or client secret?
Do I need a client ID or client secret?
Not for a standard browser OAuth connection. Granola MCP uses Dynamic Client Registration (DCR), so your AI tool registers itself automatically.If a third-party platform (such as Composio) shows client ID and client secret fields, leave them blank. For Enterprise-Managed Authorization, see Client ID at resource under Set up with your identity provider.
Enterprise admin controls
Enterprise admins choose what AI tools can read and change through MCP in Settings > Workspace > General > Apps & connectors > MCP access. All Enterprise workspace members can view these settings, but only admins can change them.Note access
Turn on Personal notes, Public notes, both, or neither. If neither is enabled, workspace members have no MCP access. These note access controls apply to non-admin workspace members; Enterprise admins can always access both personal and public notes through MCP.Permissions
Permissions apply to everyone in the workspace, including admins. All permissions are on by default.
To make MCP read-only, turn off Organise notes, Edit notes, and Send feedback.
Enterprise-Managed Authorization
Enterprise-Managed Authorization (EMA) lets your company approve Granola MCP once for everyone, so workspace members don’t have to sign in individually through a browser. When they open their AI tool with their work account, Granola is already connected. EMA works by having a trusted identity source sign an identity assertion (an ID-JAG) for each user:- Claude auto-connect (beta): Claude signs the assertion for your Claude organization. No identity provider setup required.
- Your identity provider: Your IdP (such as Okta) signs the assertion.
Before you begin
EMA requires:- A Granola Enterprise workspace with SSO enabled (SSO requires Enterprise with at least 50 seats: 50 active workspace members, or a subscription committing to at least 50 seats).
- Admin access to Granola and to either Claude or your IdP.
Set up Claude auto-connect (beta)
Claude auto-connect (also called Claude-issued enterprise-managed auth) connects workspace members to Granola in Claude automatically, without a sign-in or consent screen. Each person acts as themselves in Granola with their normal note access. You’ll need a Claude Team or Enterprise plan, and each person’s Claude email must match their Granola email. Workspaces without Enterprise and SSO should use the standard flow in How to connect. You register Claude’s issuer URL yourself in Granola, under Enterprise-managed authorization in Settings > Workspace > General > Apps & connectors > MCP access. Only Enterprise admins can see this section. Your workspace’s domain must be verified for SSO.- In Granola, configure the note access you want to allow under Enterprise admin controls.
- In Claude, go to Organization settings > Connectors and select Granola.
- Next to Managed authorization, click Set up.
- In the Connect step, set Identity source to Claude-issued.
- Copy the Issuer URL shown in Claude (this is unique to your Claude organization).
- In Granola, open MCP access. Under Enterprise-managed authorization, click Manage next to Claude managed access.
- In the page that opens, paste the issuer URL and save it.
- Back in Claude, leave Tenant ID (optional) blank.
- Click Run test and confirm every check passes, with
https://mcp-auth.granola.aishown as the authorization server. - Click Enable and continue, then pick which roles should receive the connector (all roles are selected by default).
Things to keep in mind
- Identity checks: Claude confirms that someone is an active member of your Claude organization with that email address, and sends Granola their email and an opaque ID. It doesn’t verify an IdP sign-in or MFA.
- Offboarding: Removing someone from your Claude organization stops future connections, but remove them from Granola too so existing tokens don’t stay valid until expiry. If you use SCIM directory sync, Claude removes users when they are deleted from your directory, not when they are only suspended.
- Reassigned emails: Remove a former employee’s Granola account before reusing their email address for someone else, or the new hire will connect to the old account.
- Turning it off: Open the connector’s Managed authorization settings in Claude and click Disable to return to individual sign-in. To stop trusting Claude completely, remove the issuer URL with Manage next to Claude managed access in Granola.
Troubleshooting
Run test stops at the first failing check:
If Claude warns that Granola’s authorization server address changed, re-run the test, verify the address is
https://mcp-auth.granola.ai, and confirm it.
Set up with your identity provider
Your IdP and MCP client both need to support EMA. Granola has tested this with Claude and Okta.- In Granola, configure the note access you want to allow under Enterprise admin controls.
- In your IdP, add or open Granola and enable its managed authorization or resource server capability.
- Create a managed resource connection from your MCP client to Granola using these values (field names vary by IdP, and some values may be filled in automatically):
- Assign the right users or groups to both Granola and the MCP client, then activate the connection.
Building your own MCP client
To connect a custom client with EMA, implement the MCP EMA specification, obtain an ID-JAG from your IdP, and publish a public HTTPS metadata document declaringprivate_key_jwt and a jwks_uri. Discover supported endpoints and capabilities from Granola’s OAuth metadata, and use the advertised issuer as the audience for your client assertion.
Example: Claude and Okta
Granola has tested EMA with Claude and Okta Cross App Access (XAA):- In Okta, add the Granola integration.
- Open the Resource server tab and enable Cross App Access (XAA).
- Follow Okta’s guide to configure a resource server connector between Claude and Granola.
- Enter
https://claude.ai/oauth/mcp-oauth-client-metadataas the Client ID at resource.

