Skip to content

Support for "Streamable HTTP" Transport #220

Open
@richieto

Description

@richieto

Is your feature request related to a problem? Please describe.

As a developer using the Typescript SDK for the Model Context Protocol (MCP), I need it to support the new "Streamable HTTP" transport introduced in PR modelcontextprotocol/specification#206 of the specification repository. Without this update, the SDK will be incompatible with servers adopting the new transport, causing integration issues and preventing me from leveraging the specification’s latest improvements.

Describe the solution you'd like

I’d like the Typescript SDK to be updated to implement the "Streamable HTTP" transport as outlined in PR
This includes:

  • Removing the /sse endpoint.
  • Routing all client-to-server messages through the /message endpoint.
  • Supporting server-upgraded SSE for notifications and requests.
  • Implementing session IDs for state management.
  • Enabling clients to initiate SSE streams with an empty GET to /message.
  • The implementation should also address any backwards compatibility requirements specified in the PR.

Describe alternatives you've considered

One alternative is manually patching the SDK to support the new transport, but this isn’t a sustainable solution. Another option is waiting for the maintainers to address this independently, but filing this issue ensures the change is tracked and prioritized proactively.

Additional context

The details of the "Streamable HTTP" transport are in PR of the MCP specification repository: modelcontextprotocol/specification#206. Updating the SDK is essential to keep it aligned with the latest MCP standard and to ensure seamless integration with updated servers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions