Notion MCP
Notion's hosted MCP server — search the workspace, fetch and create pages and databases, and manage comments through Markdown-optimized agent tools.
Notion's hosted MCP server (mcp.notion.com) exposes 18 tools built around Notion-flavored Markdown for token efficiency: notion-search across the workspace (and connected Slack/Drive/Jira with Notion AI), notion-fetch by URL, page and database create/update/move, comments, and user/team lookups. OAuth-only — one claude mcp add plus a browser flow, and your workspace becomes agent-readable.
Notion MCP turns the team wiki from something you quote at the agent into something it reads itself. Specs, runbooks, decision docs, meeting notes — notion-search and notion-fetch make them retrievable mid-task, and the write tools let the agent file its own output where the team will actually find it.
Highlights
- 18 tools across the real workflows — search, fetch-by-URL, page create/update/move/duplicate, database creation and queries, views, comments, user/team lookups.
- Markdown-optimized — tools speak Notion-flavored Markdown rather than raw block JSON, a deliberate token-efficiency design Notion has written up publicly.
- Connector-aware search — with Notion AI,
notion-searchreaches connected Slack, Google Drive, and Jira too: one retrieval tool over the team's whole knowledge surface. - Hosted, OAuth-only —
mcp.notion.com/mcp; access inherits the authorizing user's permissions, so the agent sees exactly what you see.
In an AI-assisted workflow
claude mcp add --transport http notion https://mcp.notion.com/mcp
# in a session: /mcp → notion → Authenticate
# then:
# > Find our API versioning policy in Notion and apply it to this new endpoint;
# > when done, append a decision note to the "API decisions" pageThe pattern: docs in, decisions out. The agent grounds work in the team's written context, then writes durable artifacts back instead of leaving them in a chat transcript.
When another teammate takes over, use the AI project-handoff workflow to preserve the source files, decisions, and unresolved work. For company knowledge spread across configured systems, Glean is an enterprise search option to evaluate.
TIP
The agent's access equals your access — scope writes with permission rules (ask on mcp__notion__notion-update-page and friends) while you build trust, and keep retrieval tools friction-free.
Good to know
The hosted server is the only actively supported path — Notion's open-source local server (makenotion/notion-mcp-server, MIT) is in maintenance mode with a possible sunset, useful mainly when you need token-based auth instead of OAuth. Plan gating applies to a few tools (connector search needs Notion AI; some database queries need Business+/Enterprise). Treat workspace content as sensitive context: it flows into the model like anything else the agent reads.
Frequently asked questions
- How do I connect Notion to Claude Code?
- claude mcp add --transport http notion https://mcp.notion.com/mcp, then /mcp in a session to complete the browser OAuth. The hosted server is OAuth-only — no API-key/bearer auth — and access mirrors the permissions of the user who authorized it.
- What tools does the Notion MCP server expose?
- Eighteen, spanning the real workflows: notion-search and notion-fetch for retrieval; create/update/move/duplicate for pages; database creation, views, and queries; comments; and user/team lookups. Outputs use Notion-flavored Markdown, which keeps token usage down versus raw block JSON.
- Is Notion MCP free?
- Connecting is free with any Notion account, but some tools are plan-gated: cross-connector search (Slack, Google Drive, Jira) requires Notion AI, database-view queries need Business+, and data-source queries need Enterprise with Notion AI.
Filed under
mcp · notion · docs · knowledge-base · workspace
Related
- Adding MCP Servers to Claude Code: Local, Remote, and Project-ScopedThe complete claude mcp add reference — stdio vs HTTP transports, local/project/user scopes, .mcp.json with env expansion, OAuth via /mcp, and the gotchas.
- Connecting and Governing MCP Servers: Registries, Gateways, and Tool SprawlAs MCP servers multiply, discovery, trust, and tool sprawl become the problem. How registries, gateways, and curation keep a growing fleet secure and usable.
- The Best MCP Servers in 2026The MCP servers actually worth connecting in 2026 — Context7, GitHub, Chrome DevTools, Playwright, Serena, Exa, Firecrawl, and official vendor servers.
- Linear MCPLinear's hosted MCP server — find, create, and update issues, projects, and comments from your AI agent, with OAuth and one-command setup.
- Adr WriterWrite an Architecture Decision Record capturing a decision the user describes, in Michael Nygard ADR format (Status, Context, Decision, Consequences) with an added Considered Alternatives section. Use when recording a significant architectural or technology choice.
- Readme GeneratorGenerate or refresh a project README grounded in the actual repository. Use when a project has no README, a stale one, or you want install/usage/scripts/structure sections that match the real code.
- AI ConnectorsAI connectors are the integrations that let an assistant like Claude read and act in tools such as Google Drive, Slack, and Notion; in Claude, MCP servers.
- Slack MCP ServerThe community-canonical Slack MCP server — smart history fetch, message search, channels, reactions, and opt-in posting, after the official server was archived.