F
licenseA
qualityD
maintenanceProvides access to Granola notes, meeting transcripts, calendar events, and document panels through the Granola API, enabling search and retrieval of meeting-related content.
7
5
-
Granola MCP Server
by EoinFalconer
Related Servers
Alternatives to Granola MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceIntegrates local Granola.ai meeting intelligence with Claude Desktop to enable searching and analyzing meeting transcripts, notes, and summaries. Users can perform natural language queries to retrieve meeting details, analyze participant patterns, and access full speaker-identified conversations.5MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides AI agents access to Granola meeting notes. It enables searching notes, retrieving full content with transcripts, and paginating through meeting history.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables access to Granola meeting notes through OAuth authentication, allowing users to search, retrieve, and summarize meeting transcripts and documents.MIT
- FlicenseNot gradedqualityFmaintenanceMCP server for Granola that exposes meeting notes, AI summaries, and transcripts to Claude.-
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes local Granola meeting notes, summaries, and transcripts to AI assistants via SQLite-backed search and retrieval.MIT
TDQS
A3.5/5.0
Scored across 7 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues