Notion MCP is retiring its legacy SSE endpoint
TL;DR
On November 11, 2026, Notion said clients that connect to https://mcp.notion.com/sse should switch to Streamable HTTP at https://mcp.notion.com/mcp. The legacy SSE endpoint shuts down on February 23, 2027.
- Status
- Coming Soon
- Released
- Plans
- Not specified
What changed
On November 11, 2026, Notion's developer changelog added a retirement notice under that day's update. Clients that connect to https://mcp.notion.com/sse need a new transport and a new URL. The transport is Streamable HTTP. The URL is https://mcp.notion.com/mcp. Notion will shut down the legacy endpoint on February 23, 2027.
The migration section calls this the legacy HTTP with Server-Sent Events (SSE) endpoint. It tells you to update the client before February 23, 2027. In the client's Notion server settings, change the transport from SSE to Streamable HTTP, replace the URL with https://mcp.notion.com/mcp, save, sign in again if the client asks, and check that the client lists Notion tools. A client that only offers SSE needs a version that supports Streamable HTTP.
The same getting-started guide already documents https://mcp.notion.com/mcp as the remote server URL for manual setup. The migration steps are in the Other MCP clients section of that page. This notice is separate from the faster page webhooks item in the same November 11 changelog update.
The changelog entry and the migration section have no official image.
Why it matters
This reaches people who typed the Notion MCP server URL into a client themselves, or who kept an older config that still points at https://mcp.notion.com/sse. A config that already uses https://mcp.notion.com/mcp with Streamable HTTP is on the URL the guide documents today.
A client still pointed at https://mcp.notion.com/sse loses that connection when the endpoint shuts down on February 23, 2027. The November 11 note and the migration section do not name a plan. The same guide says Notion MCP works on every plan, and that some tools and limits depend on the workspace plan. Notion MCP memories are a separate topic from this URL change.
What to change
- Open the Notion server entry in the client. Set the transport to Streamable HTTP and the URL to
https://mcp.notion.com/mcp. - Save. Sign in again if the client prompts you. Confirm the client lists Notion tools.
- If the client only offers SSE, update the client to a version that supports Streamable HTTP, then repeat the first two steps.
- If the client cannot use a remote HTTP server, the guide's JSON example runs
npxwithmcp-remoteandhttps://mcp.notion.com/mcp. The guide calls that the STDIO configuration for clients without remote HTTP. It also says the open-sourcenotion-mcp-serverpackage is a last resort and is no longer actively maintained.
Frequently asked questions
Which Notion MCP clients have to leave the SSE endpoint?
Clients whose server URL is https://mcp.notion.com/sse. The November 11 changelog names that URL. The migration steps are for that legacy SSE endpoint.
What URL replaces the Notion MCP SSE endpoint?
https://mcp.notion.com/mcp, using the Streamable HTTP transport. That is the remote server URL in Notion's manual setup guide.
When does the Notion MCP SSE endpoint shut down?
February 23, 2027. Notion's changelog and migration section both give that date and say to update before then.
Which Notion plans does the SSE retirement apply to?
The November 11 changelog and the migration section do not name a plan. The getting-started guide says Notion MCP works on every plan. Some MCP features on that page still depend on the workspace plan, and this URL change does not list a new plan requirement.