Granola MCP connector

Connecting Granola to Claude takes two steps. First, open Elaichi, choose Granola, and paste in your Granola API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it can read your Granola notes and folders as you.

Yes. Once Granola is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, the Elaichi Agent and any other MCP client. You connect Granola once and every client your team uses picks it up.

With Granola connected, an AI agent can list your meeting notes, open any single note in full, and see how your notes are organized into folders, so you can ask things like what was decided in Tuesday's customer call or what a particular account has asked for across all of its meetings. It can also set up, change or remove Granola webhook endpoints, which tell another system when a new note arrives. It cannot write or edit the notes themselves.

No. The AI only sees the Granola notes and folders that the connected Granola account can already see, because every request runs through the access of the person who connected it. Elaichi can narrow that further, for example to reading notes only, but it can never widen access beyond what Granola itself allows.

Yes. One person connects Granola with their API key and shares the connection with a team in Elaichi, and nobody else ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who read which Granola note, even though they are all working through the same connection.

Yes. In Elaichi you can restrict a Granola connection action by action, for example allowing notes and folders to be read while restricting the creation, updating or deletion of Granola webhook endpoints. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.

When you offboard someone in Elaichi, their access to Granola through every connected client ends at once. If they had shared a Granola connection with a team, that connection keeps working for everyone else on the team. And if you ever want to remove Granola entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

Yes. Granola is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Granola. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Granola call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Granola: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.