How to Use Claude and Notion Together

The most direct way to use Claude and Notion together is through the Notion MCP server. Once connected, Claude can read page content, search your workspace, query databases, and with the right authorization, create or update pages. The connection uses Notion's official integration API, so Claude acts as an authorized integration within the permissions you set.

Both Claude and Notion are tools where context matters. A decision you make in a Notion page can affect work Claude handles in a different tool, and vice versa. Tools like fenbs help with that gap: they keep the cross-tool decisions and next steps in one shared record any connected assistant can read, so you do not have to restate the project state every time you switch between apps.

The connection options between Claude and Notion

Notion publishes an official MCP server that wraps its integration API. You configure the server with your Notion integration token, connect it to your Claude environment from Integrations, and Claude gains tools for reading pages, searching content, and writing to authorized pages and databases.

An alternative path is an automation platform like Zapier or Make, which both have Notion integrations. You can build workflows where Claude produces output and the platform writes it to Notion, or where a Notion trigger passes content to Claude. This is less flexible for conversational use but practical for repeating, well-defined tasks.

For background on what Claude is and how MCP connections work in general, see the main overview.

Set up the Notion MCP server

To use the official Notion MCP server, create a Notion integration at notion.so/profile/integrations. Give it a name, choose the capabilities you want to allow (read content, update content, insert content), and save the integration token. Then connect the server to your Claude environment following the instructions in Integrations.

Notion uses a permission model where an integration only has access to pages and databases you explicitly share with it. After you create the integration, go to each Notion page or database you want Claude to access and add the integration as a connection from the page's settings menu. Claude cannot read anything you have not shared in this way.

That per-page sharing is also a useful boundary. Share only the pages relevant to the current project. If a page contains sensitive information that Claude does not need, do not share it with the integration.

Read a Notion database or page in Claude

Once the connection is live, you can ask Claude to read a specific page, search your workspace for content on a topic, or query a database. Claude receives the structured content — text blocks, database rows, linked pages — and can summarize, answer questions about, or draft follow-up content based on it.

Keep in mind that Claude reads what is in Notion at that moment. If you update a page after Claude has read it in a session, it will not automatically re-read it. For long sessions, ask Claude to re-read a page if you know it changed.

Ask Claude to update Notion records

With update permissions enabled in your integration, Claude can create new pages, add blocks to an existing page, or update database properties. You can ask it to draft a meeting summary and save it to a specific Notion page, add a row to a project database, or update a status property on a task.

Claude works with Notion's content model: it understands pages, databases, properties, and block types. When you ask it to add a table, a checkbox list, or a callout block, it constructs the appropriate API call. Complex formatting that requires precise layout may need manual adjustment after Claude writes it.

Review before Claude writes to Notion

A write to Notion is harder to undo than a change in a chat. Database properties have history in Notion's page history, but recovering deleted content requires Notion's restore features and, depending on your plan, may be limited. Before Claude writes anything, read what it proposes to write.

For important databases — project trackers, client records, content calendars — consider leaving Claude with read-only access and copying its output to Notion yourself. That stays safe when you are getting started. You can expand the access when you are confident the workflow produces the right output consistently.

Keep cross-tool decisions and next steps

Notion and Claude are often two parts of a larger workflow. A decision you make in a Notion page, or a task Claude identifies while reading one, may need to travel to a coding session, a calendar app, or a team discussion. Without a shared record, those cross-tool items get stranded in the app where they were created.

When Claude reads a Notion page that contains a decision or an action item, ask it to add that item to your project record in fenbs. The task then appears in Where we left off and is visible to any assistant you connect in any session, not just the one where you read the Notion page.

How to do this with fenbs

1. Create a free account and set up a project that corresponds to the work you are doing in Notion.
2. Connect the Notion MCP server to Claude from Integrations and share the relevant Notion pages with your integration.
3. In Decisions and rules, record which Notion pages Claude may read, which it may update, and which require your review before a write goes through.
4. When Claude reads a Notion page and identifies a task or decision, ask it to add that item to the fenbs project so it is accessible from any session.
5. Before each session ends, ask Claude to save progress in Where we left off so the next session — in Notion, in Claude, or anywhere else — starts from the current state.

fenbs does not replace Notion. It keeps the decisions, tasks, and context that connect your Notion work to the rest of your AI workflow. For related questions, see Notion MCP with Claude Code, Notion automations, and the guide on how to share Notion with Claude.