Claude Code Club

Claude Code + Notion Integration

Give Claude Code access to your Notion workspace through the Notion MCP server so it can read docs, query databases, and draft pages in context.

By David Iya - Updated 2026-08-04

Your specs, roadmaps, and notes live in Notion, but Claude Code cannot see them, so you keep pasting context into the chat by hand. Connecting Notion through MCP lets Claude read the relevant page or database directly and write back a draft, keeping the project's source of truth and the build in the same loop.

Before you start

  • The Claude Code desktop app installed and signed in.
  • A Notion account with a workspace you can create an integration in.
  • A Notion integration token, and the specific pages or databases shared with that integration.

What it unlocks

Claude reads the real spec

Instead of pasting a doc into chat, point Claude at the Notion page so it builds against the actual requirements, not a stale copy.

Query databases in place

Ask questions against a Notion database - open tasks, roadmap items, content calendar - and let Claude filter and summarize without you exporting anything.

Draft back into Notion

Have Claude create or update a page - a summary, a checklist, meeting notes - so the workspace stays current as the work happens.

How to connect Notion

1

Create a Notion integration

In Notion, open Settings then Connections then Develop or manage integrations, create a new internal integration, and copy its token.

2

Share the pages you want Claude to see

Notion integrations only see what is explicitly shared with them. On each page or database, use the connection menu to grant your new integration access.

3

Add the Notion MCP server to Claude Code

Register the Notion MCP server with Claude Code and pass your integration token. Use the command below as the shape; keep the token out of any committed file.

claude mcp add notion
4

Confirm the tools appear

Restart Claude Code and ask it to search your Notion workspace. If the Notion tools are listed and a search returns a shared page, the connection is live.

Spec in Notion, code in Claude

  1. Share the spec page

    Grant the Notion integration access to the feature's page so Claude can read it.

  2. Build against it

    Ask Claude to read the page and implement the described behavior in your project.

  3. Write the summary back

    Have Claude append a short 'what shipped' note to the same Notion page.

What people build with it

Build straight from the spec

Share the feature's Notion page with the integration and ask Claude to implement it, so the code matches what the doc actually says.

Summarize a messy database

Turn a sprawling tasks database into a short 'what is open and what is blocked' readout you can act on.

Keep docs current automatically

After a change, have Claude write the updated notes back to the relevant Notion page instead of letting the doc drift.

Commands & configuration

Register the Notion MCP server

claude mcp add notion

Supply your Notion integration token via the server's configured environment, not inline in the repo.

List configured MCP servers

claude mcp list

Use this to confirm the Notion server registered before you try to use it.

Prompts to steal

Build from a Notion spec

Search my Notion for the page titled with this feature name, read it in full, list the acceptance criteria you found, then implement them in this project. Ask me before making any assumption the doc does not cover.

Summarize an open-tasks database

Query my Notion tasks database, then give me a short readout of what is in progress, what is blocked and by what, and the three things most worth doing next.

Recommended MCP servers

  • Notion MCP server

    Exposes search, page read/write, and database query as tools so Claude can work directly against your workspace.

Skills worth having

  • Single source of truth

    Keeping one canonical doc per feature so Claude - and your teammates - always build against the same version.

Troubleshooting

Keep it safe

  • Share only the pages Claude needs, not your whole workspace. The integration can touch everything you grant it.
  • Keep the Notion token out of committed files and out of chat history. Load it from the MCP server's environment.
  • Rotate the token if you ever paste it somewhere it should not be, the same way you would treat a leaked password.

Notion + Claude Code: FAQ

Does Claude Code get access to my entire Notion workspace?

No. It sees only the pages and databases you explicitly share with the integration you created, which keeps the blast radius small.

Do I need to code to connect Notion?

No. You create an integration in Notion's settings, share a few pages, and register the MCP server in Claude Code. No programming is required to wire it up.

Can Claude write to Notion or only read?

It can do both when the MCP server exposes write tools - creating pages, appending content, and updating databases - as long as the integration has edit access to those pages.

More integrations

Turn Notion + Claude into a real workflow

Connecting the tools takes minutes. Building a system where your docs and your code actually stay in sync is what the club is for.

Join the club See the curriculum

Related: what is Claude Code, glossary, and use cases.