Notion MCP server: setup, auth, production
Last verified: June 2026· Notion MCP integration
Official MCP server commonly availableYour team’s docs, specs, and knowledge base.
What is the Notion MCP server?
A Notion MCP server implements the Model Context Protocol and exposes Notion's capabilities as typed tools an agent can discover and call in the middle of a task. Your team’s docs, specs, and knowledge base.
Docs and comms access give an agent the context that lives outside the repo — the spec, the decision, the channel where it was made — and a way to report back. Scope to the right spaces and prevent noisy or unauthorized posting.
A real Notion workflow
The agent reads the spec in Notion while implementing it, then writes the “what changed and why” doc back — so documentation is a by-product of the work instead of a task nobody gets to.
What an agent can do with Notion
- Let an agent read a spec while implementing it
- Generate or update documentation from a change
- Search internal knowledge for context
Read-only is the right default: let the agent observe and reason first, then grant specific write actions deliberately — each behind audit logging and, for anything high-impact, human approval.
Setting up the Notion MCP server
The trap: the Notion MCP server uses OAuth, not the internal-integration token (ntn_…) you may already have. Those are different auth systems — the integration token will not authenticate the MCP server.
Auth: Notion OAuth (note: MCP uses OAuth, not the REST integration token). Credentials belong in the environment or a secret store — never in the repo or the agent's sandbox. Wiring a server into Claude Code or Cursor is the same for every tool; the step-by-step lives in the MCP connection guide.
The risk to watch with Notion
Beyond the OAuth gotcha, scope access to the specific workspaces or pages the agent needs; a broad grant exposes the whole company wiki to whatever the agent ingests.
More broadly, a production-grade Notion integration needs correct OAuth setup and scoping access to the right workspaces. The MCP security checklist applies to every integration — we build servers with these controls baked in.
Troubleshooting
If the Notion tools don't appear after setup, it's almost always auth or transport. See MCP server not connecting for the step-by-step fix — and note that hosted servers often need OAuth, not a plain API key. To understand how MCP relates to ordinary tool use, see MCP vs function calling.
Frequently asked questions
Is there an official MCP server for Notion?
Official MCP server commonly available. Whichever you use, a production setup needs correct oauth setup and scoping access to the right workspaces.
How does authentication work for Notion over MCP?
Notion OAuth (note: MCP uses OAuth, not the REST integration token). Credentials should never live in the sandbox or the repo; route them through your client's secret handling or a vaulted credential.
What can an agent actually do with Notion?
Let an agent read a spec while implementing it; Generate or update documentation from a change; Search internal knowledge for context. Start read-only and add write access deliberately, behind audit logging.
Is it safe to give agents access to Notion?
Yes, when scoped correctly: least-privilege credentials, read-only by default, audit logs on every call, and human approval for any high-impact action. Correct OAuth setup and scoping access to the right workspaces.