Notion MCP
Current Spec Verified Confidence: High (0.95)Notion MCP is an MCP server published by Notion with verified support for the current MCP specification revision (2026-07-28). It is the first-party server from Notion. Last verified 2026-08-07.
Does Notion MCP support the current MCP specification (2026-07-28)?
Yes. Notion MCP has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-08-07).
Is Notion MCP a first-party (official) MCP server?
Yes. Notion MCP is the first-party MCP server published by Notion (last verified 2026-08-07).
How do I connect to Notion MCP?
Notion MCP is available via a hosted remote endpoint at https://mcp.notion.com/mcp, the official MCP Registry under com.notion/mcp. Authentication: oauth. Transports: streamable-http, sse-legacy.
Does Notion MCP support MCP revision 2026-07-28?
Yes. Notion MCP supports MCP revision 2026-07-28 (checked 2026-08-07).
When were Notion MCP's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
Which MCP concepts apply to Notion MCP?
- Stateless core - The 2026-07-28 revision's redesign of MCP from a bidirectional stateful protocol into a request/response stateless one: the initialize handshake and protocol-level session are removed, every request carries its protocol version, client identity, and capabilities in _meta, and any request can land on any server instance behind a plain load balancer.
- Streamable HTTP - MCP's HTTP transport, introduced in the 2025-03-26 revision as the replacement for the original HTTP+SSE transport. A single endpoint accepts JSON-RPC POST requests; since 2026-07-28, requests must carry the Mcp-Method and Mcp-Name headers for header-based routing, and the legacy HTTP+SSE transport is formally deprecated.
Notion MCP is a remote MCP server hosted by Notion. Its documentation
publishes two endpoints: a Streamable HTTP endpoint at
https://mcp.notion.com/mcp, described as the recommended transport, and
a legacy SSE endpoint at https://mcp.notion.com/sse. Both are listed as
remotes on the server's official MCP Registry record,
com.notion/mcp. Workspace owners control which MCP clients may connect
from the workspace connection settings.
Notion's developer changelog entry of 2026-08-03 states that the Streamable HTTP endpoint supports protocol version 2026-07-28, and that clients negotiating the earlier 2025-era protocol on the same endpoint continue to work unchanged with no client updates required. It is the first vendor adoption of the revision recorded after the cluster of announcements on the revision's release date.
Authorization is OAuth 2.0. Notion's client-building guide states that
PKCE is mandatory with a code_challenge_method of S256, documents
discovery per RFC 8414 and RFC 9470, and describes Client ID Metadata
Documents as an alternative to Dynamic Client Registration. Token
responses carry top-level user_id, workspace_id and email_domain
fields.
Which MCP spec revisions does Notion MCP support?
Notion MCP has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Supported | Source |
How widely adopted is Notion MCP?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: vendor-changelog
· confidence 0.95 (High).
- Notion developer changelog entry dated 2026-08-03, titled "Notion MCP supports MCP protocol version 2026-07-28" - states "The Notion MCP Streamable HTTP endpoint at https://mcp.notion.com/mcp now supports MCP protocol version 2026-07-28. Existing MCP clients that negotiate the earlier 2025-era protocol on the same endpoint continue to work unchanged, so no client updates are required." - accessed
- Notion docs page "Notion MCP" - describes Notion MCP as a remote MCP server hosted by Notion, OAuth-authenticated, with client access managed by workspace owners under Settings then Connections - accessed
- Notion guide "Build an MCP client" - documents the Streamable HTTP endpoint https://mcp.notion.com/mcp and the SSE endpoint https://mcp.notion.com/sse, states PKCE is mandatory with code_challenge_method S256, and describes Client ID Metadata Document support as an alternative to Dynamic Client Registration - accessed
- Official MCP Registry record com.notion/mcp version 1.0.1, "Official Notion MCP server" - lists a streamable-http remote at https://mcp.notion.com/mcp and an sse remote at https://mcp.notion.com/sse - accessed
- Endpoint probe of https://mcp.notion.com/mcp - HTTP 401 with a Bearer WWW-Authenticate challenge carrying realm="OAuth" and an RFC 9728 resource_metadata URL, MCP's authorization discovery signal; OAuth requirement confirmed first-hand, capability set not observable without credentials - accessed