Connector · Docs and files
A Granola teammate in Slack, reading your notes over Granola's MCP server.
Chickpea gives a channel a named AI teammate that holds its own Granola connection. It signs in through the browser and calls Granola's MCP server, so there is no client to configure and no key to paste. In Slack, ask it what yesterday's call decided or which meeting first raised a topic, and it answers in the thread.
What people ask it.
The teammate is @revops, in #growth. Pick a scenario to watch it play.
What a call decided Read only
@revops what did we decide about pricing on the Northwind call yesterday
@revops did the Acme renewal call land on a start date, and what was it
Reads never need confirmation. The teammate searches the notes on the connected account, then answers with the meeting it read and the date. It sees the summarized notes Granola wrote, and on a paid plan it can open the raw transcript for an exact quote.
Action items and owners Read only
@revops list the action items from this morning’s roadmap review, with owners
@revops what did I agree to do on the Acme call
Granola says the server is for finding topics in past meetings and pulling decisions and action items out of the notes. The teammate does that work in the thread. Nothing it finds is written back to Granola.
Find the meeting Read only
@revops which call first raised the annual-plan discount
@revops find every meeting this month where someone asked about SSO
A long answer comes back as a table in the thread, with the meeting, the date, and who was on it. Search reaches the notes in the active Granola workspace of the connected account, and Granola does not combine notes across workspaces.
Catch someone up Read only
@revops summarize the Northwind call for Marco, he missed it
@revops three bullets from the QBR I can paste into the thread
The summary is written in Slack, in the thread where you asked. The teammate cannot edit a note, retitle one, or add anything to Granola, because every tool Granola publishes on this server reads.
On a schedule Applies at once
@revops every Friday at 4pm Eastern, list the action items from this week’s customer calls
@revops every Monday at 9am Pacific, post what we agreed in last week’s pipeline reviews
A schedule saves on the spot. It needs an explicit time zone, and it runs under the Granola connection of the person who asked, so it reads their meetings and nobody else’s. Disconnect that account and the schedule stops with a named reason rather than running.
Connect it
Five steps, from Admin or from Slack.
You sign in through a page Chickpea serves, never in Slack. The link the teammate posts is good for one action, for one teammate, for 24 hours.
- In Chickpea Admin, open the teammate, then Connections, find Granola, and choose Connect. Or ask in Slack,
@revops connect Granola, and follow the link it posts. - Choose Personal, not Team. Granola MCP signs in as one Granola user, so a team account would put that one person’s meeting history in front of everyone who can use the teammate. Personal means your sign-in answers your requests and nobody else’s.
- Choose Continue to sign in. Granola opens in the browser and asks you to approve the account whose notes the teammate should reach. There is no key to paste and no config file to edit.
- Chickpea connects to mcp.granola.ai/mcp and records the tools the server answered with. The teammate is handed that list, and it can later be narrowed to fewer tools but never widened to more.
- Ask something.
@revops what did we decide on the Northwind callis a good first question, because every tool on this server reads and none of them can change a note.
A connection belongs to one teammate. Giving a second teammate Granola means a second sign-in with its own consent, so the support teammate never inherits the meetings the growth teammate can reach. Switch workspaces in the Granola app and the connection follows the active one.
There is no built-in Chickpea skill for Granola, and none is needed. The tools arrive from Granola’s MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Granola publishes six: query_granola_meetings, list_meetings, get_meetings and get_account_info on every plan, then get_meeting_transcript and list_meeting_folders on paid plans only. Granola documents the server, its tools, and the plan each one needs.
GranolaBeside Granola
What the same teammate usually holds too.
Each is its own connection, granted to the teammate alone. All 37 connectors.
The action items from a call become tasks with owners and dates
LinearA bug someone raised on a call gets filed with the quote from the transcript
HubSpotWhat the customer actually said goes onto the deal, not a paraphrase
Google CalendarFind the meeting on the calendar, then read what came out of it
Questions people ask
Does Granola have an MCP?
Yes. Granola runs a first-party MCP server at mcp.granola.ai/mcp over streamable HTTP, with browser OAuth, and documents it for Claude, ChatGPT, and Cursor. Chickpea connects to that same server, so a teammate in Slack uses it without any of those clients installed.
How do I connect Granola MCP?
For a desktop client, follow Granola’s own docs, since each client keeps its own connector list. For Slack there is nothing to configure. Open the teammate in Chickpea Admin, choose Granola, choose Personal, and sign in. Or ask "@revops connect Granola" in the channel and follow the link it posts.
Whose meetings can it see?
The connected account’s, inside whichever Granola workspace that account has active. This is the reason to choose a personal connection. Anyone who can use the teammate can ask it a question, so a shared team sign-in would make one person’s meeting history readable by the whole channel. A personal connection is used only for the member who owns it, and someone else’s is not in the room.
Does it use Granola’s MCP server or an API?
The MCP server. Granola is a vendor MCP lane here: the deployment connects to mcp.granola.ai/mcp over streamable HTTP and signs in with OAuth, asking for the `mcp` scope. Granola does also publish a REST API on its Business and Enterprise plans, and this connector does not touch it. There is no API key anywhere in it.
Can it write to Granola?
No. Granola publishes six tools on this server and every one of them reads: a search, two ways to list, two ways to fetch, and an account check. Nothing renames a note, edits a summary, or files anything. The gate on the Chickpea side holds independently of that. During a Slack turn Chickpea refuses any MCP tool whose name does not start with an unambiguous read verb unless your message names that action, so thread history and retrieved content cannot authorize one on their own.
Which Granola plan includes MCP?
All of them, including Basic. Granola limits what each one reaches. Basic is personal notes from the last 30 days, and Granola marks the folder and transcript tools as paid plans only. Business adds public workspace notes. On Enterprise, workspace admins choose which scopes members get, and a member with neither scope enabled cannot use Granola MCP at all.
Can it read the transcript, or only the summary?
Both, on a paid plan. `get_meetings` returns the notes and the summarized content, and `get_meeting_transcript` returns the raw transcript, which is what you want when the answer turns on someone’s exact words. Granola lists that tool as paid plans only, so on Basic the teammate works from the notes.
Do I still need Granola’s own Slack integration?
They do different jobs, and most teams want both. Granola’s Slack app pushes a note out: you share one to a channel and it posts a link with a summary, and a folder can post every new note automatically. It shares to channels only and needs a Google Workspace or Microsoft 365 account. A Chickpea teammate goes the other way. It posts nothing unprompted and answers when asked, across your whole meeting history rather than one note.
Can I use this from Claude or ChatGPT instead?
Yes, and Granola documents both. Those put the server in one person’s client, on one machine. A teammate puts it in a channel, with a stored connection, saved instructions, schedules, and every answer visible where it was asked for, beside the other accounts that teammate holds. Teams often run both.
Where does the OAuth token live?
On your deployment, outside the teammate record. It never enters the model’s context, the tool arguments the model writes, or Slack. The model picks a connection by id and the credential goes in at the last step on the way out. Disconnect the account and the stored secret is removed, and any schedule that depended on it stops.
Try it
Give a channel a Granola teammate.
One deploy into your own Cloudflare account, connect Slack, sign in to Granola, ask. Apache 2.0, no seats, no metering.
Or run it on Node. The setup guide covers both.
Last checked
Facts on this page were checked against the product and Granola's own pages on September 17, 2026. This page is also available as markdown at /connectors/granola.md.