Skip to content

Workflow guide

How to Connect Notion to Claude—and Turn Research Pages into a Sourced Brief

Add Notion from Claude’s connector settings, sign in to the right workspace, check one known page, then build a sourced brief in chat before anything is written back to Notion.

By Christian Stewart, Founder and EditorPublished 28 Oct 2026Documentation reviewed 28 Oct 2026

Research in Notion tends to pile up in pieces: an interview page, a competitor scan, a half-finished project brief, a page of links someone meant to summarize. Asking an assistant to “summarize what we know” across them is risky, because the answer can blend what a page says with what sounds plausible.

Claude can reach Notion through Notion MCP, Notion’s hosted server for AI apps. The habit that makes it useful is simple: choose the pages, make Claude quote and link them, and keep its own reasoning visibly separate from the evidence.

This walkthrough uses Claude’s remote connector settings in the web and desktop apps. Product claims were checked against five official Anthropic and Notion pages on October 28, 2026. AI assisted the research and writing. The prompts and fictional example are Connector Scout editorial recommendations, not results from hands-on testing.

Quick answer

In Claude, open Customize > Connectors, add Notion, and complete Notion’s sign-in for the workspace that holds your pages. On Team and Enterprise plans an Owner must first add the connector for the organization; each person still signs in unless Enterprise-managed auth is used. Notion MCP acts with your existing Notion permissions. Check one known page first. The four prompts below read and draft in chat; asking Claude not to write is an instruction, not a permission setting. (Anthropic on Claude connectors; Notion’s MCP help page)

Setup path
Customize > Connectors → add Notion → sign in to Notion
Access
What your Notion account can already open, within admin and tool limits
Writes
Notion MCP has write tools; what you can use depends on the connection, tool permissions and admins

The walkthrough ends with your review and anything you choose to save to Notion yourself. Installation and prompts are not substitutes for checking the workspace, permissions and the pages themselves.

Connect Notion in Claude’s connector settings

Anthropic says web connectors are available to all users on Claude, Cowork, Claude Desktop and Claude Mobile, and treats a cloud service like Notion as a remote connector, so you do not need the desktop-extension route. Notion lists Claude.ai and Claude Desktop among the apps that work with Notion MCP. (Anthropic on Claude connectors; Anthropic on remote vs desktop connectors; Notion’s MCP help page)

  1. Open Customize > Connectors in Claude, or open the + menu in a chat, hover over Connectors and choose Manage connectors.
  2. Select + next to Connectors and find Notion in the list.
  3. Review its description and capabilities, then select Connect.
  4. Sign in to Notion and approve access for the workspace that holds your pages.
  5. In a chat, open + > Connectors and turn Notion on for that conversation.

Installing connectors on mobile is in beta; web and desktop remain the main path. If you belong to several Notion workspaces, approve the one with the pages you need. Notion’s setup guide says the connected client can read and update content you can access in the selected workspace. (Anthropic on Claude connectors; Notion’s MCP setup guide)

If Notion is not in the list you see, you can add it as a custom web connector with Notion’s hosted URL, https://mcp.notion.com/mcp. In Customize > Connectors, choose Add > Custom > Web, name it and paste that URL, then follow the sign-in prompts. Free plans are limited to one custom connector. The Notion setup page also shows terminal commands for Claude Code and other coding tools; those are not needed for Claude chat. (Anthropic on Claude connectors; Notion’s MCP setup guide)

Team, Enterprise and Notion admin controls

On Claude Team and Enterprise plans, an Owner or Primary Owner has to add a connector for the organization (Organization settings > Connectors) before members can use it. That makes it available, but each person still authenticates individually. The exception is Enterprise-managed auth, in beta for Team and Enterprise, where a connector is authorized once for the organization. Members who cannot add a connector may be able to request one; requests are on by default on Team and off by default on Enterprise. (Anthropic on Claude connectors)

Claude Owners can also set tool permissions for a connector across the organization. Each permission category or tool can be set to Always allow, Needs approval or Blocked, so an organization can allow reading while blocking writes. These settings only narrow access: a person still needs the underlying Notion permission to make any change. (Anthropic on Claude connectors)

