The hosted server and what it needs
Notion runs one hosted MCP server. You add the URL to your AI tool and sign in; nothing runs on your machine.
| Notion MCP, as of November 2026 | |
|---|---|
| Endpoint | https://mcp.notion.com/mcp (Streamable HTTP) |
| Legacy endpoint | https://mcp.notion.com/sse, retired on February 23, 2027 |
| Sign-in | OAuth in the browser; MCP tokens for Business and Enterprise (created by a workspace owner); enterprise-managed authorization for Enterprise with SAML SSO |
| What the AI can reach | What the signing-in member can access in the selected workspace |
| Who can connect | Workspace members, not guests |
| Plans | All plans; Business and Enterprise get higher request limits, unlimited SQL queries (with Notion AI), connected-source search and extra search filters |
Notion’s setup guide covers Claude Code, Codex, Cursor, VS Code with Copilot, Devin and others. For clients that only run local servers, Notion suggests bridging with npx -y mcp-remote and the URL.
Notion MCP calls count toward Notion’s standard API request limits. When a call is rate limited, Notion MCP retries it once if the wait is 2 seconds or less; for a longer wait it returns a rate_limited tool error at once, with retry_after_seconds when known and rate_limit_reason naming the limit that was hit. Notion’s advice to an assistant that runs into this is to reduce parallel operations or try again later.
Setting it up, per tool
- Claude Code:
claude mcp add --transport http notion https://mcp.notion.com/mcp, then sign in through/mcp. Use the project scope to share the setup with the team through the repo (see MCP servers in Claude Code for a team). - Codex: add the URL to
~/.codex/config.toml, runcodex mcp login notion. A project-level.codex/config.tomlshares it with the team. - Cursor: put the server in
.cursor/mcp.json, enable it and complete OAuth. - VS Code with Copilot: put it in
.vscode/mcp.json, start it from the MCP commands and complete OAuth. - Claude or ChatGPT in the browser: add it as a connector; per tool see how to connect an MCP server.
An admin may restrict adding MCP servers. Workspace owners manage MCP clients and can see how members use Notion MCP through Notion’s admin controls.
Memories and Skills: personal versus shared
Notion MCP has two features that sound like team memory. They are not the same thing.
- Memories. You can ask your assistant to save context in your personal Notion memories and recall it later, also in another client connected to the same Notion account and workspace. That is real portability across tools, but it is yours. Notion calls them personal memories.
- Skills. You can create Skills in Notion, share them with teammates and use them in any AI assistant connected to Notion MCP. That is shared, but it is a written instruction someone made on purpose, not something the AI learned.
So what your AI learns about your preferences can follow you from Claude to Cursor, but it does not reach your colleague.
The common misunderstanding
“Our wiki is in Notion, so now the AI knows our wiki.” The AI can search and fetch pages when it chooses to, as you. If the wiki has outdated pages, it may cite them. If something was never written down, it is not there. And the AI acts with your access: if you can edit a page, so can it. Decide whether the AI may write, or ask it to propose changes for a human to apply.
The old open source notion-mcp-server is a second trap. Notion describes it as no longer actively maintained, needing an integration token and your own infrastructure, and recommends the hosted server instead.
What this means for a team
Notion MCP gives every MCP-capable tool in your team the same view of Notion, each person within their own permissions. That is useful: the developer in Cursor and the manager in Claude read the same pages. What stays separate is what each person’s AI picks up along the way, unless someone writes it into a page or a Skill. For the basics, see what is an MCP server; if your knowledge is spread over Jira and Confluence as well, see the Atlassian MCP server.
Where Bombos fits
Notion holds what your team wrote down; Bombos holds what the team’s AI tools learn while working, shared across people and tools. It is a plugin for Claude, Claude Code, ChatGPT, Copilot, Cursor, Codex, Grok and your own agents, with team knowledge and learned rules, and it also reads what already sits in documents, mail and repos, with a trail of what each answer rests on. It runs in our cloud or on your own server, and one person can try it first with their own agents.
Related questions
Which Notion plan do I need for Notion MCP?
Notion says all plans can use Notion MCP. MCP tokens, connected-source search (notion-connector-search) and some search filters require Business or Enterprise.
Can guests use Notion MCP?
No. Notion's documentation says only workspace members can connect Notion MCP.
Is the SSE endpoint still supported?
For now. Notion is retiring https://mcp.notion.com/sse on February 23, 2027, so set up clients with Streamable HTTP at https://mcp.notion.com/mcp.
Can an agent connect without a browser sign-in?
On Business and Enterprise a workspace owner can create an MCP token in the Developer portal, which the client sends as a bearer token.
Are Notion MCP memories shared with my team?
Notion describes them as personal memories: you can recall them in another client connected to the same Notion account and workspace. Notion Skills, by contrast, can be shared with teammates.
