Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Notion to Claude Code

Let Claude create pages and update database rows in Notion. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Notion to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Notion, you add a Notion MCP server: a small hosted service that exposes Notion's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Notion account. No API keys pasted into config files.

claude mcp add --transport http notion https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Notion once connected?

Full read-write Notion access lets Claude create a page from a template, append and edit blocks, add or update database rows with the right properties, and adjust status or assignee fields. The note-taking and database upkeep that used to mean manual copy-paste happen directly inside the workspace, with your approval.

  • Create a new page from a template and fill in its sections
  • Append or edit blocks within an existing page
  • Add a row to a database with the correct properties set
  • Update a row's status, assignee, or date fields
  • Search across pages and databases, then propose structured edits
  • Archive a page once you confirm it is no longer needed

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Notion access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Notion API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Notion changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Notion connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Notion connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Notion account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Notion's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Notion?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Notion account it signs in with. Revoking access is one click in Notion.

More on the Notion connector

Notion connector for claude.aiAsana + Claude CodeMonday.com + Claude CodeClickUp + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us