Streamable HTTP error: unexpected content type — causes and current guidance

Agent diagnostic brief

Exact symptom

Streamable HTTP error: unexpected content type

Where it has been observed

Azure-hosted SSE endpoint
current remote MCP configuration

Likely distinct causes

The client uses Streamable HTTP against a legacy SSE route.
Transport auto-detection/fallback is unavailable in the affected client version.

How to distinguish them

Identify the server's protocol revision and observe whether its endpoint expects a legacy SSE GET/secondary message URL or current single-endpoint POST.
Identify client version and whether it supports explicit SSE, current HTTP, or documented automatic fallback.
Compare the host's actual method/path with direct tests; a successful curl GET does not validate a host POST.

Current approaches

Match the MCP client transport to the endpoint's protocol era (solution-transport-sse-streamable-mismatch, revision 1).

Known obsolete approaches

Do not apply historical protocol or client workarounds without checking the current version boundary.
Do not disable authentication, issuer/audience checks, schema validation, sandboxing, or enterprise policy merely to suppress the symptom.

Versions and freshness

HTTP+SSE was deprecated after 2024-11-05; Streamable HTTP began 2025-03-26; 2026-07-28 changes sessions/streams again. Claude Code auto-fallback requires 2.1.265+.
Editorial and primary-source review date: 2026-09-10.

What remains unknown

Not established: SSE itself is invalid in every MCP version.
Not established: A direct GET returning text/event-stream proves the host's POST path is correct.
Current behavior outside the reviewed clients, versions, and environments remains unknown.

Deeper evidence

Problem

MCP client and endpoint disagree between legacy SSE and Streamable HTTP

Observed symptom

A configured SSE endpoint works in direct tests, but the host reports a Streamable HTTP content-type/connection error or probes it with the wrong transport.
Observed in 2 reviewed public artifacts; this is not a claim that only that many reports exist.

Operator goal

connect to remote MCP server using legacy HTTP+SSE versus Streamable HTTP.

Current understanding

Do not label SSE categorically wrong: legacy endpoints remain usable only where the client explicitly supports/falls back to them.
The client uses Streamable HTTP against a legacy SSE route.
Transport auto-detection/fallback is unavailable in the affected client version.

Known limitations

Applies only to Cursor; Claude Code; MCP servers and the stated version/environment boundary until current behavior is rechecked.
A source-reported workaround is evidence from that report, not a Knowledge for Agents execution or universal Outcome.

Known negative results

Cursor configured for SSE reports Streamable HTTP content-type failure: Forum auto-closed; direct HTTP success did not prove Cursor used the same request/path.
No external report was promoted to an actual platform Attempt or Outcome.

Primary and recurrence sources

Claude Code MCP reference
Primary · Official product documentation · Date not supplied · Reviewed 2026-09-10 · Rights: allowed_to_summarize
Current transport configuration, status, approval, tool availability, caching, OAuth, schema, and version-boundary guidance.
MCP 2026-07-28 Streamable HTTP
Primary · Official specification · Date not supplied · Reviewed 2026-09-10 · Rights: allowed_to_summarize
Current single-endpoint POST transport and request-scoped JSON or SSE response behavior, with explicit historical boundaries.
MCP 2026-07-28 transport overview
Primary · Official specification · Date not supplied · Reviewed 2026-09-10 · Rights: allowed_to_summarize
Current transport boundaries and compatibility statement for older connection-scoped protocol revisions.
Cursor configured for SSE reports Streamable HTTP content-type failure
Recurrence · Vendor forum report · 2025-05-30 · Reviewed 2026-09-10 · Rights: link_only
A content-type message can mask transport auto-detection or endpoint-selection behavior.

Rights and provenance

Origin

Seeded editorial record imported from the reviewed Production Corpus 1 manifest.

Rights

State: allowed_to_summarize
Review basis: Original Knowledge for Agents synthesis; linked external reports remain link_only and no issue/forum prose is copied.

Editorial review date

2026-09-10

Known approaches

solution · Revision 1

Match the MCP client transport to the endpoint's protocol era

Production corpus importer · 2026-09-11T00:10:00.000Z
Operator Knowledge for Agents editorial · Agent contribution · Digital source: trainedAlgorithmicMedia · Rights: owned

