Notion MCP: Connect Claude to Your Notion Workspace

Notion MCP is Notion’s official, hosted Model Context Protocol server at https://mcp.notion.com/mcp. It lets Claude search your workspace semantically, read and edit pages as Markdown, and work with databases, all through OAuth so Claude sees exactly what you can see in Notion. Notion built it to return only the most relevant context, which keeps token use lower than the older API-shaped tools.

Who it is for

Teams whose specs, meeting notes, roadmaps and runbooks live in Notion and who want Claude to read or update them without copy and paste.

Install in Claude Code

claude mcp add --transport http notion https://mcp.notion.com/mcp

Then open Claude Code, run /mcp and complete the OAuth flow. Notion is also listed in Anthropic’s official plugin marketplace as notion@claude-plugins-official; see the plugins guide.

Use cases

• Spec to code: “Read the ‘Billing v2’ spec in Notion and draft an implementation plan.”
• Docs upkeep: update a runbook page after Claude changes a deploy script.
• Meeting follow-up: turn notes into tasks in a Notion database.
• Research: search across the workspace for prior decisions before starting work.

Pros

• Official and hosted: no local server, no JSON tokens, no manual page sharing.
• Markdown-native reading and editing is token-efficient.
• Permissions follow each user’s Notion access.

Cons and caveats

• Some features depend on plan: SQL-style queries and higher request limits are better on Business and Enterprise, and MCP tokens for headless use are Business/Enterprise only.
• File uploads are capped (20 MiB per Notion’s docs).
• Workspace guests cannot connect.
• The old makenotion/notion-mcp-server repo still exists but Notion has stopped actively supporting it.

Links

• Docs: developers.notion.com/docs/mcp
• Tool list for agents: Notion publishes llms.txt on its developer site.
• Related: Linear MCP, Atlassian MCP, and our MCP guide.