---
title: "Granola MCP in Slack: ask an AI teammate what a meeting decided | Chickpea"
description: "Use Granola's MCP server from Slack. Give a channel an AI teammate connected to Granola, then ask what a call decided and who owns what. Open source."
canonical: https://chickpea.co/connectors/granola
keyword: "Granola MCP in Slack"
verified: 2026-09-17
---

# 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.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/granola; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Granola** (Granola Labs, Inc., https://www.granola.ai): Search meeting notes and transcripts, browse folders, and extract decisions and action items. Category: Docs and files. Lane: Vendor MCP server. Sign in: OAuth.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @revops, published to #growth.

### What a call decided
- @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
- @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
- @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
- @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
- @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.

### Example conversations

**What did we decide**
> **Sofia:** @revops what did we decide about pricing on the Northwind call yesterday?
> **@revops:** From Northwind QBR, Tue Sep 16, 2:00 PM. You agreed on annual billing at 12% off list and took the monthly option off the table for this renewal. Priya said legal needs the new terms before anyone signs.

**Action items**
> **Marco:** @revops list the action items from this morning’s roadmap review, with owners.
> **@revops:** Five action items in Roadmap review, 9:30 AM today. Four have an owner in the notes and one does not.

**Find the meeting**
> **Dana:** @revops which call first raised the annual-plan discount?
> **@revops:** Four meetings mention it. The first is Acme discovery on Aug 21, where Acme asked for annual pricing before we had one.
>
> | Meeting | Date | Raised by | What they wanted |
> |---|---|---|---|
> | Acme discovery | Aug 21 | Acme | Annual pricing, any discount |
> | Pricing working session | Aug 28 | Priya | 10% for annual prepay |
> | Northwind renewal | Sep 9 | Northwind | 15%, matched to a competitor |
> | Northwind QBR | Sep 16 | Marco | Settled at 12% |

**Every Friday**
> **Priya:** @revops every Friday at 4pm Eastern, list the action items from this week’s customer calls here.
> **@revops:** Saved. Every Friday at 4:00 PM Eastern I’ll read the week’s customer calls and post the action items with owners in #growth. First run is Fri Sep 18. It runs on your Granola connection, so it reads your meetings and nobody else’s.

## Connect Granola
1. 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.
2. 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.
3. 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.
4. Chickpea connects to [mcp.granola.ai/mcp](https://docs.granola.ai/help-center/sharing/integrations/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.
5. Ask something. `@revops what did we decide on the Northwind call` is 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.

## What the teammate is handed with Granola
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: https://docs.granola.ai/help-center/sharing/integrations/mcp

## Beside Granola
- **Asana:** The action items from a call become tasks with owners and dates
- **Linear:** A bug someone raised on a call gets filed with the quote from the transcript
- **HubSpot:** What the customer actually said goes onto the deal, not a paraphrase
- **Google Calendar:** Find the meeting on the calendar, then read what came out of it
- All 37 connectors: https://chickpea.co/connectors

## 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.

## Sources
- [Chickpea docs: connector catalog, the Granola preset, its lane and OAuth scope](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the read-verb gate](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, OAuth presets and the Slack link](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what each run rechecks](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Granola preset (server URL, transport, OAuth scope)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Chickpea source: an MCP connection exposes approved tools that are still discovered](https://github.com/pejmanjohn/chickpea/blob/main/src/config/types.ts)
- [Granola docs: the MCP server, its tools, plans, and workspace rule](https://docs.granola.ai/help-center/sharing/integrations/mcp)
- [Granola docs: the Slack integration](https://docs.granola.ai/help-center/sharing/integrations/slack)
- [Granola docs: the Granola API, on Business and Enterprise plans](https://docs.granola.ai/introduction)
- [Granola: the MCP connector for Claude, ChatGPT, and Cursor](https://www.granola.ai/blog/granola-mcp)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co