Up-to-date library docs pulled directly into your AI context.
Notion
Read, write, and search across Notion pages, databases, and blocks.
Install Notion
— pick your client, copy, paste.{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}
}Paste under mcpServers. Fully quit and reopen Claude after editing.
# export NOTION_API_KEY=secret_your_integration_token
claude mcp add notion -- npx -y @notionhq/notion-mcp-serverRun from your repo. Commit .mcp.json to share with your team.
{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}
}Global path: ~/.cursor/mcp.json. Reload window after editing.
{
"servers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}
}VS Code uses the "servers" key (not "mcpServers").
{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}
}Open via Cascade → hammer icon → Configure.
{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}
}Open via the Cline sidebar → MCP Servers → Edit.
{
"experimental": {
"modelContextProtocolServers": [
{
"transport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}
]
}
}Continue uses modelContextProtocolServers with a transport block.
# ~/.codex/config.toml
[mcp_servers.notion]
command = "npx"
args = [
"-y",
"@notionhq/notion-mcp-server",
]
env = { NOTION_API_KEY = "${NOTION_API_KEY}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
{
"context_servers": {
"notion": {
"command": {
"path": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
]
},
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}
}Zed calls them "context_servers". Settings live-reload on save.
{
"name": "Notion",
"transport": "stdio",
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}Enable Developer mode (paid plans) and enter these values in the UI.
Quick answer
What it does
Surfaces Notion's page, database, and block APIs as MCP tools — search, read, create, update, and query with filter expressions.
Best for
- Agent-generated meeting notes
- Project database queries
- Living knowledge-base updates
- Auto-generated status pages
Not for
- Bulk content migration
- Real-time collaborative editing
Setup recipe
- 1
Install
Copy the install snippet for your client from the Install section above.
- 2
Set required secrets
Set
NOTION_API_KEYin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Summarise a known workspace page
Find the page titled "Weekly Planning" in my Notion workspace and summarise its current state in 5 bullets. Highlight any item blocked on someone else.Tested with: Claude Desktop, Cursor.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Security & scope
- Access scope
- Read + write
- Sandbox
- Authenticates via a Notion integration token with exactly the permissions granted to the integration at installation time.
- Gotchas
- The integration only sees pages explicitly shared with it — on un-shared pages the MCP returns 404.
- Integration tokens cannot be restricted to a single workspace — they have workspace-level access once granted.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. documents & content work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-documents-content
Compare Notion MCP vs [Obsidian MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/notion - top-mcps.com listing for Obsidian
Install the Notion MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/notion (fetch https://top-mcps.com/mcp/notion.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (NOTION_API_KEY) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Documents & Content MCPs
Other tools in the same category worth evaluating.
Exploring Top MCPs for Documents & Content? See all Documents & Content MCPs →