Granola MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_granola_notesC | Search through Granola notes/documents by query string. Returns matching documents with their content. |
| search_granola_transcriptsB | Search through Granola meeting transcripts by query string. Returns matching transcripts with their content. |
| search_granola_eventsB | Search through Granola calendar events by query string. Returns matching events with details. |
| search_granola_panelsC | Search through Granola document panels (structured note sections) by query string. |
| get_granola_documentC | Get a specific Granola document by its ID. |
| get_granola_transcriptC | Get a specific Granola transcript by its ID. |
| list_granola_documentsB | List all Granola documents with basic metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose targeting different Granola resources (documents, transcripts, events, notes, panels) with specific actions (get, list, search). No ambiguity exists between tools, as each name precisely indicates the resource and operation, preventing misselection.
All tools follow a consistent verb_noun pattern with 'granola' as a prefix (e.g., get_granola_document, search_granola_events). The naming is uniform across all 7 tools, using snake_case and clear verbs (get, list, search), making the set predictable and readable.
With 7 tools, the count is well-scoped for a Granola document/note/transcript/event management server. Each tool earns its place by covering distinct operations (retrieval, listing, searching) across multiple resource types, avoiding bloat while providing comprehensive functionality.
The tool set offers strong coverage for retrieval and search operations across documents, transcripts, events, notes, and panels, with no dead ends. A minor gap exists in CRUD operations, as there are no tools for creating, updating, or deleting resources, but agents can still perform core read and search workflows effectively.