Notion and Claude: Every Way to Connect Them (October 2026)

There are two main ways to use Notion and Claude together: connect Notion to Claude (through the Notion connector in Claude.ai or Claude Desktop, or Notion MCP in Claude Code), or use Claude agents inside Notion itself. The first lets Claude search, read and edit your Notion pages from the Claude app; the second, in beta for Business and Enterprise plans as of October 2026, lets you assign tasks to a Claude agent without leaving Notion.

Below is how each option works, how to set it up, and which one fits what you’re trying to do. Notion and Anthropic both ship changes quickly, so treat menu names and plan details as accurate as of late October 2026.

The three ways Notion and Claude connect

There’s also a fourth, less visible link: Notion’s own AI features use Claude models among others. Anthropic’s Notion customer story says Claude powers parts of Notion AI such as writing, Autofill and Enterprise Search. That’s not something you set up; it’s just part of Notion AI.

Option 1: Connect Notion to Claude.ai or Claude Desktop

This is the route most people searching “notion and claude” want. Notion’s MCP help page lists Claude Desktop and Claude.ai as supported apps. Under the hood it uses Notion’s hosted MCP server, and sign-in happens through OAuth, so Claude only reaches what your Notion account can access and what you choose to share.

Steps

Based on Anthropic’s help article on connectors:

1. In Claude, open Customize > Connectors, or in a chat click + (or type ”/”), hover over Connectors and choose Manage connectors.
2. Click + next to Connectors to browse the directory and pick Notion.
3. Click Connect and sign in to Notion in the window that opens.
4. Choose which pages or workspace Claude can reach and approve access.
5. In a conversation, use the + menu to make sure the Notion connector is toggled on.

Once connected, you can ask things like “Find our Q3 planning doc and summarise the open decisions” or “Create a meeting notes page under Projects with these action items.”

Plans

Anthropic’s help center says pre-built web connectors are available to all users on Claude, Claude Desktop and the mobile apps, and that custom remote MCP connectors are available on every plan, with free users limited to one custom connector. Several third-party guides say the Notion connector requires a paid plan. The sources disagree here, so check the directory in your own account.

For Team and Enterprise

On Team and Enterprise plans, an Owner or Primary Owner has to add the connector first in Organization settings > Connectors (“Browse connectors”, then “Add to your team”). Enabling it doesn’t connect anyone automatically; each person still signs in to Notion themselves. Owners can also set org-wide tool permissions (Always allow, Needs approval, Blocked).

Notion’s help center also describes enterprise-managed connections, where an Okta admin sets up Claude’s access once for the team. It says this is currently available for Claude on Enterprise plans using organization connectors and needs an Okta admin, a Notion organization owner and a Claude admin.

Option 2: Use Notion MCP in Claude Code

If you write code and keep specs, tickets or docs in Notion, you can wire Notion into Claude Code directly. Both Notion’s developer docs and the Claude Code MCP docs give the same command.

1. In your terminal, run:

   claude mcp add --transport http notion https://mcp.notion.com/mcp
   

2. Start Claude Code and run /mcp.

3. Follow the browser prompt to log in to Notion and grant access.

4. If the browser doesn’t open, copy the URL Claude Code shows and open it manually.

A few useful details from the Claude Code docs:

• By default the server is added with local scope (just you, just this project). Add --scope user to make it available in all your projects, or --scope project to write it to a shared .mcp.json your team commits.
• Tokens are stored and refreshed automatically. Use Clear authentication in the /mcp menu, or claude mcp logout notion, to revoke access.

Notion also maintains an older, self-hosted open-source MCP server that uses an integration token, but reporting on it indicates Notion is prioritising the hosted server. Unless you have a specific reason, use the hosted mcp.notion.com endpoint.

Option 3: Claude agents inside Notion

The newer direction is running Claude agents in Notion itself. Per Notion’s help page Use Claude agents in Notion, as of October 2026:

• The feature is in beta and available on Business and Enterprise plans.
• Agents are hosted by Notion. They run on Notion credits charged per run, and you don’t need your own Anthropic account or API key (and can’t use one).
• An agent can answer questions and create or edit pages, and it only sees what you share with it.
• For Enterprise and HIPAA workspaces, Claude agents are off by default; a workspace owner turns them on under Settings > Notion AI > Agents > Manage external agents. Admins switch them off in the same place.

Creating one

1. In the Notion sidebar, go to Agents.
2. Choose New Agent, then Claude.
3. Start from a template or build from scratch, and share the pages the agent needs.

Notion’s guides describe using Claude agents on a team task board, where some templates connect to GitHub so the agent can read repos and open pull requests. Anthropic’s customer story says this is built on Claude Managed Agents: you move a task to a “ready to start” state and Notion kicks off a Claude session that draws on connected pages and docs.

Cost

Notion says tasks with more steps, more reading or more tool use cost more credits. Its credit help pages describe Business and Enterprise seats getting monthly Standard and Select credits, with new workspaces moving to the new credit system from October 19, 2026 and existing workspaces from November 2, 2026. Check your credits dashboard before rolling agents out widely.

What changed in October 2026

Two Notion announcements this month are likely behind the spike in searches:

• October 13 release: Notion redesigned its Connections settings. Admins can see who connected each AI tool and when it was last used, revoke one person’s access without affecting others, and allow only Notion-verified tools or a specific list (release notes).
• October 19 announcement: Notion’s “Agents, rebuilt to do more for less” post covers an overhauled Notion MCP that connects agents including Claude to Notion, agents that can work on tasks for up to 24 hours, a new credit system, and an upgraded “Auto” model router. Notion’s own claim is that Auto matched results from top models at much lower cost; that figure is Notion’s and hasn’t been independently verified.

Which option should you pick?

• You live in Claude and want it to know your notes: use the Notion connector in Claude.ai or Claude Desktop.
• You’re a developer: add Notion MCP to Claude Code so specs and docs are a prompt away.
• Your team plans work in Notion and wants to delegate tasks: try Claude agents in Notion, if you’re on Business or Enterprise and can live with beta features and credit-based billing.

Privacy and access tips

• Share only the pages Claude actually needs during the OAuth step; you can widen access later.
• On Team or Enterprise, admins should review connected tools in Notion’s Connections settings and set tool permissions in Claude.
• If you disconnect, revoke access on both sides: clear authentication in Claude, and remove the connection in Notion’s settings.