Guide
Notion's shared brain for ChatGPT and Claude: what launched, how to set it up, and what it doesn't cover
On 4 November 2026 (5 November in Japan), Notion announced what it calls one shared brain for AI agents: ChatGPT, Claude and other agents connected to your Notion workspace save what they learn to one private Memories database and use the same Notion skills. Most of the pieces shipped between mid-September and 30 October; what's new is a one-click setup link for ChatGPT and for Claude that opens Notion's setup prompt (first published 30 September), which teaches each AI to check Notion first. It suits people who already keep their work in Notion and switch between AIs. The memory is per person: a team shares skills and pages, not memories.
Short answer
- What it is: Notion's MCP server plus a setup prompt. Each AI you connect reads and writes your Notion memories and loads your Notion skills.
- New on 4 November: the links ntn.so/chat and ntn.so/claude, the launch thread and the CEO's essay. Memory sync went live on 19 October; skill tools over MCP were documented by 18 September.
- Who it's for: Notion users who work in more than one AI.
- What it isn't: a memory your team shares. Each person's memories are private to them.
What launched
Notion's post on X at 19:14 UTC on 4 November said ChatGPT, Claude, Muse and Bot "can save what they learn to the same memory" and use the same skills in Notion. The thread gave two links: ntn.so/chat for ChatGPT and ntn.so/claude for Claude. Each opens the AI with one sentence already typed, asking it to set up Notion as your "context system" with Notion's guide at developers.notion.com/
Notion's release notes have no entry for 4 or 5 November, and its blog has no launch post. The details live in Notion's help center, its developer docs, and the setup guide itself (version 0.0.6, published 30 October).
What's actually new, and what shipped earlier
| Date (2026) | What shipped |
|---|---|
| 20 March | Custom skills for Notion AI, on Business and Enterprise |
| 18 August | Notion's engineers open-source Lore, a team memory for agents stored in Notion |
| 15 September | Notion 3.7: a skills library; skills download as SKILL.md files to Claude Code, Codex, Cursor, Gemini and Grok |
| 17 September | Skills API; Notion says agent apps can upload and edit skills over MCP |
| By 18 September | Developer docs for using Notion skills over MCP are online (Wayback Machine copy) |
| 30 September | Setup prompt 0.0.1 and 0.0.2: import memories and skills, the Agent Operating Guide, a daily routine |
| 13 October | Notion 3.8, "Context for your agents": any MCP agent, admin controls; setup prompt 0.0.4 has agents fetch enabled skills every session |
| 19 October | "Agents, rebuilt": memory sync goes live, "with skills via MCP coming soon" |
| 29–30 October | Setup prompt 0.0.5 and 0.0.6: one step at a time, a two-choice card, click paths for Claude and ChatGPT |
| 4 November (US), 5 November (Japan) | Launch thread, the CEO's essay, one-click links for ChatGPT and Claude |
So the launch is mostly packaging and distribution, built on parts that shipped over the previous seven weeks. Even the headline phrase already headed a section of the setup guide on 30 October. One line doesn't fit: the 19 October note called skills over MCP "coming soon", a month after Notion documented its MCP skill tools. Notion hasn't said what that referred to. One creator on X called the launch "more of a framework rather than a set of new features" (@temnco).
What memory and skills are in Notion now
Memory: a private database for each person
Your memory is a Memories database plus an About page that summarizes it, both created when the first memory is saved. Each memory has a type: Profile, Preference, Work, People or Notes. It's the same database Notion Agent uses inside Notion, so Claude, ChatGPT, Claude Code or Codex add to the same place. To see it, open Settings, then Notion AI, and under Memory find Saved memories.
- Private to you. Memories don't give an agent access to anything you can't already see.
- Searched, not loaded whole. An agent searches your memories and gets the best matches: 10 by default, 50 at most.
- Only through your own sign-in. The memory tools appear on a connection where you signed in to Notion yourself, with memories turned on for you and for your workspace. A workspace owner can turn them off for everyone.
- No history import. Connecting an AI doesn't bring over another app's chat history, Notion's developer docs say.
Skills: Notion pages in the SKILL.md format
A Notion skill is a page marked as a skill, with a Description and a Files field. Teams keep them in a Skills database, where every new page becomes a skill; the Library's Skills tab gathers them in one view. Skills follow the open Agent Skills format: downloading one gives a SKILL.md with its files, and uploads take the same format. Because a skill is a page, it follows page permissions and page history, and teammates can comment and suggest edits.
Skills leave Notion three ways: connected agents load them over MCP in every session; an admin can sync them to GitHub every hour; or the desktop app sends a copy to a local agent such as Claude Code, Codex or Cursor, and that copy is marked out of date when the skill changes.
- 200 skills turned on per person, and 50 loaded per connected agent per session.
- The MCP tool that lists your enabled skills returns 30 at most, with no next page, so a team with more has to choose.
- An uploaded skill can be 20 MiB compressed, with a SKILL.md of up to 200,000 bytes.
How to set it up in Claude
- Add Notion to Claude. Open Notion's page in Claude's connector directory, select Add to Claude, and sign in to Notion. Use the same Notion account and workspace in every AI you connect: memories are shared only across those.
- Open ntn.so/claude. It starts a new Claude chat with Notion's setup sentence typed in. Send it. The link doesn't add the connector, which is why step 1 comes first.
- Confirm the connection. Claude asks you to sign in to Notion if it needs to, then names you and your workspace.
- Pick a setup. Claude shows two choices. Shared context layer (Recommended) lets it create a private guide page and save your memories, work and skills to private Notion pages without asking each time. Basic setup creates only the guide and the custom instructions. Either way, Claude saves your choice as a Notion memory.
- Paste the custom instructions. Claude creates a private page called Agent Operating Guide and shows a block of text to copy. Click your name in the bottom left, then Settings, then Account, and paste it into "Instructions for Claude".
- Answer the rest. With the shared context layer, Claude offers a daily check if your app can run scheduled tasks (it asks for a separate yes), then saves what it can already see: memories, recent work and installed skills, to private pages. Notion's guide rules out passwords, secrets and chat transcripts. It asks before putting anything in a shared or team space.
- Read the summary. Claude fills in the guide with where your memories, skills and documents live, and gives you the link.
How to set it up in ChatGPT
- Open ntn.so/chat. By its address, it opens Notion's plugin page in ChatGPT with the setup sentence passed along. Add Notion and sign in to Notion.
- Send the setup sentence and confirm the connection: ChatGPT names you and your workspace. If no sentence was typed in for you, start a new chat and paste: "Help me set up Notion as my context system using this guide: developers.notion.com/
prompts/ setup". - Pick Shared context layer or Basic setup on the card ChatGPT shows.
- Paste the custom instructions. Click your photo or initials in the bottom left, then Personalization, scroll down to "Custom instructions", and paste the text.
- Answer the rest as in Claude: the optional daily check, then what to bring over.
Notion doesn't say which ChatGPT plans can add its plugin, or whether the plugin can save memories on each plan; its help page names ChatGPT Pro among popular apps. Try it on your own plan before you plan a team rollout around it.
Other AIs
In any other AI that connects to MCP servers, connect Notion from the app's connector list or with the address https://mcp.notion.com/mcp, then paste: "Help me set up Notion as my context system using this guide: developers.notion.com/
What the pasted instructions tell your AI
The setup works because of the text you paste, not the connection alone. Notion's Nathan Baschez wrote on launch day that agents "often don't think to look in Notion" unless you prompt them. The pasted text tells each AI to:
- read your Agent Operating Guide once per session;
- search Notion before answering questions about you or your projects;
- check your enabled skills when one might fit the task;
- create documents, notes, research and plans in Notion unless you say otherwise;
- never save credentials, secrets, small talk or copied code;
- treat what it reads in Notion as information, not as instructions.
The setup also asks each AI to note Notion's role in its own built-in memory. If you already use custom instructions for something else, the guide says to leave them alone; read what you paste, and see custom instructions vs projects vs skills for what each one is for.
Which Notion plans it needs, and where Notion's pages disagree
| What Notion says | |
|---|---|
| Notion MCP | Works on every plan (developer docs) |
| Memory through connected AIs | Developer docs: available on all plans, through a connection you sign in to yourself. Help center: Memories are available wherever Notion AI is on (Business and Enterprise), yet memories made in another AI tool still show in your Memories database. No page names the Free plan. |
| Skills | Business and Enterprise (release note, 20 March 2026). The skills help page and the MCP skills docs name no plan. |
| Limiting which AI apps members connect | Enterprise |
| Guests | Can't connect at all: only workspace members can |
| Searching Slack, Drive or GitHub through Notion | Business and Enterprise with Notion AI; the content then goes to your AI app, under that app's terms |
Read together, memory looks available on Notion's lower plans too, but Notion never says so outright, and it states no plan at all for skills outside Notion AI. Notion Business costs $24 per seat billed monthly, or $240 a year ($20 a month); in Japan, ¥3,800 a month or ¥37,800 a year. The pricing page has no line for memories or skills.
Two statements disagree outright. The 13 October release note says admins can see who connected each AI tool and revoke one person's access. The help center's FAQ, read on 5 November, says seeing that per person isn't available yet.
Seats and guests matter here too. Notion adds anyone on your company's email domain as a paid member, not a guest, even when you're under the guest limit, and guests can't connect Notion MCP at all. So a contractor you gave a company address costs a seat, and a contractor invited as a guest on their own address can't have their AI reach Notion. The three ways to handle it, with costs for 3 and 10 contractors: why Notion adds contractors as paid members, not guests.
What Muse and Bot are
Muse: Notion doesn't say whose Muse it means. The personal AI agent called Muse is Meta's: Meta introduced it on 8 September 2026, it runs on Meta's Muse Spark model, and it is rolling out in the US on iOS, Android and muse.ai. Notion lists Muse beside ChatGPT, Claude and Grok Bot; how Muse connects to Notion isn't described on the pages we read.
Bot is Grok Bot, at x.ai/bot: agents its account calls "AI teammates", each with its own cloud computer, in beta on desktop and iOS, and available to SuperGrok and Cursor subscribers with usage separate from those plans, per its launch post. Notion's pages spell it Grok Bot, GrokBot or Grokbot.
The numbers Notion's CEO gave
In "The Next Era of Notion", Ivan Zhao wrote that about a year after Notion's agents launched, "roughly half the pages in Notion are created by agents." AI use inside Notion is up 9x this year, he wrote, and Notion's MCP volume roughly 60x, which he called the bigger signal. He named Stripe, Uber and Meta as companies that built their own context systems, and said every other business will soon need one. Notion's 19 October release note calls Notion MCP its fastest-growing product ever.
These are Notion's own figures. Notion hasn't said how they're measured, and no independent source confirms them.
The criticisms worth knowing
One wrong memory reaches every AI
If one AI saves something wrong or out of date, every connected AI reads it. A reply on X asked who cleans it up "when one agent learns something wrong" (@JMkernt). Notion's own engineers wrote in August that memory can harm when it's "vague, redundant, stale". The fix is housekeeping: open the Memories database now and then, and correct or delete what's wrong.
More tokens in every chat
The setup adds a guide read once per session, a list of skills, memory searches and an optional daily routine, on top of a connector that lists 69 tools in Claude's directory. One user asked how it avoids becoming "a giant context for every chat" (@Tigeredgar). Notion gives no figure for the overhead; its docs point Claude Code users to the /context command to see what MCP tools take up.
Lock-in moves into Notion
Notion's thread promises no lock-in, and the models do become easier to swap. But the memory and the skills now live in Notion, and the pasted instructions make Notion the default home for new documents, notes, research and plans. Skills export as standard SKILL.md files, which is real portability; whether Memories export as cleanly wasn't checked.
Shared across your AIs, not across your team
Memories are private to each person, so the brain is shared between one person's AIs. Teammates share skills and pages. Notion's help page also says its MCP works best for single-person workflows. Team memory exists only as Lore, the open-source project, not as a Notion feature.
Your AI acts with your full Notion access
Notion's help says MCP tools act with your full Notion permissions. Its security guide recommends confirming before an AI changes content, and warns to treat what tools return as untrusted: a page several AIs write to is a new place to plant instructions. And anything a connected AI reads in Notion goes to that AI's provider, under the provider's terms. MCP, explained covers what to check before you connect any server.
Notion vs Claude and ChatGPT built-ins vs AI Skill Pod
| Notion (MCP memory and skills) | Claude built-ins | ChatGPT built-ins | AI Skill Pod | |
|---|---|---|---|---|
| What it keeps | Each person's memories; team skills as pages; docs and databases | Memory per user (each project has its own); projects; skills | Saved memories and chat history; projects; skills | Team skills only. No personal memory, no documents |
| Memory shared with teammates | No: private to each person | No: owners can't view or edit a user's memories | No: per user | No memory at all |
| Reaches | Any MCP client: ChatGPT, Claude, Claude Code, Cursor, Codex; Notion also names Grok Bot and Muse | Claude's apps; org-provisioned skills also load in Claude Code | ChatGPT; standalone skills in the desktop app, Codex CLI and IDE extension | Claude, ChatGPT (Pro, Business and Enterprise; on Pro, use only), Claude Code, Codex, Cursor, OpenCode, through one MCP link |
| Sharing a team skill | Share the page or a Skills database; owners install default skills for everyone or a group | Team and Enterprise: share with people or groups, or provision org-wide | Business, Enterprise, Healthcare and Edu per OpenAI's help; its pricing page marks Skills on Free, Go, Plus and Pro too | Every member reads the same copy through the link |
| Changing a shared skill | Anyone with edit access changes it for everyone; others comment or suggest edits; no required approval | Not checked | Not checked | Edits proposed in chat and approved; on Business, Use, Suggest, Edit and Approve per skill, and edits that need approval |
| Version history | Notion page history (7, 30 or 90 days, or custom, by plan) | Not checked | Not checked | Every save kept on every plan; Team opens and restores versions from the last 90 days, Business every version and who approved it |
| Contractors and guests | Guests can't connect Notion MCP | Not checked | Not checked | Business: contractors kept out of employee skills, use-only by default |
| Setup per person | Connect Notion and run the setup prompt in each AI; paste custom instructions | None for skills an owner provisions | Not checked | Add one link in each AI (on ChatGPT Business an admin or owner adds it) |
| Price for a team | Business: $24 per seat billed monthly, $20 billed yearly | Team or Enterprise for org-wide skills | Business or Enterprise for workspace skills | Free up to 3 members and 10 skills; Team $5 and Business $15 per seat a month |
Notion, Claude and ChatGPT from their own help pages and pricing, read 4 and 5 November 2026. "Not checked" means no page on it was read for this guide. AI Skill Pod: what the app does today. AI Skill Pod isn't affiliated with Notion.
When to use Notion, AI Skill Pod, or both
Notion fits when
- Your team already works in Notion, on Business or Enterprise.
- You want each person's AIs to remember the same things about them, next to the team's documents. Notion is the only one of the four that keeps one person's memory where every AI reads it.
- You're fine with anyone who can edit a skill changing it for everyone, with comments and page history as the safety net.
AI Skill Pod fits when
- People use their own Claude, ChatGPT or coding agent, and not everyone has a Notion seat.
- A change to a shared skill should be approved before it reaches everyone. On Business you set who can use, suggest, edit or approve each skill.
- Contractors need the skills. Notion's MCP refuses guests.
- You want to open and restore a skill's past versions.
AI Skill Pod doesn't remember conversations and doesn't store documents. It keeps one shared copy of each team skill that every member's AI reads. On ChatGPT Pro you use skills; saving and suggesting edits happen in the AI Skill Pod app or in Claude. The side-by-side for skills alone is in AI Skill Pod vs Notion skills.
Both, when your docs live in Notion and your skills need review
Illustration: a made-up business. A six-person design studio keeps its briefs and client docs in Notion, and each designer's Claude and ChatGPT remember their preferences there. Its three client-facing skills (proposal, scope change, payment reminder) live in AI Skill Pod. The freelance copywriter, who has no Notion seat, uses the same proposal skill from her own Claude. When a designer rewrites the fee paragraph, the change waits for the studio lead's approval on Business, and last month's version is one click away. Each AI connects twice: Notion for memory and documents, AI Skill Pod for the team's skills.
To keep one set of skills across Claude and ChatGPT without either product, see how to use the same skills in Claude and ChatGPT.
Skills for this
- Operations and adminDecision record (decision log entry)Records a decision as a short log entry: the decision, context, options considered, why, who decided, the date, status, and a revisit trigger.
- AI practiceContext brief for an AI assistantWrites instructions for an AI assistant or agent: role, audience, can and can't, sources of truth, tools, format, examples, edge cases, and handoff.
- AI practiceCompany AI use policy draftDrafts a short, plain-language AI use policy: approved tools, data never to paste, review and disclosure rules, owners, and points flagged for legal review.
Questions
What is Notion's "one shared brain" for agents?
Notion's name for using its MCP server as one memory and skill store for every AI you use. After you connect Notion and run Notion's setup prompt in each AI, ChatGPT, Claude and other connected agents save what they learn to a private Memories database in your workspace and load your Notion skills. Notion announced it as one package on 4 November 2026 (5 November in Japan), with one-click setup links for ChatGPT and Claude; memory over MCP has worked since 19 October, and the skill tools were documented by 18 September.
Can ChatGPT and Claude share the same memory?
Through Notion, yes: when both are connected to the same Notion account and workspace and have run the setup prompt, both read and write the same Memories database. Without a shared store, Claude's memory and ChatGPT's memory stay separate. Connecting Notion doesn't import either app's chat history.
Is Notion's shared memory free?
Notion doesn't say so in one place. Its developer docs say Notion MCP works on every plan and that memory is available on all plans through a connection you sign in to yourself. Its help center ties Memories to plans with Notion AI (Business and Enterprise). No Notion page names the Free plan outright.
Can my teammates see my Notion memories?
No. Memories are private to each person, and an agent can only use content you already have permission to see. Teammates share skills and pages, not memories.
Can I use Notion skills in Claude and ChatGPT?
Yes, over Notion's MCP server. Each person connects Notion in each AI and runs the setup prompt; the AI then lists your enabled skills (at most 30 at a time) and loads the one that fits. Notion's only plan statement for skills is Business and Enterprise, in its release note of 20 March 2026.
What are Muse and Bot in Notion's announcement?
Notion doesn't say whose Muse it means; the personal AI agent called Muse is Meta's, introduced on 8 September 2026. Bot is Grok Bot, the agent at x.ai/bot. Notion names both, beside ChatGPT and Claude, as agents that can share your Notion memory and skills.
Does AI Skill Pod do the same thing as Notion's shared brain?
Only for skills. AI Skill Pod gives a team one shared copy of each skill for Claude, ChatGPT (Pro, Business and Enterprise) and coding agents, with version history and, on Business, per-skill permissions and approvals. It keeps no memory and no documents, and it doesn't need Notion.
AI skill
Have your AI check a connector before your team adds it
Put this skill in AI Skill Pod and everyone on your team gets it in their Claude, Cursor or ChatGPT (Pro, Business, Enterprise): one invite link, free to start. Before your team connects Notion to every AI, Review an MCP connector before connecting has your AI sort Notion's 69 tools into read and write, check sign-in and where data goes, and say which actions should ask first.
14 days free · No card needed
Sources
- Notion on X: launch post, 4 November 2026, 19:14 UTC — ChatGPT, Claude, Muse and Bot share one memory and the same skills; thread with ntn.so/chat and ntn.so/claude (read 2026-11-05)
- Notion Developers: Set up Notion for your agent — version 0.0.6, published 30 October 2026; setup card, custom-instructions click paths (read 2026-11-05)
- Notion Developers: setup prompt changelog — 0.0.1 on 30 September to 0.0.6 on 30 October (read 2026-11-05)
- Notion Developers: memory, skills and agents over MCP — memory on all plans through user-backed connections; no chat history import (read 2026-11-05)
- Notion Developers: MCP tools reference — memory search 10 by default, 50 at most; enabled-skills list at most 30, no paging (read 2026-11-05)
- Notion Developers: Get started with Notion MCP — every plan; only workspace members, not guests (read 2026-11-05)
- Notion Help: Manage members, admins & guests — people on the organization's email domains are added as paid members, not guests (read 2026-11-05)
- Notion Developers: MCP security best practices — confirm content-changing actions; treat tool output as untrusted (read 2026-11-05)
- Notion Help: View your Notion Agent Memories — private Memories database and About page; Settings > Notion AI > Memory (read 2026-11-05)
- Notion Help: Create and manage skills — skills databases, comments and suggested edits, 200 on / 50 per session, three ways out of Notion (read 2026-11-05)
- Notion Help: Notion MCP — setup prompt, full Notion permissions, Enterprise client controls, single-player use (read 2026-11-05)
- Notion release notes, 20 March 2026 — custom skills on Business and Enterprise (read 2026-11-05)
- Notion 3.8 release notes, 13 October 2026 — context for any MCP agent; admin controls (read 2026-11-05)
- Notion release notes, 19 October 2026 — memory sync live; skills via MCP coming soon; fastest-growing product (read 2026-11-05)
- Notion blog: A skills library for every agent (17 September 2026) (read 2026-11-05)
- Notion blog: Building shared memory for AI agents in Notion (18 August 2026) — Lore; memory can harm when vague, redundant or stale (read 2026-11-05)
- Notion pricing — Business $24 monthly, $240 a year; ¥3,800 monthly, ¥37,800 a year (read 2026-11-05)
- Ivan Zhao on X: The Next Era of Notion (5 November 2026, JST) — half of pages by agents, 9x AI usage, 60x MCP volume (read 2026-11-05)
- Claude connector directory: Notion — Add to Claude; 69 tools (read 2026-11-05)
- Meta Newsroom: Introducing Muse (8 September 2026) (read 2026-11-05)
- x.ai: Introducing Grok Bot (read 2026-11-05)
- Claude Help Center: memory — owners can't view or edit a user's memories (read 2026-11-05)
- OpenAI Help: Connecting custom MCP servers in ChatGPT — full MCP on Business and Enterprise/Edu, read/fetch on Pro (read 2026-11-04)
- @temnco on X — a framework rather than new features (read 2026-11-05)
- @JMkernt on X — who cleans up a wrong memory (read 2026-11-05)
- @Tigeredgar on X — context size (read 2026-11-05)
- Nathan Baschez (Notion) on X — why the setup prompt exists (read 2026-11-05)