Granola MCP

@granola what meetings did I have yesterday and what were the key takeaways from each?

Based on your Granola meeting history, you had three meetings yesterday: a 1:1 with Sarah at 10am (discussed Q1 roadmap priorities and agreed to defer the analytics dashboard), a product sync at 2pm (team decided to ship the mobile redesign in two phases), and a customer call with Acme Corp at 4pm (they requested SSO integration and committed to a pilot in March). Each meeting includes timestamped notes and action items captured during the call.

This example shows Granola's core strength: retrieving structured meeting data with context. Requires OAuth2 connection to your Granola account. The MCP can only surface meetings you've already recorded through Granola's app — it doesn't transcribe or capture new meetings on its own.

@granola find all action items assigned to me from the past two weeks and group them by project

Here are your action items from Granola meetings in the past two weeks, grouped by project: **Mobile App Redesign** — finalize icon set (from 1/13 design review), review accessibility audit (from 1/15 sprint planning). **Enterprise Sales** — send SSO implementation timeline to Acme Corp (from 1/14 customer call), schedule follow-up with TechCo (from 1/16 demo). **Internal Ops** — update team wiki with new onboarding flow (from 1/10 all-hands). Five total action items across three active projects.

Demonstrates how the MCP synthesizes action items across multiple meetings. Useful for weekly planning or standup prep. Note that action item extraction quality depends on how clearly tasks were stated during the original meeting — vague discussions may not surface structured to-dos.

@granola summarize the main concerns raised in customer meetings this month and identify any recurring themes

Across eight customer meetings in January, three recurring themes emerge: **SSO and enterprise auth** (mentioned in 5 meetings, particularly by larger accounts), **mobile app performance** (3 meetings, mostly related to offline sync), and **reporting/analytics depth** (4 meetings, with requests for custom dashboards). The SSO requests are most urgent — two customers explicitly tied it to contract renewals in Q2. Acme Corp and TechCo both need implementation timelines by end of month.

This example pairs Granola's meeting data with AI reasoning to spot patterns humans might miss. Particularly valuable for product and customer success teams tracking feedback at scale. The analysis is only as complete as your meeting coverage — if customer calls happen outside Granola, they won't appear in this synthesis.

When Granola MCP helps remote teams skip the recap call

A 6-person engineering team spread across three time zones uses Granola to capture standup and planning calls, then surfaces the notes in Switchy for the folks who couldn't attend live. The MCP pulls meeting transcripts and action items into shared context, so the PM can ask "what did we decide about the API rate limit?" without re-watching 40 minutes of video. OAuth2 auth means each person's meeting history stays private until they share a specific session. This works when your team has 3-8 recurring meetings per week and you need the notes searchable, not just archived. If you're running 20+ meetings a day, you'll want a dedicated meeting ops tool instead.

How Granola MCP turns sales calls into support context

A 4-person support team at a B2B SaaS company uses Granola to log customer calls, then queries the notes in Switchy when a ticket comes in. The support lead asks "what did the customer say about SSO during onbointing?" and the MCP surfaces the exact timestamp and quote from the sales call two weeks ago. OAuth2 keeps each rep's call history separate until they tag a call for team access. This scenario wins when you have 10-30 customer calls per month and the context gap between sales and support costs you hours of back-and-forth. If your call volume is higher, you need a CRM integration that writes structured data, not just meeting notes.

When Granola MCP speeds up retro without the manual notes

A 5-person product team runs two-week sprints and uses Granola to record their daily standups and weekly check-ins. At retro time, the PM asks Switchy "what blockers came up this sprint?" and the MCP scans the last 10 meeting transcripts for mentions of delays, dependencies, or scope changes. OAuth2 means each person controls which meetings go into the shared pool. This works when your team has consistent meeting cadence and you want to spot patterns without re-reading 20 pages of notes. If your retros are ad-hoc or you don't record standups, the MCP won't have enough signal to be useful.