Notion MCP

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-search reaches 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" page

The 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.

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.