Notion has its own layer. On the Notion Enterprise plan, workspace owners can restrict which AI apps members may connect to an approved list (Settings > Connections > Permissions). Notion blocks calls from apps not on that list, even if an old connection still appears. Enterprise workspaces can also use enterprise-managed connections through their identity provider. Notion guests cannot connect Notion MCP; only workspace members can. (Notion’s MCP help page; Notion’s MCP setup guide)

The separate checks behind a working Notion connection in Claude

Claude organization (Team or Enterprise)

What it controls
Whether an Owner has added Notion for members

Your Notion sign-in and workspace

What it controls
Which workspace Claude reaches, as you

Notion page permissions

What it controls
Which pages your account can open; MCP does not add access

Notion Enterprise approved-apps list

What it controls
Whether Claude is allowed to connect to that workspace

Claude tool permissions

What it controls
Whether each tool is allowed, needs approval or is blocked

Notion plan

What it controls
Some search filters, connected-source search, SQL query limits and request limits

What Notion MCP can read and change

Notion says MCP tools act with your full Notion permissions: they can reach everything you can, and nothing you cannot, within any admin and tool limits on the connection. Naming pages in a prompt sets the scope you are asking for; it is not a permission boundary. (Notion’s MCP help page)

Notion’s tool list includes reading tools, such as searching, fetching a page or database and reading comments, and tools that change content: creating and updating pages, moving and duplicating them, creating databases and views, adding comments, and moving pages to Trash. Workspace-owned connections show only the tools an admin selected. Do not assume your Claude connection exposes every tool on Notion’s list; ask Claude which Notion tools it can see. (Notion’s MCP tool list)

Plan matters too. Notion MCP works on every Notion plan, but some search filters, such as last edited by and last edited date, need Business or Enterprise. Searching connected sources such as Slack or Google Drive through Notion needs Business or Enterprise with Notion AI, and request limits are higher on those plans. Every tool call counts toward Notion’s request limits. (Notion’s MCP setup guide; Notion’s MCP tool list)

Check one page you already know

Pick a non-sensitive page you can open in Notion right now, with a distinctive title and a detail you remember. Notion recommends descriptive page titles, because AI apps rely on them to understand your content. (Notion’s MCP help page)

Prompt 1: Check one known Notion page
Use the Notion connector. Find the page titled [page title] in the [workspace name] workspace. Tell me its exact title, its parent page or database if you can see it, and its last-edited date if that is available. Quote one short sentence from it word for word and give me the page link. If you find a similar page but not this one, say so instead of guessing. Also list which Notion tools you can see in this conversation. Only read; do not create, edit, move or comment on anything.

Open the page yourself and compare the quote. If Claude cannot find it, confirm Notion is turned on for the chat, that you signed in to the same workspace, and that your account can open the page. Notion suggests disconnecting and reconnecting when sign-in fails. (Anthropic on Claude connectors; Notion’s MCP setup guide)

Gather a bounded set of research pages

Search can miss pages, and broad requests encourage confident filler. Name the pages, or a parent page and date range, so you can compare the pages Claude actually read with the set you requested. This structure is our recommendation, not a Claude or Notion feature.

Prompt 2: Gather a bounded set of notes
Use the Notion connector. Read only these pages: [page links or titles], plus any pages directly under [parent page] edited since [date]. For each page, give me its title, link, last-edited date if visible, and three to five key points in its own words, with one short quote. Then list: - pages you tried to open but could not, - pages that look relevant but were outside the set I gave you. If you cannot apply the parent-page or last-edited constraint, tell me which constraint is unavailable or was dropped and ask before widening the search. Do not search beyond this set without asking, and do not change anything in Notion.
Prompt 3: Separate facts, inferences and conflicts
Using only the pages you just read, sort the findings into three lists: 1. Page facts: statements a page makes directly, each with the page link and a short quote. 2. Inferences: conclusions you draw from more than one page or from indirect clues. Label each [inferred] and explain the reasoning. 3. Conflicts: places where pages disagree on dates, numbers, owners or decisions. Quote both sides and name both pages. If something matters for the brief but no page states it, write [not found]. Do not fill gaps from general knowledge, and do not change anything in Notion.

A fictional example

This is an illustration with invented pages, not a real result. Each row keeps what a page says apart from what it suggests and what is still missing.

