mcp-granola
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRANOLA_API_KEY | Yes | Your Granola API key (starts with `grn_`). Get it from Granola app > Settings > API. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesA | List Granola notes, most-recent first. Supports created_after/created_before ISO timestamps and a cursor for pagination. |
| get_noteA | Fetch a Granola note by ID. Pass include="transcript" to also return the transcript. |
| search_notesA | Client-side substring search over the list_notes response (title + summary). Pages up to 200 most recent notes then filters. |
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 3 tools
Each tool has a clearly distinct purpose: get_note retrieves a single note by ID, list_notes lists notes with filtering and pagination, and search_notes performs substring searches over note content. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_note, list_notes, search_notes) with clear, descriptive verbs. The naming is uniform and predictable, enhancing usability and reducing confusion.
With only 3 tools, the server feels thin for a note management domain, as it lacks essential CRUD operations like create, update, or delete. While the tools are well-defined, the count is borderline low for comprehensive functionality.
The tool surface is significantly incomplete for note management, covering only read and search operations. There are no tools for creating, updating, or deleting notes, which are critical for a full lifecycle, leading to potential agent failures in workflows requiring modification.