Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

MCP Streamable HTTPMCP 2026-07-28

Connect to an MCP server over the current Streamable HTTP transport.

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

MCP Streamable HTTP: 7 supported, 0 partial, 0 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 Streamable HTTP?

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
  • Supported7
  • Partial0
  • Unsupported0
  • 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 to an MCP server over the current Streamable HTTP transport.

The Grok Bot cell is registry-listed. Authentication, server policy, and optional MCP primitives remain separate claims.

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
  • transportthe remote server must be reachable from the Claude Code host and may require headers or OAuth
Evidence
Cursordesktop · current
Supported
Target
current Cursor MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportthe configured HTTP endpoint must be reachable and may be restricted by authentication, enterprise MCP policy, and URL/network allowlists
Evidence
Gemini CLIcli · current
Supported
Target
Gemini CLI MCP documentation updated 2026-06-18 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportthe configured endpoint must be reachable and can require headers, OAuth, or other documented authentication providers
Evidence
Grok Botdesktop · current
Supported
Target
2026-08-28 Agent Plugins compatible-client listing · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • runtimetransport 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
  • transportthe endpoint must be reachable and `type` must be set to `streamableHttp`; omitted remote types retain legacy SSE behavior for compatibility
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
  • transportthe configured endpoint must be reachable and may require API-key or custom-header configuration; native desktop OAuth is separately limited
Evidence
Zed Agentdesktop · current
Supported
Target
Zed source commit e3adf43f37d7 and current documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • protocol-revisionthe pinned source negotiates MCP through revision 2025-11-25; it does not yet advertise the catalog's 2026-07-28 revision
  • transportthe remote endpoint must be reachable and may require configured headers or Zed's OAuth flow
Evidence
  1. 1. Evidence checked 2026-08-28: the Agent Plugins compatible-client registry explicitly lists MCP Streamable HTTP for Grok Bot. This is registry evidence, not an independent transport test.
  2. 2. Evidence checked 2026-08-28: Anthropic documents adding remote Claude Code MCP servers with the HTTP transport and a server URL.
  3. 3. Evidence checked 2026-08-28: Gemini CLI documents Streamable HTTP as a supported MCP transport using HTTP streaming.
  4. 4. Evidence checked 2026-08-28: Cursor documents Streamable HTTP as a supported local or remote MCP transport using an HTTP endpoint.
  5. 5. Evidence checked 2026-08-28: Cline documents Streamable HTTP as its recommended remote MCP transport and provides an explicit `streamableHttp` configuration.
  6. 6. Evidence checked 2026-08-28: Continue documents `streamable-http` remote MCP configuration and its pinned desktop client constructs the MCP SDK Streamable HTTP client transport.
  7. 7. Evidence checked 2026-08-28: Zed documents a single remote MCP endpoint, while its pinned HTTP transport sends JSON-RPC with POST and accepts JSON or request-scoped SSE responses.