granola

Granola MCP Server provides an MCP-compatible interface for accessing Granola.meeting data via Claude Desktop and other MCP clients. It exposes tools to search meetings, retrieve meeting content in Markdown, and manage/work with workspaces and folders through a direct Granola API bridge. After configuring Claude Desktop or your MCP client to point at the server, you can issue natural-language commands like 'Search for meetings about quarterly planning', 'Get the content from yesterday's standup', or 'List all my workspaces'. The server translates these requests into Granola API calls, converts ProseMirror content to readable Markdown, and caches results for five minutes to improve performance and reduce API load.

Tools surfaced by the server include: search_meetings (by title/content), get_meeting_details (metadata), get_meeting_content (full markdown content), list_workspaces, list_folders, filter_by_workspace, and filter_by_folder. These provide a comprehensive set of read operations for meetings, documents, and organizational structure, enabling you to work with Granola data inside your MCP client without leaving the chat or assistant interface.

Prerequisites:\n- Node.js 18+ (LTS) installed on your system.\n- npm (comes with Node.js) installed.\n- Access to a machine where you can run the MCP server and configure Claude Desktop or your MCP client.\n\nInstallation steps:\n1) Clone the repository:\n git clone https://github.com/EoinFalconer/granola-mcp-server.git\n2) Navigate into the project:\n cd granola-mcp-server\n3) Install dependencies:\n npm install\n4) Build the server (if the project uses a build step):\n npm run build\n5) Run the server (example):\n node dist/index.js # or the appropriate entry point per the project setup\n6) Configure your MCP client to point to the server endpoint as described in the Configuration section.

Notes and tips:\n- This server uses Granola credentials from your local Granola installation. Ensure you are logged in to Granola on the machine where the server runs. The server reads credentials from ~/Library/Application Support/Granola/supabase.json (macOS).\n- Because this is built against undocumented APIs, behavior may change and usage could violate Granola’s Terms of Service. Use at your own risk.\n- The server implements an in-memory cache with a 5-minute TTL to balance freshness with performance.\n- If you encounter 'Failed to get access token' errors, verify that Granola is installed and that you are logged in on the same machine where the server runs.\n- Ensure Claude Desktop or your MCP client’s config points to the correct index.js (or built entry point) path.\n- If you modify the server, re-run the build (npm run build) and restart the MCP client for changes to take effect.