MCP server · Memory + knowledge
Notion MCP
Search, read and update authorized Notion workspace content through Notion's official hosted MCP server.
Quick verdict
A flagship knowledge-workspace connector with unusually strong first-party documentation, but its convenience should never be framed as narrow access: it inherits the user's readable and writable Notion reach.
- MaintainerNotion (official)
- Security scopeRead-write
- Transportsstreamable-http, sse
- Install channelremote · https://mcp.notion.com/mcp
- EvidenceSource Validated
- LicenseProprietary · Proprietary hosted service
Notion MCP connects an assistant to one authorized Notion workspace through OAuth. It can search and fetch workspace knowledge, query structured data, create or update pages and databases, move content, add comments and transfer selected files. Its effective reach matches the connected user's access, and some advanced search and query tools depend on the workspace's Notion AI plan. Notion treats content returned through MCP as untrusted input, since prompt injection inside workspace content can otherwise cause disclosure or unintended changes — human confirmation before every write is part of the security posture, not optional polish.
Install Notion MCP
http https://mcp.notion.com/mcp
{
"mcpServers": {
"notion": {
"url": "https://mcp.notion.com/mcp"
}
}
}Notion-hosted endpoint; the client completes an interactive OAuth grant to one workspace after connecting. Notion's older open-source notion-mcp-server package used a separate bearer-token/API path and is no longer actively maintained — it is a different, unmaintained artifact, not an alternate transport of this profile.
Credentials
No static secret goes in this config, but this server still requires account authorization. Connecting it starts an interactive sign-in and consent flow against the account it reaches, and whatever that account is allowed to do becomes what the agent can do through this server. Authorize it from an account scoped to the work at hand, and keep your client’s approval prompts on.
Verified configurations
Not run by us yet. This profile is Source Validated: the install channel, config entry, credentials and license were checked against the source and upstream metadata, but no configuration has been installed, discovered and executed in a recorded environment. When one is, it appears here with the eight scope dimensions below.
Best for
Teams that use Notion as a working knowledge base and want an assistant to research, draft and maintain content with the user's existing workspace permissions.
Why use it
It is Notion's actively maintained first-party path, uses interactive OAuth rather than a copied integration secret, and exposes richer workspace-native operations than the deprecated local server.
Tradeoffs
The OAuth grant can expose a broad workspace surface, connected-source search may expand the data boundary beyond Notion itself, and write tools can reorganize or overwrite important content. Some capabilities require higher Notion plans. Treat returned content as untrusted and require confirmation before every mutation.
Upstream state
in the official MCP Registry (active). Lifecycle is derived from a committed upstream snapshot at build time, never authored by hand.
Official MCP Registry name: com.notion/mcp
Editorial review
Grade B — Source Validated. Re-review is due by 2027-02-18. Config entries, credential names and package status can change upstream; verify against the official documentation before granting an agent access.
Sources
Related MCP servers
- Playwright MCPMicrosoft's MCP server that drives a real browser through Playwright with accessibility snapshots, not screenshots — navigate, click, type, read.
- Qdrant MCPGive agents a local or hosted Qdrant memory layer for storing notes and retrieving them by semantic search.
- Basic Memory MCPGive agents durable local memory in plain Markdown, with search, graph traversal and explicit note creation, editing and deletion.