How to Connect Notion to Claude and What It Can See

How-to — 2026-11-03 — by Mahmoud Zalt

Connect your Notion workspace to Claude with Notion MCP, then learn exactly which pages it can read and which ones stay invisible to it.

Most people searching this have the same picture in their head. They imagine pointing Claude at the workspace once, and from then on it simply knows everything in there. That picture is wrong in an important way, and the gap between it and reality is where nearly all the disappointment comes from.

What you are really building is a doorway, not a download. Claude does not swallow your workspace and hold it in memory. It asks for one specific thing at a time, gets an answer back, and has to ask again next time it needs something.

That design is good news for privacy and mildly annoying for expectations. It means nothing is copied out wholesale, and it also means the quality of what you get back depends heavily on how findable your pages are.

At a Glance

4: core tools: search, fetch, create pages, update page
Yours: the exact Notion permissions the connection inherits
3/sec: average Notion API calls allowed, totalled across tool calls
Paid plans: remote connectors are not available on Claude's free tier

What does connecting Notion to Claude actually do?

It gives Claude a small set of tools it can call against your workspace while you are chatting. It can search for pages, fetch the contents of a page or database by URL, create new pages with properties and content, and update the properties of a page that already exists.

Those tools are chained inside a single request. Ask for a summary of last quarter's retro notes and Claude will search, pick candidates, fetch the ones that look right, then write the answer from what came back. You can watch each call happen.

Search: looks across your Notion workspace. Notion's docs note that searching connected tools like Slack, Google Drive and Jira from this tool needs Notion AI access, and without it the search stays inside Notion.
Fetch: pulls the content of a page or database when it has the URL. This is the one that does the actual reading.
Create pages: writes one or more new pages, with properties, into a location you point at.
Update page: changes the properties of an existing page, which is how status fields and dates get moved.

How do I connect Notion to Claude?

Two routes work. The simple one is to add Notion from the connectors area inside Claude and approve the Notion authorization screen. The other is to start from Notion's own MCP gallery, which hands you to the same authorization step from the other direction.

Either way the connection is made with OAuth, which means you sign in at Notion rather than pasting a secret into Claude. Notion's developer docs also note that this flow is interactive by design, so there is no way to set it up without a human clicking approve.

Connect Notion to Claude

Check your plan first — Notion's developer docs state that remote MCP servers are not available on Claude's free tier. If the connector option is missing, this is usually why.
Open connectors in Claude and add Notion — Claude lists Notion among the available connectors. Choosing it starts the authorization handoff. Nothing has access yet at this point.
Approve on Notion's own page — Notion shows you what is being authorized and which workspace it applies to. Read the workspace name carefully if you belong to more than one.
Ask a boring question first — Something like: find the page called onboarding checklist and tell me the last three bullet points. If it comes back correct, the wiring is right.
Then test a write — Ask it to create a single throwaway page in a test area. Confirm the page lands where you expected before you let it near anything real.

The workspace name on that approval screen matters more than people expect. Plenty of readers have a personal workspace and a company one under the same login, and approving the wrong one produces an assistant that confidently reports there is nothing in your workspace.

What about Claude Code and other clients?

Any client that speaks MCP can connect to the same server. Notion publishes the endpoint directly, so you point your client at it and complete the same sign in. For Claude Code, Notion's docs give a one line command and then an in session authorization step.

After that you run the MCP command inside the session to finish signing in. Notion also documents an older event stream endpoint for clients that cannot handle the newer transport, which is worth knowing if your tool is a bit behind.

What can Claude actually see in my workspace?

Exactly what you can see, and nothing else. Notion's help centre states plainly that MCP tools act with your full Notion permissions. A private page belonging to a colleague stays invisible. A teamspace you were never added to stays invisible. Your existing permissions keep applying without any extra configuration.

This cuts both ways. Nobody can use the connector to reach around Notion's sharing rules, which is the point. But it also means a page you personally cannot open will never appear in an answer, no matter how clearly you describe it.

