Guides · Claude & Notion

How to connect Claude to Notion. Two ways, step by step.

One takes two minutes and no code. The other takes ten minutes and a config file, and gives you more control. Most guides only show you one. Here is both, plus what to do when the connection quietly breaks.

Level Beginner
Read time 7 min
You need A Notion workspace + a Claude account

Most people trying to connect Claude to Notion hit the same wall: they find a tutorial for the manual setup, get lost in a config file they have never seen before, and give up before Claude ever reads a single page. That got easier in July 2026, when Notion shipped native External Agents support, with Claude as one of the first two agents available. You may not need the config file at all.

01Pick your method

Both methods end in the same place: Claude can read (and in some setups, write to) your Notion workspace. They differ in where the connection lives.

Fastest

Native connector

Built into Notion since version 3.6. A toggle in Settings, no code, no terminal. Best if you use Claude.ai or Notion's own AI features day to day.

Most control

Manual MCP setup

A small config file and an integration token. Works with Claude Desktop and Claude Code specifically, and lets you scope exactly which pages Claude can reach.

02The native connector

In Notion, go to Settings → Notion AI → Agent → Manage external agents. Claude appears as one of the available agents. Authorize it, then choose which pages or databases it can see. That's the entire setup. No file to edit, nothing to install.

Good to know

This path is newer than most tutorials online, which is partly why so few of them mention it. If your Notion plan or workspace doesn't show this menu yet, it hasn't rolled out to you and Method 2 below is your only option for now.

03The manual MCP setup

This is the version most existing tutorials cover, and it's still the right call for Claude Desktop or Claude Code, or if you want narrower control over exactly what Claude can reach.

Step 1. Create an internal integration at notion.so/my-integrations. Name it something you'll recognize later ("Claude access" is fine), and copy the integration token it gives you.

Step 2. Open the specific Notion page or database you want Claude to see. Click the ··· menu in the top right, choose Connections, and add the integration you just created. Notion only shares what you explicitly connect, page by page.

Step 3. Point Claude at Notion's MCP server. In Claude Code, the fastest way is the CLI:

Shell · Claude Code
# adds Notion's hosted MCP server to Claude Code
claude mcp add notion --transport http https://mcp.notion.com/mcp

If you're on Claude Desktop instead, add the same server to your config file directly:

JSON · claude_desktop_config.json
{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.notion.com/mcp"]
    }
  }
}
Before you paste this

Both Claude and Notion ship changes weekly. The command shape above is correct as of this writing, but confirm the exact server URL against Notion's own current docs (notion.com/help/use-claude-agents-in-notion) before you rely on it, especially if it's been more than a few weeks since you read this.

04Test the connection

In Claude Code, run /mcp and confirm Notion shows up as connected. In Claude Desktop or Claude.ai, just ask it directly: "What Notion pages can you see right now?" If it lists the page you shared in Step 2, you're done.

05When it doesn't connect

This integration has a few known rough edges. If you hit one of these, it's not something you broke.

Stuck

OAuth hangs on "Connecting..." Close the auth window, revoke the connection in Notion's integration settings, and reconnect from scratch rather than retrying the same window.

Vanishing

Notion tools disappear after the first prompt. A known session issue in some Claude clients. Restarting the client (not just the conversation) reliably brings the tools back.

Read-only

Claude can read pages but won't create or edit them. Expected in some configurations, not a bug: the native connector is currently stronger at reading than writing. For reliable writes, pair it with an automation tool (Zapier or Make) rather than expecting Claude alone to write back.

None of these mean you set something up wrong. They're documented, active issues on Anthropic's and Notion's own trackers as of this writing, not signs you missed a step.

Also in Guides

Claude Skills, explained (and how to install your first one) →

Back to Notes & Guides →

The Operator Kit

Once Claude can see your workspace, the next question is what to have it do.

Twelve Claude skills built from real studio work, including the ones that turn a connected workspace into an actual content and email system. See the Operator Kit.