How to Connect Claude to Notion with MCP (2026 Guide)

You ask Claude to sort out your week. It gives you a clean answer. Then you spend six minutes moving that answer into Notion by hand — one task at a time, one project property at a time. Do that twice a day and the assistant costs you more time than it saves.

MCP — the Model Context Protocol — is the piece that closes the loop. It gives Claude a direct, permissioned connection to your Notion workspace: it can search your databases, read a project page, and create or update tasks without you touching the keyboard.

Think of MCP as a standard plug. Before it, every AI-to-tool connection was a custom integration. With it, a tool publishes one server and any MCP-capable client — Claude desktop, Claude Code, and a growing list of others — can talk to it. Notion publishes an official MCP server. That is the whole story.

Two practical consequences. First, you grant access at the page level, not the workspace level — Claude sees only what you share with the integration. Second, the connection is live: Claude reads the current state of a database every time it needs it, not a snapshot you pasted an hour ago.

• A Notion workspace where you can create integrations (owner or admin).
• A paid Claude plan — the connectors live in Claude desktop and Claude Code.
• One database you actually use for tasks. Do not build a new one for this; connect the messy real one.

1. 1Open Notion → Settings → Connections → Develop or manage integrations.
2. 2Create a new internal integration, name it something you will recognise later (for example «Claude»).
3. 3Under capabilities, enable read, update, and insert content. Leave user information off unless you need it.
4. 4Copy the internal integration secret and keep it somewhere safe — you paste it once, in the next step.

This is the step people skip, and then wonder why Claude says it cannot find anything. An integration starts with access to nothing. Open your task database, use the page menu → Connections → add your integration. Do the same for your projects database and any page you want Claude to read.

In Claude desktop, open Settings → Connectors and add the Notion connector; you will be asked to authorise the workspace. In Claude Code, add the server from the command line with the Notion MCP endpoint and your integration token. Either route ends in the same place: Claude lists Notion tools when you start a conversation.

Verify it before you build anything on top. Ask Claude: «List the databases you can see in Notion.» If it names your task database, the connection is real. If it returns nothing, go back to step 2 — it is almost always sharing, not tokens.

Claude can read your properties, but it cannot guess your conventions. Write a short brief and keep it in a Claude Project so it applies to every conversation:

• Which database is tasks, which is projects, how they relate.
• The exact property names and allowed values — «Status: Inbox / Next / Waiting / Done», not «status: open or closed».
• Your defaults: every new task gets a project, an energy level, and a status of Inbox.
• What Claude should never do — for example, never mark something Done, only you do that.

Morning: «Read my task database. Show me what is still Waiting from last week, then give me three tasks for today based on my deadlines.» Claude reads, filters, and answers in your own vocabulary.

Midday brain dump: you talk for ninety seconds about four different projects. Claude splits it into tasks, assigns each to the right project, and writes them into Notion as Inbox items. You review the list once instead of typing eleven rows.

End of day: «What did I not get to, and what is now blocking someone else?» The answer is the only status update you need to send.

• Large databases get truncated. Filter before you ask — «tasks with status Next» beats «all tasks».
• Formula and rollup properties are read-only. Claude can see them, not set them.
• It will happily create duplicates if you dump the same notes twice. Keep an Inbox status and review it.
• Notion AI is separate and billed separately at roughly $20 per member per month. MCP does not replace it — see the comparison below.

Once the connection exists, the interesting work is not the plumbing — it is the instructions. That is what Claude Skills are for: reusable briefs that turn «plan my week» into a repeatable procedure. That is the next article.