Overview
What Notion MCP does
Notion MCP connects an agent to the signed-in user's workspace and exposes tools optimized for finding and editing pages, data-source content, comments, and related workspace information. The hosted service is Notion's actively supported path and uses standard OAuth, avoiding local process and integration-token setup. It is suited to collaborative knowledge work where the agent should operate with the same content permissions as the user.
Best for
- Finding project knowledge across a Notion workspace
- Drafting and updating specifications, reports, and task pages
- Combining search, page creation, and property updates in one agent workflow
Not ideal for
- Headless jobs that cannot complete a user OAuth flow
- File or image uploads through MCP
- Automation that needs a narrowly scoped service identity instead of a human user
Capabilities
What an agent can do
- 01
Workspace and connected-source search
- 02
Page retrieval and Markdown-oriented editing
- 03
Page and data-source creation
- 04
Property and data-source updates
- 05
Comments and user lookup
- 06
Hosted OAuth access with no local runtime
Representative tools and operations
notion-searchnotion-fetchnotion-create-pagesnotion-update-pagenotion-create-databasenotion-update-data-sourcenotion-create-commentnotion-get-users
Installation
Connect Notion MCP
Use the publisher’s current instructions as the source of truth. The examples below were checked on .
Claude CodeAdd the hosted server
claude mcp add --transport http notion https://mcp.notion.com/mcpRun /mcp in Claude Code and complete the browser authorization flow.Generic MCP clientConfigure the recommended endpoint
https://mcp.notion.com/mcp{"type":"http","url":"https://mcp.notion.com/mcp"}Trust and access
Authentication and security notes
Authentication: Interactive user-based OAuth. The hosted service does not accept a conventional Notion integration token or generic bearer token, so a user must authorize the client.
Review before connecting
- Verify the endpoint is exactly on mcp.notion.com before authorizing.
- The agent receives the same workspace reach as the signed-in user, including connected sources available to that user.
- Review create, update, move, and comment actions before execution.
- Use trusted MCP clients and periodically revoke connections that are no longer needed.
Known limitations
- Hosted Notion MCP requires a human OAuth flow and does not support bearer-token automation.
- Image and file uploads are not currently supported through the hosted MCP tools.
- Workspace and API rate limits can throttle multi-step workflows.
- The older open-source local server is no longer the actively supported default.
Evidence
Sources used for this guide
Facts were checked against primary publisher material. Descriptions and guidance are original Graphify summaries.
FAQ
Questions about Notion MCP
Can I connect Notion MCP with an integration token?
Not to the hosted endpoint. It requires user OAuth. The older self-hosted package supports token-based access but is not Notion's actively supported path.
Can Notion MCP upload files?
No. Page and workspace operations are supported, but file and image uploads currently require the Notion API or another workflow.
