Offizieller Notion MCP Server für Claude Code mit einem Befehl nutzbar
Der offiziell gehostete Notion MCP Server lässt sich ohne API-Token in Claude Code einbinden. Damit entfällt das manuelle Kopieren von Anforderungen, Meetingnotizen und Tickets aus Notion ins Terminal.

Posted on Oct 14 • Originally published at quickpromptco.com
Your specs, meeting notes, and bug tickets live in Notion. Your code lives in Claude Code. So every task starts with the same ritual: open the Notion page, copy the requirements, paste them into the terminal, and hope you didn’t miss the comment thread at the bottom where the scope changed.
Notion MCP is Notion’s official hosted MCP server at mcp.notion.com. Claude Code signs in with your Notion account through OAuth and can then search your workspace, read pages and databases as Markdown, and create or update pages, all limited to what you can already see. There’s no API token, no JSON config, and nothing to run locally.
Heads-up: search results still point to the older self-hosted package ( @notionhq/notion-mcp-server ). Notion’s own README now says that repo is no longer actively maintained and recommends the hosted server instead. That’s the version this guide sets up, for the same reason our community MCP picks skip abandoned servers.
claude mcp add --transport http --scope user notion https://mcp.notion.com/mcp Enter fullscreen mode Exit fullscreen mode Then sign in: run /mcp inside Claude Code, select notion, and approve access in the browser window that opens. Total time: about 2 minutes.
Skip the manual steps below and hand the whole job to the agent instead:
You have shell access and the `claude mcp` CLI on this machine. Connect Notion's official hosted MCP server to Claude Code and report back. Do not tell me it's done unless step 5 actually confirms it: 1.
Run `claude mcp list`. If a notion entry already exists, show me its command or URL. If it runs `npx @notionhq/notion-mcp-server` (the old self-hosted server), tell me and ask before replacing it.
2. If there's no hosted entry, add it for all projects: `claude mcp add --transport http --scope user notion https://mcp.notion.com/mcp` 3. Tell me to run `/mcp` inside Claude Code (or `claude mcp login notion` in a terminal) and complete the Notion sign-in in my browser.
Wait for me to confirm. Never ask me for a Notion token or integration secret; this server uses OAuth only. 4.
Run `claude mcp list` and confirm notion shows Connected. 5. Search my Notion workspace for any page (use a short keyword like "meeting") and show me the titles of up to 3 results.
Read only; do not create or edit any page. If any step fails, give me the exact error and the command that produced it. Do not skip ahead.
Enter fullscreen mode Exit fullscreen mode The agent can’t click “Allow” in Notion’s sign-in page for you, so the prompt pauses there. It also checks for the old self-hosted server so you don’t end up with two Notion entries.
Prefer to do it by hand instead of delegating to the agent? Here’s the manual version.
--scope user makes Notion available in every project. Use --scope project instead to share it with your team through a.mcp.json file in the repo:
claude mcp add --transport http --scope user notion https://mcp.notion.com/mcp Enter fullscreen mode Exit fullscreen mode
Real run, October 2026. Needs authentication means the server is reachable and waiting for you: run /mcp inside claude to sign in.
Inside Claude Code, run /mcp, pick notion, and follow the browser prompt. Prefer the terminal? This runs the same sign-in without opening a session:
claude mcp login notion Enter fullscreen mode Exit fullscreen mode Choose the workspace you want Claude to reach. You can connect only one workspace per entry.
Every MCP server adds tool definitions to Claude’s context. Run /context in Claude Code to see how many tokens Notion takes, and compare it with your other servers.
Your Notion pages and databases, readable from the terminal after one OAuth sign-in.
claude mcp list Enter fullscreen mode Exit fullscreen mode ✔ notion https://mcp.notion.com/mcp (HTTP) – Connected! notion Needs authentication → run /mcp and finish the sign-in ✘ notionApi npx @notionhq/notion-mcp-server → old self-hosted entry; remove it
Find the Notion page for our next feature, list the requirements that don 't have a matching file in this repo yet, and don' t edit anything in Notion Enter fullscreen mode Exit fullscreen mode If Claude calls notion-search, then notion-fetch, and compares the page against your code, the connection and your permissions are working.
The server is free to connect on any Notion plan. Some features, like AI search across connected apps and certain search filters, depend on your Notion plan.
It can see what your Notion account can see, nothing more. For tighter scope, sign in with an account that only has access to the teamspaces Claude needs.
No. The hosted server replaces it. Notion says the self-hosted repo may be sunset and that issues there aren’t actively monitored.
Yes. Add it with --scope project and commit the generated.mcp.json. Each person still signs in with their own Notion account.
claude mcp remove notion --scope user. To also revoke the grant on Notion’s side, remove the connection in Notion under Settings → Connections.
Originally published at quickpromptco.com, where the guide is kept up to date.