What you are asking about	Can Claude see it	Why
A page in a teamspace you belong to	Yes	You can open it, so the tools can too
A colleague's private page	No	Your account cannot open it either
A teamspace you were never added to	No	Same rule, permissions are inherited from you
A page shared with you as view only	Yes to read, no to change	Write tools still respect the level you were granted
Content in Slack or Drive via Notion search	Only with Notion AI access	Notion documents this as a requirement of that tool
Everything at once, preloaded	No	Content arrives one tool call at a time

There is one more control worth knowing about if you are the person responsible for a company workspace. Notion documents admin settings that restrict which AI apps members may connect at all, gated to its Enterprise plan, so an admin can hold the connector list to an approved set.

A chat connector is the right tool when you are the one asking the questions. It is the wrong tool when the work should happen without you sitting there, which is the problem we set out to solve at Sistava. You hire an AI Employee, connect the tools it needs, and describe the job in plain English rather than driving every step of it yourself.

What this connection will not do

The honest limits are not bugs. They fall out of how the connection is built, and knowing them in advance saves you an afternoon of blaming the wrong thing.

It does not index your workspace in advance. Every answer is assembled from tool calls made during that conversation, so a badly titled page is a page that may never surface.
It cannot reach anything your own account cannot reach. If the answer lives in a private page belonging to someone else, the connector is not the fix, a sharing change is.
It is not built for whole workspace sweeps. Notion documents an average of three API requests per second per user across all tool calls, so asking it to walk hundreds of pages will be slow and may hit that ceiling.
It does not run when you are not there. Notion notes that the authorization flow is interactive, and the connector itself only acts inside a conversation you started.
It is described by Notion as suited to single player use rather than shared team workflows, so treat it as your personal reader and writer, not a team service.

None of that makes the connector less useful. It makes it a specific tool with a specific shape. Use it for reading, drafting and quick edits while you work, and reach for something scheduled when the job needs to happen on its own.

Frequently asked questions

FAQ

Do I need a paid Claude plan to connect Notion?

For the remote connector, yes. Notion's developer documentation states that remote MCP servers are not available on Claude's free tiers and lists the paid plans as the ones that support them. If you open the connector area and Notion is not offered, check your plan before you start troubleshooting anything else.

Can Claude edit my Notion pages or only read them?

It can do both. The published tool set includes creating pages with properties and content, and updating the properties of an existing page. Whether a specific edit succeeds still depends on the access level you hold on that page, since the tools inherit your permissions rather than granting new ones.

Why can it not find a page I know exists?

Three usual causes. The page may sit outside your own access, in which case nothing will surface it. The workspace approved during setup may not be the workspace the page lives in. Or the page title and content may simply not match the words you used, since search is doing real matching rather than reading your mind. Try giving it the page URL directly and see if fetching works.

Is my whole workspace being sent to the AI provider?

No. Content moves when a tool call asks for it, and what moves is the result of that call. There is no upfront copy of your workspace. That said, anything returned during a conversation does travel to the model handling that conversation, so treat sensitive pages with the same care you would apply to pasting them into a chat window.

How do I disconnect it?

Remove the connector from Claude and revoke the authorization on the Notion side. Doing both is the belt and braces version. Notion also documents admin controls on its Enterprise plan that let a workspace admin restrict which AI apps members are allowed to connect in the first place.

Is this the same as the enterprise Notion connection Anthropic documents?

No, and it is worth separating them. The enterprise route uses a Notion internal integration secret held by the agent rather than by a person, and Anthropic's documentation is explicit that nothing is reachable until you share specific pages or databases with that integration. It is a different trust model from the personal connector described here.

Sources

Notion Help Center, Connect AI tools with Notion MCP for what MCP is, the connection routes, the permissions statement and the admin controls.
Notion Docs, Connect to Notion MCP for the server endpoint, the Claude Code command, the OAuth requirement and the plan note.
Notion Docs, Supported tools for the tool list and the Notion AI requirement on connected tool search.
Notion Docs, Request limits for the average of three requests per second.
Anthropic, Connect Notion for the separate enterprise connection and its share before use requirement.

Connect it, ask one small question, then ask one small write. That order catches almost every setup mistake in under five minutes, and it stops you discovering the wrong workspace was approved three weeks later. Once the doorway works, the real question becomes what you want done through it. If the honest answer is that you want the work to happen while you are doing something else, a chat connector is the wrong shape and a hired worker is the right one. You can see how that looks on Sistava.