Notion MCP Server
Connect Notion to your AI agents — pages, databases, and search as tools.
Updated
What is Notion MCP?
The Notion MCP server is an implementation of the Model Context Protocol that exposes your Notion workspace to AI agents as a set of tools. Instead of pasting Notion content into a chat, an agent connected to the Notion MCP can search your workspace, read and create pages, and query databases directly.
Notion ships an official hosted server at https://mcp.notion.com/mcp that you connect with OAuth, so there is nothing to deploy. A self-hosted open-source version is also available if you want to run it against the Notion API with your own token.
Tools the Notion MCP server exposes
| Tool | What it does |
|---|---|
| search | Full-text search across the connected Notion workspace |
| fetch | Retrieve a page or database by ID, including its content blocks |
| create-pages | Create one or more new pages, optionally inside a parent page or database |
| update-page | Update the properties or content of an existing page |
| query-database | Filter and sort rows in a Notion database |
| get-comments | Read comments on a page |
| create-comment | Add a comment to a page |
Connect the Notion MCP server
Connect Notion MCP to Claude Code
- 1
Add the server
Run `claude mcp add --transport http notion https://mcp.notion.com/mcp` in your project.
- 2
Authorize with OAuth
On first use, Claude Code opens a browser to sign in to Notion and grant access to the pages you choose.
- 3
Verify
Ask Claude to "search my Notion for the onboarding doc" to confirm the tools are live.
Notion's OAuth lets you scope access to specific pages — grant the minimum the agent needs.
Connect Notion MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add the URL
Use `https://mcp.notion.com/mcp` as a streamable HTTP server and complete the OAuth flow.
- 3
Test
Reference a Notion page in chat and confirm Cursor can fetch it.
Sample use cases
A support agent needs the latest internal runbook
It searches Notion, fetches the runbook page, and answers from the live doc — no copy-paste.
You want meeting notes turned into a project database row
The agent creates a page in your Projects database with the right properties filled in.
A weekly digest of a Notion roadmap database
The agent queries the database, filters to this sprint, and posts a summary.
Security & permissions
The hosted Notion MCP server authenticates with OAuth, not a static token, so you never paste a secret into your client config. During authorization Notion lets you choose exactly which pages and databases the integration can access — agents can only see what you grant. Revoke access at any time from Notion's Settings → Connections. For the self-hosted server you supply a Notion internal integration token; treat it as a secret and scope the integration's capabilities in Notion.
Using Notion MCP with Gamut
On Gamut, the Notion MCP server becomes a tool your agents use as part of an automated workflow — not just an interactive chat. An agent can be triggered by an event (a new lead, a closed deal, a scheduled digest), pull context from Notion, act across your other connected MCP servers, and write the result back to a Notion page or database. Because Gamut manages the OAuth connection and runs agents on a schedule or on triggers, your Notion workspace stays in sync without anyone in the loop.
Frequently asked questions
What is the Notion MCP server?
It is an official Model Context Protocol server from Notion that exposes your workspace — search, pages, and databases — to AI agents and assistants as callable tools.
Is the Notion MCP server free?
Yes. The official hosted server is free to connect with OAuth on any Notion plan; standard Notion API rate limits apply.
How do I connect Notion MCP to Claude?
Add `https://mcp.notion.com/mcp` as an HTTP MCP server in Claude (or `claude mcp add` in Claude Code) and complete the OAuth sign-in, choosing which pages to share.
Hosted vs self-hosted Notion MCP — which should I use?
Use the official hosted server for the simplest setup and OAuth scoping. Self-host the open-source server only if you need to run it inside your own infrastructure with an internal integration token.