Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Granola MCP" |
| 4 | description: "Public behavior and schema guidance for the official Granola MCP server." |
| 5 | category: "toolkits-and-providers" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-14T00:00:00Z" |
| 8 | tags: |
| 9 | - "granola" |
| 10 | - "mcp" |
| 11 | - "schemas" |
| 12 | --- |
| 13 | # Granola MCP |
| 14 | |
| 15 | ## Composio mirrors Granola's official MCP server |
| 16 | |
| 17 | The Granola MCP toolkit uses Granola's official MCP server. Tool names, descriptions, input definitions, and response metadata are limited to what that upstream server exposes. |
| 18 | |
| 19 | - If Granola supplies only a tool name and description, that is the metadata Composio can expose. |
| 20 | - If Granola does not declare a response/output schema, Composio cannot invent one, so an empty output schema is not by itself evidence of a stale Composio catalog. |
| 21 | - If a customer reports a mismatch, ask for the exact tool name and missing field. Compare it with the current official Granola MCP server behavior before attributing it to the Composio catalog. |
| 22 | - Escalate when the official server currently exposes a tool or schema field but the same item is absent from Composio. |