Streamable HTTP vs SSE: Which MCP Transport Do Claude, ChatGPT and Gemini Accept?
Use Streamable HTTP. It replaced the HTTP+SSE transport in the MCP spec, ChatGPT's production endpoint must support it, and Anthropic's policy says remote servers should support it. Claude still supports legacy HTTP+SSE for now, Gemini CLI connects to either (httpUrl for Streamable HTTP, url for SSE), and the MCP Registry accepts an sse remote only to support existing clients. HTTP+SSE is listed as Deprecated in the current spec.
"SSE" causes confusion because it means two different things in MCP. There is the old HTTP+SSE transport from protocol version 2024-11-05, and there is Server-Sent Events as a response format that Streamable HTTP can still use. Directories care about the first one. mcplisted is not affiliated with any of the platforms below.
The short answer by platform
| Platform | Streamable HTTP | Legacy HTTP+SSE |
|---|---|---|
| Claude connectors | Recommended; policy says remote servers should support it | Supported for now; policy says it will be deprecated |
| ChatGPT plugins | Required for the production endpoint | Not listed as an option |
| Gemini CLI | httpUrl in config |
url in config |
MCP Registry remotes |
"type": "streamable-http" |
"type": "sse", only to support existing clients |
What the 2025-06-18 spec says Streamable HTTP is
The spec defines two standard transports: stdio and Streamable HTTP. Streamable HTTP "replaces the HTTP+SSE transport from protocol version 2024-11-05." The key rules:
- The server provides one endpoint path (the "MCP endpoint") that supports POST and GET, such as
https://example.com/mcp. - Every client message is a new HTTP POST. The client MUST send
Accept: application/json, text/event-stream. - For a request, the server returns either
Content-Type: application/json(one object) orContent-Type: text/event-stream(an SSE stream). Clients MUST support both. - For a notification or response, the server returns
202 Acceptedwith no body. - A GET either opens an SSE stream or returns
405 Method Not Allowed. - The server MAY assign an
Mcp-Session-Idon the initialize response; clients then send it on every request. - Clients send
MCP-Protocol-Version: 2025-06-18on requests after initialization. An unsupported version gets400 Bad Request.
A minimal POST looks like this:
curl -s https://mcp.example.com/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
How the old HTTP+SSE transport differs
The 2024-11-05 transport used two endpoints: a GET that opens an SSE stream and sends an endpoint event, and a separate POST endpoint for messages. The spec's backward-compatibility section tells clients to POST an initialize first and fall back to GET only if that fails with a 4xx such as 405 or 404. Servers that want to support old clients can host both the old SSE and POST endpoints alongside the new MCP endpoint.
Where the spec is heading
The current MCP revision is 2026-07-28. Its deprecated features registry lists the HTTP+SSE transport as Deprecated, with earliest removal "three months after SEP-2596 reaches Final." The same revision also changes Streamable HTTP itself:
- Protocol-level sessions and the
Mcp-Session-Idheader are removed. - The
initializehandshake is removed; each request carries its protocol version in_meta. - The standalone GET stream is replaced by
subscriptions/listen; a server on only this revision answers GET or DELETE with405. - SSE resumability with
Last-Event-IDis removed.
Claude's docs currently state that its OAuth client follows the 2025-03-26, 2025-06-18, and 2025-11-25 authorization specs, so a server that speaks the 2025 Streamable HTTP shape remains the safe target for directories today. If you adopt 2026-07-28, the spec describes how clients detect which era a server speaks.
Practical setup
- One stable path, typically
/mcp, for POST and GET - Return JSON for simple calls; use an SSE response only when you stream progress
- Answer GET with
405if you don't offer a server-to-client stream - Disable proxy buffering for SSE responses (the 2026-07-28 spec recommends
X-Accel-Buffering: no) - Validate the
Originheader; the spec says servers MUST, to prevent DNS rebinding - Don't register a URL that redirects to another host
OpenAI's deployment guide lists streaming response behavior as one of the factors when choosing infrastructure. Check proxy and CDN buffering before blaming the client.
Gemini CLI configuration
Gemini CLI picks the transport from the config key:
{
"mcpServers": {
"myServer": { "httpUrl": "https://mcp.example.com/mcp" },
"legacyServer": { "url": "https://mcp.example.com/sse" }
}
}
httpUrl maps to the Streamable HTTP client transport and url to the SSE client transport. See publishing a Gemini CLI extension.
MCP Registry entry
"remotes": [
{ "type": "streamable-http", "url": "https://analytics.example.com/mcp" },
{ "type": "sse", "url": "https://analytics.example.com/sse" }
]
The registry docs say remote servers should use Streamable HTTP and publish an sse remote only to support existing clients. See publishing to the MCP Registry.
Should you keep an SSE endpoint?
Only if you already have users on it. New servers should ship Streamable HTTP only. Then run a free check to confirm the endpoint answers a POST correctly, and read latency and timeouts if you stream long-running work.
Run a free check on your MCP server →Paste your URL and see what Claude, ChatGPT and Gemini reviewers will flag.
FAQ
Is SSE banned from the Claude directory?
No. Anthropic's policy says servers may support SSE for the time being but that it will be deprecated, and its build docs say Claude supports legacy HTTP+SSE.
Can a Streamable HTTP server still use SSE?
Yes. In the 2025-06-18 spec a server can answer a POST with Content-Type text/event-stream to stream messages, or with plain JSON.
Does ChatGPT accept SSE-only servers?
OpenAI's docs say the production endpoint must support the MCP Streamable HTTP transport. SSE-only is not listed as an option.
What should GET return on my MCP endpoint?
Under 2025-06-18, either an SSE stream or 405 Method Not Allowed if you don't offer one.
Sources
- MCP specification 2025-06-18: Transports
- MCP specification 2026-07-28: Streamable HTTP
- MCP specification 2026-07-28: Deprecated features
- Build an MCP server for Claude (Claude docs)
- Anthropic Software Directory Policy
- Build an MCP server (OpenAI plugin docs)
- MCP servers with Gemini CLI
- MCP Registry: Publishing Remote Servers
Rules change. If something here is out of date, email hello@mcplisted.com and we'll fix it. See our editorial policy.