Fictional research brief: page evidence, interpretation and gaps

Interview notes, 6 Oct: “Three of five customers mentioned slow exports.”

Reasonable interpretation
Export speed may be a common complaint in this sample
Gap
Five interviews are not a representative sample; no usage data was read

Competitor scan: “Rival A added scheduled exports in Q3.” Project brief: “No competitor offers scheduled exports.”

Reasonable interpretation
The pages conflict about scheduled exports
Gap
Which claim is correct; neither page links current primary evidence

Project brief: “Target launch: November.” No owner field filled in.

Reasonable interpretation
A November target exists
Gap
Who owns the launch and whether the date is agreed

The middle column is where briefs drift. “Exports are the top complaint” sounds like a finding, but the pages only show what a few people said in interviews.

Draft the brief in Claude first

Prompt 4: Draft a sourced brief in chat
Using only the facts, inferences and conflicts above, draft a one-page brief for [audience] about [topic], under 400 words, here in this chat. - Key facts, each with its page link. - Open conflicts, with both pages and who might resolve them. - Inferences, kept labelled [inferred]. - A short “Not covered” line naming pages or questions you did not check. After the draft, suggest a page title and where in Notion it could go, but do not create, update or move any Notion page.

Review the draft against the original pages before it goes anywhere. On Team and Enterprise plans, connectors work only in private projects. (Anthropic on Claude connectors)

Later, you may want Claude to save the brief as a Notion page. Notion MCP includes a page-creation tool, but whether your connection exposes it, and whether it runs without asking, depends on your tool permissions, organization settings and Notion access. Our recommendation: when you are ready, name the exact parent page, give Claude the final text, and set that tool to Needs approval so you review the action before it runs. Creating a page is not the same as setting up a recurring template, automation or button; configure those in Notion. (Notion’s MCP tool list; Anthropic on Claude connectors)

When Notion is connected but a page is missing

Troubleshooting Notion in Claude

Notion is not in your connector list

Next check
On Team or Enterprise, ask an Owner to add it or use Request; otherwise add it as a custom web connector

Claude does not use Notion

Next check
Turn Notion on in + > Connectors for this chat

A page you know is not found

Next check
Open it in Notion with the same account; give Claude the exact title or link

Sign-in fails or keeps repeating

Next check
Disconnect and reconnect in Customize > Connectors; check Notion’s approved-apps list if you are on Notion Enterprise

A message says you are a guest

Next check
Notion MCP is for workspace members; ask a workspace owner about membership

A tool is missing or blocked

Next check
Check the connector’s tool permissions, your Notion plan, and admin tool selection

Rate-limit errors

Next check
Ask Claude to make fewer parallel calls, or try again later

Connecting never adds Notion permissions you did not already have. Restricting tools in Claude only narrows what the connector can do. (Anthropic on Claude connectors; Notion’s MCP help page)

Disconnecting and where your data goes

To stop using Notion, open Customize > Connectors, select Notion and disconnect it. Content Claude retrieves goes into your conversation and is handled under Anthropic’s terms; Notion processes requests on its own infrastructure under its own terms. On Notion Enterprise, a workspace owner can disconnect all MCP connections at once with Disconnect All Users; there is no option to disconnect every user from one specific app. (Anthropic on Claude connectors; Notion’s MCP help page)

On Notion Business and Enterprise with Notion AI, an app connected through Notion MCP may also search sources connected to Notion, such as Slack or Google Drive, within what your own connection can see. That content then goes to Claude. Check what is connected to Notion before running broad searches. (Notion’s MCP help page)

For the connection itself, see the Claude + Notion record. If you use ChatGPT instead, the ChatGPT Notion setup guide covers its separate Notion app, and our MCP comparison explains how connectors and MCP servers differ.

Connector Scout is independent. It is not affiliated with, endorsed by or sponsored by Anthropic or Notion, and this guide contains no sponsored or affiliate links.

Sources

  1. [1] Anthropic, Use connectors to extend Claude's capabilities
  2. [2] Anthropic, When to use desktop and web connectors
  3. [3] Notion, Notion MCP
  4. [4] Notion, Get started with Notion MCP
  5. [5] Notion, Notion MCP supported tools

Accessed and reviewed 28 Oct 2026.