Connect Notion to Claude AI with the MCP
Notion runs an official remote MCP server that plugs straight into Claude as a Connector, so Claude can read, search, create and edit pages in your workspace without you copying anything by hand. Most people should use the point-and-click OAuth connector below; a local, token-based server is there for setups that need it. Either way, Claude only ever sees the pages you explicitly share with it.
MCP is the open standard that lets Claude talk to outside tools. Notion's MCP server plugs into it, so once connected, Claude can search, read and — if allowed — edit your workspace, right inside the chat.
- No copy-paste. Claude reads and writes live Notion content.
- Scoped by page. Only pages you've explicitly shared are reachable.
- Two setups. A no-code OAuth connector, or a local server for on-machine control.
- Two-way. Summarize, draft, or update Notion pages straight from chat.
01Before you start
Two things need to be true before the connector will work at all:
- A Claude.ai plan that supports Connectors (Pro, Max, Team or Enterprise), or a current build of Claude Desktop — the free web tier does not expose the Connectors settings panel.
- Edit or admin access to the Notion workspace you want to connect, since sharing a page with the integration requires the same permission as sharing it with a person.
02Connect Notion to Claude
No code · OAuth · 2 minutesThis is the built-in, point-and-click path. It runs on Notion's own hosted MCP server, so there's nothing to install and no token to manage yourself.
-
Step 1. Open Connectors in Claude's settings.
In Claude.ai, click your profile icon → Settings → Connectors. In Claude Desktop, it's the same path from the app menu. You'll see a list of first-party connectors including Notion, Google Drive, and GitHub.
-
Step 2. Add Notion and sign in.
Click Add (or Connect) next to Notion. A popup opens Notion's own login and OAuth consent screen — you're authenticating directly with Notion, not handing Claude a password.
# nothing to type here — this step is entirely a browser popup Settings → Connectors → Notion → Connect -
Step 3. Choose which pages Claude can see.
Notion's consent screen lists your pages and databases with toggles. Turn on the ones you want Claude to read or edit — a whole workspace, a single project space, or just one database. You can come back and add more later from Notion's own Settings → Connections panel.
-
Step 4. Confirm and return to Claude.
Click Select pages then Allow access. The popup closes and Notion shows up as Connected back in Claude's Connectors list, with a toggle to turn it on or off per-conversation.
03Confirm the connection works
Test it in a fresh conversation before trusting it with real work:
- Click the tools icon in the message box (a plug or slider icon depending on platform) and confirm Notion shows tools like
search,fetch, ornotion-create-pages. - Ask directly: "Search my Notion for pages about onboarding." Claude should call the tool and return real page titles, not a generic answer.
- If nothing appears, re-check that at least one page is actually shared with the integration — an empty share list is the single most common cause of "it says connected but finds nothing."
04Things to actually ask Claude to do
Once it's live, the connector is most useful for the back-and-forth work that used to mean tab-switching:
- "Summarize the Q3 roadmap page and list what's overdue." — pulls the live page instead of a stale export.
- "Turn these meeting notes into a Notion page under Team Docs." — paste rough notes in chat, Claude formats and creates the page.
- "Update the status column to Done for the tasks I just described." — edits database properties directly, if you granted write access.
- "Compare what's in my Notion CRM against this list of leads." — cross-references a shared database against pasted or uploaded data.
05How this compares to other ways to link Notion
| Method | Setup | Live read/write | Needs code |
|---|---|---|---|
| Notion MCP connector | ~2 minutes, OAuth | Yes, both ways | No |
| Zapier / Make automation | Per-automation setup | One-way triggers, not conversational | No |
| Manual copy-paste export | None | No, always stale | No |
06Gotchas before you rely on it
- Access is opt-in per page, not per workspace. Connecting the integration grants nothing on its own — Claude only reaches what you or a teammate has explicitly shared, exactly like sharing with a guest.
- Write access is a separate decision from read access. Some workspace admins intentionally share pages read-only; check a database's connection settings if Claude reports it can't edit something you expected it to.
- Large databases get summarized, not dumped. Very large pages or databases may come back trimmed or paginated rather than pasted in full — ask Claude to filter or query a specific view instead of "give me everything."
07Quick answers
Do I need the Notion desktop or web app open for this to work?
No. The remote connector talks to Notion's servers directly over the OAuth connection, and the local server talks to Notion's API over your integration token — neither depends on the Notion app being open on your machine.
Can I connect more than one Notion workspace?
Only one Notion connection is active per Claude account at a time through the connector. To switch workspaces, disconnect from Claude's Connectors settings and reconnect with the other workspace's OAuth login.
Will Claude see private pages I haven't shared?
No. The connector is bound by Notion's own sharing model — a page that isn't shared with it is invisible to every tool call, regardless of what you ask Claude to search for.
What's the difference between this and Notion's built-in AI features?
Notion AI runs inside Notion on Notion's own models. The MCP connector runs the other direction — it lets Claude, wherever you're chatting with it, reach into Notion as a tool, which matters if Claude is already where you plan, code or write.
Primary sources
- Official developers.notion.com/docs/mcp — Notion's own MCP server documentation.
- Official modelcontextprotocol.io — the open MCP specification.
- Official docs.claude.com — Claude Desktop and Connectors setup documentation.
Get Trending AI Tips in Your Mailbox
Sign up and we'll send bite-sized MCP setup tips, trending AI workflows and new integration guides as they land, no fluff.
Sign up now!Takes 30 seconds · No spam