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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_meetingsC | Search meetings by title, content, or participants |
| get_meeting_detailsB | Get detailed information about a specific meeting |
| get_meeting_contentC | Get the full notes/content for a meeting in Markdown format |
| list_workspacesB | List all available workspaces |
| list_foldersC | List all document folders |
| filter_by_workspaceC | Filter meetings by workspace |
| filter_by_folderC | Filter meetings by folder |
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
Each tool has a clearly distinct purpose with no ambiguity. Filter_by_folder and filter_by_workspace target different filtering criteria, while get_meeting_content and get_meeting_details provide different levels of meeting information. List_folders and list_workspaces are distinct listing operations, and search_meetings offers a broader search capability that doesn't overlap with the filters.
All tool names follow a consistent verb_noun pattern using snake_case. The verbs (filter_by, get, list, search) are applied predictably to nouns (folder, workspace, meeting_content, meeting_details, folders, workspaces, meetings), making the set highly readable and uniform.
With 7 tools, the count is well-scoped for a meetings management server. Each tool earns its place by covering essential operations like filtering, retrieving details, listing resources, and searching, without being overly sparse or bloated.
The tool set provides strong coverage for core meeting operations, including retrieval, listing, filtering, and searching. A minor gap exists in CRUD lifecycle coverage, as there are no tools for creating, updating, or deleting meetings, but agents can likely work around this for read-only use cases.