Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

MCP legacy HTTP and SSEMCP 2026-07-28

Connect through the superseded HTTP plus SSE transport when migration compatibility is required.

Terminology basis: MCP 2026-07-28. MCP 2026-07-28

MCP legacy HTTP and SSE: 6 supported, 0 partial, 1 unsupported, 24 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Model Context Protocol23 capabilities

Current evidence by product

Can my agent use MCP legacy HTTP and SSE?

Read across for the answer. 7 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

Known issues (0)Report an issue
  • Supported6
  • Partial0
  • Unsupported1
  • Unknown24
  • Not applicable0

Web

9 products

Desktop

13 products
ClineCline
Y5Supported
Docs checked 2026-08-28Current · 1 condition
?Unknown
No source reviewedPreview record
Report this result

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Connect through the superseded HTTP plus SSE transport when migration compatibility is required.

The Grok Bot cell is registry-listed for migration compatibility. New deployments should prefer the current transport where the server supports it.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Claude CLIcli · current
Supported
Target
current Claude Code MCP documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportSSE is retained for legacy compatibility; Anthropic recommends the HTTP transport where the server supports it
Evidence
Cursordesktop · current
Supported
Target
current Cursor MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportSSE remains supported for compatibility, while Cursor separately documents Streamable HTTP for current HTTP endpoints
Evidence
Gemini CLIcli · current
Supported
Target
Gemini CLI MCP documentation updated 2026-06-18 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportSSE endpoints can use headers or OAuth; new deployments should prefer Streamable HTTP where available
Evidence
Grok Botdesktop · current
Supported
Target
2026-08-28 Agent Plugins compatible-client listing · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • runtimesuperseded transport support is registry-listed and was not independently tested by Can My Agent Use
  • policyorganization server and network allowlists can block a remote server
Evidence
Clinedesktop · current
Supported
Target
current Cline MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportSSE is retained for legacy compatibility; Cline recommends explicit Streamable HTTP for current remote servers
Evidence
Continuedesktop · current
Supported
Target
Continue source commit 5522c6f44ca0 and current documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportSSE is an explicit legacy remote transport and remains separate from Continue's Streamable HTTP path
Evidence
Zed Agentdesktop · current
Unsupported
Target
Zed source commit e3adf43f37d7 observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportSSE response bodies on Zed's POST-based Streamable HTTP path do not constitute the superseded dedicated HTTP-plus-SSE transport
Evidence
  1. 1. Evidence checked 2026-08-28: the Agent Plugins compatible-client registry explicitly lists legacy MCP SSE for Grok Bot. This is registry evidence, not an independent transport test.
  2. 2. Evidence checked 2026-08-28: Anthropic documents the `sse` transport for legacy remote Claude Code MCP servers while recommending HTTP for current servers.
  3. 3. Evidence checked 2026-08-28: Gemini CLI documents SSE endpoints as one of its three supported MCP transport types.
  4. 4. Evidence checked 2026-08-28: Cursor documents SSE as a supported local or remote MCP transport and distinguishes it from Streamable HTTP.
  5. 5. Evidence checked 2026-08-28: Cline documents an explicit `sse` transport for legacy remote servers and retains SSE as the default when a remote transport type is omitted.
  6. 6. Evidence checked 2026-08-28: Continue documents an explicit `sse` remote transport and its pinned desktop client constructs the MCP SDK SSE client transport.
  7. 7. Evidence checked 2026-08-28: Zed's pinned transport module exposes only stdio and a single-endpoint POST-based HTTP transport; it does not implement the superseded HTTP-plus-SSE client transport.