Granola

Get the email, active workspace, and effective note-access scopes for the Granola account currently connected to this MCP session.

When to use:

• User asks 'who am I signed in as?', 'which Granola account is this?', or 'what's my email?'
• User suspects they connected the wrong Granola account
• Meeting results may be incomplete or empty because of the user's Granola plan or workspace MCP access controls
• Before performing actions, to confirm identity if the user references a specific account

When scope-based access controls are active, mcp_note_access.scopes contains the note categories this connection can search:

• personal: notes the connected user owns, notes shared directly with them, and notes accessible through private folders
• public: notes accessible through workspace-visible Team Space folders
• Both scopes means both categories can be searched. These scopes describe access, not who captured or participated in a meeting.

Read a saved, agent-oriented summary of a specific Granola meeting. Returns meeting_id and detailed_summary. It provides more context than the human-readable summary, including participant details, a longer summary, and references where available. Does not include the transcript. Use this when you know the meeting ID and need deeper context to answer a question. Returns unavailable when no detailed summary has been generated; does not generate one. Use get_meetings for the standard notes or get_meeting_transcript for verbatim wording.

Get the full transcript for a specific Granola meeting by ID. Returns only the verbatim transcript content, not summaries or notes. Transcript blocks separate audio source (Microphone/System audio) from speaker identity. Participant attribution and user-confirmed names are preserved. Desktop diarization is omitted; mobile/imported transcripts can retain Speaker A/B/... labels for unnamed voices. Recording context identifies the document owner as the recorder for native recordings, not as the speaker. Missing recorder data stays unknown; the current viewer is not substituted. Channels and room labels may include multiple people. Older preformatted transcripts keep their original labels. Use this when the user needs exact quotes, specific wording, or wants to review what was literally said in a meeting. For summarized content or action items, use query_granola_meetings or list_meetings/get_meetings instead.

Get detailed meeting information for one or more Granola meetings by ID. Returns private notes, AI-generated summary, attendees, metadata, and note URLs. Use this when you already have specific meeting IDs (e.g. from list_meetings results). For open-ended questions about meeting content, use query_granola_meetings instead.

Look up one person the user has met, by name or email. Returns their name, job title, company, how many meetings they share with the user, and when they first and last met.

When to use:

• User asks who someone is, e.g. 'who is Jane Chen?'
• User asks when they last met someone, or how often they meet
• User asks whether someone is a colleague or external
• Before a meeting, to recall the user's relationship with an attendee

When NOT to use:

• User asks what was discussed with someone: use query_granola_meetings
• User wants the meetings themselves: use list_meetings
• User asks about someone they have never met. This covers the user's own meeting history only, not a directory of everyone at their company.

If several people match a name, this returns the candidates with their email addresses; call it again with one of those addresses. Facts come from a periodically rebuilt profile of the user's meeting history; context_updated_at says when it was last built.

List the user's Granola meeting folders. Returns folder ID, title, description, and note count including nested folders.

When to use:

• User asks about their folders or wants to browse meetings by folder
• User wants to narrow down meeting searches to a specific folder

Use the returned folder IDs with list_meetings (folder_id parameter) to list meetings within a specific folder.

List the user's Granola meeting notes within a time range. Returns meeting titles, metadata, and note URLs.

IMPORTANT: For short-term questions about recent meeting details, prefer using query_granola_meetings instead.

When to use:

• User asks to list their meetings
• User asks about action items, decisions, or summaries from meetings over a longer or specific date range
• User asks about content from their meeting transcripts
• User references 'Granola notes' or 'meeting notes' or 'transcripts'

When NOT to use:

• User is asking about upcoming calendar events or scheduling
• User wants to create/modify calendar invites

Filtering:

• Omit workspace_only and involvement to return every meeting the user is allowed to access
• For 'my meetings' or meetings the user was involved in, set both involvement conditions to true; true conditions combine using OR
• Set captured_by_me to true for meetings whose Granola notes the user captured, or false to exclude them
• Set listed_as_participant to true for meetings where the user is a known participant, or false to exclude them
• False involvement conditions are exclusions and combine with the positive conditions using AND; omit a condition to ignore it
• For Team Space or public workspace meetings, set workspace_only to true
• workspace_only and involvement combine using AND

Use get_meetings to retrieve detailed meeting content after identifying relevant meetings. Use list_meeting_folders to discover folder IDs, then pass a folder_id to list meetings within a specific folder.

Query Granola about the user's meetings using natural language. Returns a tailored response with inline citation links in markdown (e.g. [[1]](url)) that reference source meeting notes.

IMPORTANT: The response includes numbered citation links to specific Granola meeting notes. These citations MUST be preserved in your response to the user — they provide transparency and allow the user to verify information by clicking through to the original notes.

For optional deeper reads, extract the meeting ID from the citation URL: https://notes.granola.ai/d/<meeting_id>. Pass that ID to get_meetings (meeting_ids) or get_meeting_transcript (meeting_id), where allowed.

When to use:

• User asks about what was discussed, decided, or action-items from meetings
• User asks about follow-ups, todos, or commitments from recent meetings
• User references 'Granola notes' or 'meeting notes'

When NOT to use:

• User is asking about calendar scheduling or upcoming events
• User explicitly asks for a specific meeting by ID (use get_meetings instead)

Prioritize using query_granola_meetings over list_meetings/get_meetings for open-ended or natural language queries about meeting content.

Remove a Granola note from a folder. Use list_meeting_folders to find the folder ID and list_meetings to find the note ID. Removing the note may revoke folder-derived access for other people.

Find the user's meetings that mention specific words, using BM25 keyword ranking. Returns metadata only — title, date, participants and note headings — ordered by relevance, which favours recent meetings.

When to use:

• User names an exact term, project, product or acronym and wants the meetings that mention it
• User wants a list of matching meetings rather than an answer
• You need meeting ids to pass to another tool

When NOT to use:

• User asks an open-ended question about what was discussed or decided: use query_granola_meetings
• User wants the full notes of a meeting you already identified: use get_meetings
• User wants to browse by date, folder or attendance rather than by word: use list_meetings

Matching is literal, so pass the words as the user said them plus obvious synonyms. A term the user never wrote in a note will not match.