Notion is a Productivity MCP server that lets Claude Code, Cursor, Windsurf and any MCP-compatible AI agent pages, databases, search in Notion workspace. Install in 1 minute with mcpizy install notion.
Connect your Notion account once — MCPizy stores the credentials encrypted and uses them whenever you run a recipe in managed mode.
mcpizy install notionnpx -y @notionhq/mcp-serversearchSearch pages and databases across the workspace
Inputs
querystringrequiredfetchFetch the full content of a page or database by ID
Inputs
idstringrequiredcreate_pagesCreate one or more pages in a database or under a parent
Inputs
parentobjectrequiredpagesobject[]requiredupdate_pageUpdate a page's properties or content
Inputs
page_idstringrequiredpropertiesobjectoptionalcreate_databaseCreate a new database with a schema
Inputs
parentobjectrequiredtitlestringrequiredpropertiesobjectrequiredcreate_commentAdd a comment to a page
Inputs
page_idstringrequiredtextstringrequiredWorks identically across clients. Only the config file path differs.
~/.claude.json{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "ntn_..."
}
}
}
}.cursor/mcp.json{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "ntn_..."
}
}
}
}~/.codeium/windsurf/mcp_config.json{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "ntn_..."
}
}
}
}Create an integration and copy the internal integration secret
NOTION_API_KEYShare the pages or databases you want accessible with the integration
Paste any of these prompts into Claude Code, Cursor or another MCP-compatible client.
“Search my Notion for pages mentioning 'Q2 roadmap' and summarise them”
Uses: search, fetch
“Create a new page in my Tasks database titled 'Review PR #42'”
Uses: create_pages
“Add the latest meeting notes to my Engineering workspace”
Uses: create_pages
“Update page abc123 and mark its Status as Done”
Uses: update_page
Notion MCP exposes the Notion database, page, and block APIs as tool calls AI agents can chain. The official server ships primitives like `search`, `fetch_page`, `create_page`, `update_page`, `append_block_children`, and `query_database` — the same surface that powers the Notion web app's API integrations. Where pages have a hierarchical block tree, the MCP lets the agent walk it: read a parent doc, fetch every child block, summarise, and write back. Authentication is OAuth or an internal integration token; the agent only sees pages explicitly shared with that integration, which gives you a clean scoping model out of the box.
We use Notion MCP for three workflows daily. First, meeting-notes reconciliation: "read yesterday's standup page, pull action items, create one Notion sub-page per owner." Second, weekly reports: the agent queries a database filtered by date and rolls up properties into a parent page. Third, knowledge-base lookups during coding sessions — "find the Notion doc that defines our deploy runbook" beats hunting through the sidebar. Token cost is dominated by block-tree size; a typical 2-page doc costs ~3-5k input tokens to read fully, and database queries returning 50 rows of 8 properties land around 4k tokens.
Compared to Linear MCP, Notion is the right choice when your planning lives in databases of tasks/projects (PMs, founders, ops teams) rather than engineering issues. Compared to Coda or Airtable MCPs, Notion's block-tree gives richer prose-and-data hybrids but a weaker formula engine. The honest trade-off: the MCP is slower than the dashboard for bulk edits (each page update is ~500-800 ms) and the block API forces you to update one block at a time — large document rewrites burn tokens and time fast.
Integration scoping bites hard. The agent only sees pages and databases that were explicitly shared with the integration in Notion settings — silent empty results almost always mean a missing share, not a missing page. Tell users to share the parent workspace once rather than per-page.
Rich-text formatting round-trips lossily through the API. If the agent reads a page with toggle blocks, callouts, or columns and rewrites it with `update_page`, expect formatting drift. For destructive rewrites, use `append_block_children` against a fresh sub-page rather than overwriting the original.
Database property names are case-sensitive and space-sensitive — "Due Date" and "due date" are different properties and `query_database` will reject the wrong one without a useful error. Have the agent call `fetch_database` first to read the canonical schema.
Rate limits are 3 req/sec sustained; an agent that walks a 200-page workspace via `fetch_page` will hit 429s within a minute. Batch via `search` + ID lists, then fetch in chunks of 10 with a brief pause.
Honest pros/cons against the closest productivity MCP servers.
| Server | Strengths | Trade-offs |
|---|---|---|
| Linear MCP | Cleaner issue model, cycles/projects primitive, faster API | No prose-first pages or flexible databases |
| Coda MCP | Stronger formula engine, table-first design, better for structured ops | Smaller MCP community, fewer maintained tools |
| Airtable MCP | Best for structured relational data with views | No prose/block model — pure database, weaker for documentation |
If Notion doesn't fit your stack, these Productivity MCP servers solve similar problems.
The Notion MCP server is an Productivity Model Context Protocol server that lets Claude Code, Cursor, Windsurf, VS Code with Copilot, and other MCP-compatible AI agents pages, databases, search in Notion workspace. It exposes Notion's capabilities as tools the AI can call directly from your editor or CLI.
The fastest way is the MCPizy CLI: run `mcpizy install notion` and MCPizy will add the server to your `.claude.json` automatically. You can also install it manually by adding an entry under `mcpServers` in `.claude.json` with the command `npx -y @notionhq/mcp-server` and restarting Claude Code.
Yes. The Notion MCP server is free and open source (see the GitHub repository linked on this page). You may still need a Notion account or API key to connect the server to the underlying service, but the MCP layer itself has no MCPizy subscription cost.
Yes. Any MCP-compatible client works — including Claude Code, Claude Desktop, Cursor (via `.cursor/mcp.json`), Windsurf, VS Code with Copilot Chat, and custom agents built on the MCP SDK. The same install command targets all of them; only the config file path differs.
Once installed, your AI agent can pages, databases, search in Notion workspace directly inside your conversation. Typical use cases include asking Claude Code or Cursor to run Notion operations, inspect results, chain Notion with other MCP servers (see our Workflow Recipes), and automate repetitive productivity tasks without leaving your editor.