You can connect Notion to Claude in a few minutes using the Model Context Protocol (MCP), and once it’s connected, Claude can search your workspace, pull up a page, and draft new content without you copying and pasting anything. This guide covers both ways to do it: Notion’s official remote MCP server connected directly, and connecting it through a gateway if you also use other AI clients or tools.
What the Notion MCP server actually does
Notion publishes an official remote MCP server at mcp.notion.com/mcp. It exposes your workspace’s pages and databases as tools Claude can call directly, instead of you exporting content or pasting it into the chat. In practice that means prompts like:
- “Find the onboarding doc and give me the short version.”
- “What did we decide about pricing? Search the workspace.”
- “Draft meeting notes as a new page in the team wiki.”
- “Turn this discussion into a documented decision page.”
Claude reads and writes through the same permissions your Notion account already has — it isn’t a separate scraper or export, it’s your account acting on your behalf.
Option 1: Connect Notion to Claude directly
Claude supports remote MCP servers natively. The short version of the setup:
- Open Claude’s connector or MCP settings.
- Add a remote server pointing at Notion’s MCP endpoint.
- Sign in with your Notion account when prompted — this is standard OAuth, so Claude never sees your Notion password, and you can revoke access from Notion’s own settings at any time.
That’s enough for one person using Notion inside Claude. The tradeoffs show up once you add a second tool or a second person: every additional AI client (ChatGPT, Cursor, an agent) needs its own copy of that same connection, its own OAuth grant, and its own place where the config can go stale or get lost.
Option 2: Connect it once, through a gateway
If you’re already juggling more than one MCP server, or more than one AI client, wiring each pair directly gets old fast — that’s the connection sprawl we wrote about in what an MCP gateway is. The alternative is connecting Notion (and everything else) to one gateway URL, then pointing every AI client at that single URL instead of reconfiguring each one.
With gate specifically, connecting Notion looks like this: add gate’s gateway URL to Claude once, then pick Notion from the Notion server page in the directory and sign in with OAuth the same way you would directly. From then on, Notion’s tools are available in every client connected to your gate URL — Claude, ChatGPT, or Cursor — without a second setup step. You can see the full list of servers set up this way on the MCP servers page.
Why the connection method matters for a workspace tool
Notion is exactly the kind of server where the access question is worth pausing on before you connect it: it can hold anything from public documentation to HR notes or draft contracts, and an MCP connection gives your AI client the same reach into that workspace that you have. A few things worth checking before or right after you connect:
- Is it the official endpoint? Connect Notion’s documented server (
mcp.notion.com), not a third-party mirror claiming to proxy it. - What can it write, not just read? A search-and-draft server like Notion’s can create and edit pages. Know that before you hand it a broad prompt like “clean up the wiki.”
- Who else in your team can reach it? If more than one person connects Notion to their own AI client, you likely want a shared, revocable setup rather than everyone holding their own token. That’s the same access-control question we cover in MCP access control for teams.
You can run a quick, no-signup check on any server’s tool list — including ones that require OAuth, once connected — with gate’s free MCP server scanner, which looks for prompt injection and hidden instructions in tool descriptions before you rely on a server day to day.
Troubleshooting the connection
A few things that commonly go wrong when connecting any remote MCP server, Notion included:
- OAuth loop or sign-in fails. Make sure you’re signed into the right Notion workspace in your browser before authorizing — a mismatched workspace is the most common cause.
- Claude can’t find a page you know exists. Notion’s search tool respects your permissions in Notion itself — if a page isn’t shared with your account, Claude won’t see it either.
- Tools disappear after a Notion update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that kind of change is exactly what drift detection is meant to catch.
The bottom line
Connecting Notion to Claude with MCP takes a few minutes either way: point Claude directly at Notion’s server and sign in, or connect it once through a gateway if you want the same Notion access available in every AI client you use, with the server’s tools checked before they go live. Either way, treat the OAuth grant for a workspace tool like Notion the same way you’d treat any other broad permission — worth a minute’s thought before you say yes.