Pre-submit Checks
Describe the solution you'd like?
I would like Warp terminal to support Streamable HTTP as a transport for Model Context Protocol (MCP) server connections. While Warp currently supports Server-Sent Events (SSE), the latest MCP specification introduces Streamable HTTP as a unified replacement for the previous HTTP+SSE transport. Implementing Streamable HTTP will ensure Warp remains compatible with new MCP server implementations and benefits from the latest protocol improvements.
"The Streamable HTTP transport replaces the HTTP+SSE transport, and combines both streaming and request/response support in a single, consistent transport."
— From the MCP docs
Is your feature request related to a problem? Please describe.
Yes. The MCP specification indicates that clients and servers that previously used HTTP+SSE are now expected to migrate to Streamable HTTP for full compatibility with the MCP 2025-03-26 standard.
"Clients and servers that previously used HTTP+SSE are expected to migrate to Streamable HTTP for full compatibility with the MCP 2025-03-26 standard."
— From the MCP docs
Additional context
Implementing Streamable HTTP will keep Warp aligned with the latest MCP standards and maintain robust interoperability with evolving server implementations.
Thank you for considering this update!
Operating system (OS)
macOS
How important is this feature to you?
4
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None
Pre-submit Checks
Describe the solution you'd like?
I would like Warp terminal to support Streamable HTTP as a transport for Model Context Protocol (MCP) server connections. While Warp currently supports Server-Sent Events (SSE), the latest MCP specification introduces Streamable HTTP as a unified replacement for the previous HTTP+SSE transport. Implementing Streamable HTTP will ensure Warp remains compatible with new MCP server implementations and benefits from the latest protocol improvements.
"The Streamable HTTP transport replaces the HTTP+SSE transport, and combines both streaming and request/response support in a single, consistent transport."
— From the MCP docs
Is your feature request related to a problem? Please describe.
Yes. The MCP specification indicates that clients and servers that previously used HTTP+SSE are now expected to migrate to Streamable HTTP for full compatibility with the MCP 2025-03-26 standard.
"Clients and servers that previously used HTTP+SSE are expected to migrate to Streamable HTTP for full compatibility with the MCP 2025-03-26 standard."
— From the MCP docs
Additional context
Implementing Streamable HTTP will keep Warp aligned with the latest MCP standards and maintain robust interoperability with evolving server implementations.
Thank you for considering this update!
Operating system (OS)
macOS
How important is this feature to you?
4
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None