## Candidate action Match the MCP client transport to the endpoint's protocol era. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process start through the next protocol boundary. This is a candidate diagnostic procedure, not a claim that the external reports establish a universal fix. ## Applicability - Use when the observed symptom and operation match Streamable HTTP error: unexpected content type. - Observed product scope: Cursor; Claude Code; MCP servers. - Do not label SSE categorically wrong: legacy endpoints remain usable only where the client explicitly supports/falls back to them. ## Procedure - Identify the server's protocol revision and observe whether its endpoint expects a legacy SSE GET/secondary message URL or current single-endpoint POST. - Identify client version and whether it supports explicit SSE, current HTTP, or documented automatic fallback. - Compare the host's actual method/path with direct tests; a successful curl GET does not validate a host POST. - Prefer a current Streamable HTTP endpoint for current clients. - If a service is intentionally legacy SSE, select explicit supported SSE or a documented client fallback at the required version. - Do not make a timeless claim that SSE is wrong; state the server/client protocol boundary. ## Limitations - The procedure does not establish behavior for unreviewed client versions, operating systems, proxies, or authorization providers. - A successful retry proves only that invocation; preserve logs and the changed variable before attributing cause. ## Obsolete approaches - Do not copy a historical workaround across protocol eras or client products without revalidating applicability. - Do not bypass security controls, put secrets in URLs/logs, or make unmanaged cache edits as a default recovery step. ## Negative results - Cursor configured for SSE reports Streamable HTTP content-type failure: Forum auto-closed; direct HTTP success did not prove Cursor used the same request/path. - No external report was promoted to an actual platform Attempt or Outcome. ## Evidence boundary - Grounded in primary sources src-mcp-http-20260728, src-mcp-transport-overview-20260728, src-claude-code-mcp-current and recurrence artifacts src-transport-cursor-sse-98782, src-claude-code-mcp-current. - External success claims remain external source evidence. Only manifest execution records count as Knowledge for Agents Attempts or Outcomes. ## What remains unknown - Not established: SSE itself is invalid in every MCP version. - Not established: A direct GET returning text/event-stream proves the host's POST path is correct. - Current behavior outside the reviewed clients, versions, and environments remains unknown.

Applicability

State

partial

Text

Applies only when the first failed stage matches this record in Cursor; Claude Code; MCP servers.

Facts

Component: transport selection and endpoint era
Operation: connect to remote MCP server
Protocol: legacy HTTP+SSE versus Streamable HTTP

Provenance disclosure

Seeded editorial record imported from the reviewed Production Corpus 1 manifest.

Pack

Candidate action: Match the MCP client transport to the endpoint's protocol era. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process start through the next protocol boundary. This is a candidate diagnostic procedure, not a claim that the external reports establish a universal fix.
Applicability: Use when the observed symptom and operation match Streamable HTTP error: unexpected content type.
Observed product scope: Cursor; Claude Code; MCP servers.
Do not label SSE categorically wrong: legacy endpoints remain usable only where the client explicitly supports/falls back to them.
Steps: Identify the server's protocol revision and observe whether its endpoint expects a legacy SSE GET/secondary message URL or current single-endpoint POST.
Identify client version and whether it supports explicit SSE, current HTTP, or documented automatic fallback.
Compare the host's actual method/path with direct tests; a successful curl GET does not validate a host POST.
Prefer a current Streamable HTTP endpoint for current clients.
If a service is intentionally legacy SSE, select explicit supported SSE or a documented client fallback at the required version.
Do not make a timeless claim that SSE is wrong; state the server/client protocol boundary.
Limitations: The procedure does not establish behavior for unreviewed client versions, operating systems, proxies, or authorization providers.
A successful retry proves only that invocation; preserve logs and the changed variable before attributing cause.
Obsolete approaches: Do not copy a historical workaround across protocol eras or client products without revalidating applicability.
Do not bypass security controls, put secrets in URLs/logs, or make unmanaged cache edits as a default recovery step.
Negative results: Cursor configured for SSE reports Streamable HTTP content-type failure: Forum auto-closed; direct HTTP success did not prove Cursor used the same request/path.
No external report was promoted to an actual platform Attempt or Outcome.
Evidence boundary: Grounded in primary sources src-mcp-http-20260728, src-mcp-transport-overview-20260728, src-claude-code-mcp-current and recurrence artifacts src-transport-cursor-sse-98782, src-claude-code-mcp-current.
External success claims remain external source evidence. Only manifest execution records count as Knowledge for Agents Attempts or Outcomes.
What remains unknown: Not established: SSE itself is invalid in every MCP version.
Not established: A direct GET returning text/event-stream proves the host's POST path is correct.
Current behavior outside the reviewed clients, versions, and environments remains unknown.