Notion publishes an official remote MCP server that lets an assistant search your workspace and connected sources, read content, and create or update pages and databases. It is the least glamorous connector a marketing team can add and usually the one that improves everything else most, because it is where the brief already is.
Last updated September 14, 2026. Figures are from Notion's own documentation. New to the protocol? Start with what MCP is.
What the Notion MCP server exposes
| Surface | What you get |
|---|---|
| Search | Content across your Notion workspace and the sources connected to it |
| Read | Page and database content, as the signed-in user can already see it |
| Write | Create and update content, including new pages and databases |
| Admin control | Workspace owners can list and revoke members’ connections through the Admin API |
The endpoint is https://mcp.notion.com/mcp. You sign in with OAuth, and workspace owners control who may connect from admin settings.
Connecting it
1. Open your client's connector settings
In Claude, go to Settings, then Customize, then Connectors. In ChatGPT, turn on Developer mode under Settings, then Security and login, and add it under Settings, then Plugins. If Notion is already listed in the client's directory, add it from there instead.
2. Paste the endpoint
Add a custom connector with the URL https://mcp.notion.com/mcp and leave the advanced fields empty. There is no client ID or secret to enter; the server registers itself when you sign in.
3. Sign in and read the scopes
The consent screen is the one place you see what you are granting. Read it, and choose the narrower scopes wherever you are offered a choice.
4. Confirm the tools arrived
Ask the assistant what the connector can do. An empty list after a successful sign-in means the token is not being accepted: disconnect and reconnect to clear the stale grant.
The exact path for thirteen clients is in the MCP client directory.
What it costs
- No separate charge for the MCP server; it comes with Notion.
- Access is governed by the permissions the connecting user already has, so it inherits rather than widens their reach.
- Workspace owners control whether members may connect at all, from admin settings.
The limits worth knowing
- A large workspace is a large surface. The server can search everything the connecting user can see, which in most companies is more than they remember. Be specific about which database you mean rather than trusting a search to be.
- It can write, and writing is how notes get overwritten. Create and update are both available. An assistant asked to "tidy up" a database is a change with no diff and no undo beyond Notion’s own page history.
- It is a document store, not a source of truth for numbers. Anything performance-related in Notion is a snapshot somebody pasted. An assistant reading it will quote a figure with total confidence and no idea how old it is.
- Connected sources inherit the question. Notion search can reach sources connected to the workspace, so the blast radius of a poisoned prompt or an over-broad query is wider than Notion itself.
Where it stops for marketing
Notion holds what you decided, not what happened. It is the context layer — positioning, brand voice, the calendar, the brief — and its value is entirely in making the servers that do reach live systems produce output that sounds like you and fits the plan. On its own it answers no question about performance, because nothing in it is live.
That is the edge of what one vendor's data can answer, not a flaw in the server. It is why a marketing stack usually runs two or three: this one for what it is good at, and one for the channels that spend money. For the other half: Writing to your site over MCP. If you would rather hand the marketing half to one agent, Sprites runs Google Ads, Meta, LinkedIn and SEO behind one connector, with every write staged for your approval.
Before you grant write access
MCP has no built-in approval step: a write tool applies the moment the model calls it, unless the server itself holds the change. Check three things before you connect: which scopes the consent screen asks for, whether writes are staged or applied, and how to revoke access. The rest is in is MCP safe.
Related
- The best Claude connectors for marketers
- Semrush MCP
- Every MCP server worth connecting for marketing
- The Claude connector shortlist
Notion MCP questions
What can the Notion MCP server do?
Search content across your workspace and connected sources, read page and database content, and create or update content including new pages and databases. It acts with the permissions the connecting user already has.
Is Notion MCP official?
Yes. It is a remote MCP server hosted by Notion and documented in their developer docs, authorised through OAuth rather than an API key you store.
Can my workspace admin control who connects Notion MCP?
Yes. Access is controlled by workspace owners through admin settings, and organisation owners can list and revoke members’ connections through the Admin API.
Why connect Notion if it has no performance data?
Because every other connector produces better output when something has read the positioning doc first. It is the difference between on-brand copy and generic copy, and it costs nothing.
Can an AI agent overwrite my Notion pages?
It can update content, so yes. MCP defines no approval step, and an assistant asked to reorganise something will reorganise it. Page history is your only undo.
Does Notion MCP work with Claude and ChatGPT?
Yes. It is a standard remote MCP server, so it works as a Claude custom connector on any plan, in ChatGPT through developer mode, and in any other client that speaks remote MCP.