Warp
Warp copied to clipboard
Add Streamable HTTP Transport Support for MCP
Pre-submit Checks
- [x] I have searched Warp feature requests and there are no duplicates
- [x] I have searched Warp docs and my feature is not there
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
Thanks for this feature request!
To anyone else interested in this feature, please add a 👍 to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.
Is two upvotes enough to make this a top priority? :-)
@jmjohnson05 normally not, but we can maybe work this into our next hackathon or something 🙏
Hey @westdavidr - can you give an example of some MCP server that you want to work in Warp, but doesn't? Ideally I'd love a paste of the exact config like:
{
"": {
"command": "",
"args": [],
"env": {},
"working_directory": null,
"start_on_launch": true
}
}
... with any environment variables redacted, of course. But the fewer env vars, the better, since there's a higher chance I'll be able to repro on my side. :)
Here you go:
{
"microsoft_learn": {
"url": "https://learn.microsoft.com/api/mcp",
"start_on_launch": true
}
}
@jefflloyd Were you able to reproduce the connection error using the streamable http mcp server from microsoft learn docs?
Haven't had a chance to dig in too deeply just yet - will let you know when I do :)
So I was playing around with this today and found a configuration to get it to work. I have been unsuccessful with all attempts using simply the URL.
{
"microsoft_learn": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://learn.microsoft.com/api/mcp"
],
"env": {},
"working_directory": null,
"start_on_launch": false
}
}
Also I was unable to get the Notion SSE example from Warp MCP Server Configuration Examples to work as demonstrated in the docs.
{
"Notion": {
"url": "https://mcp.notion.com/sse"
}
}
I was able to connect via OAuth with these configs:
{
"notion-HTTP": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.notion.com/mcp"
],
"env": {},
"working_directory": null,
"start_on_launch": false
}
}
Or
{
"notion-SSE": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.notion.com/sse"
],
"env": {},
"working_directory": null,
"start_on_launch": false
}
}
Hope this helps!
@jefflloyd @westdavidr @dannyneira
I actually am now realizing the fact that the way I showed there is the CLI Sever way vs SSE/HTTP Server way. But yeah, for the short term fix it can be run that way. Happy to help provide any logs or anything else you guys need to continue the development of the MCP server integrations.
Hey Folks, this is on the roadmap and being worked on, so thanks for your patience. Please continue to 👍 the top line request and subscribe for updates.
Closing as resolved since this support has been added in the latest release. Please update Warp and let us know if any issues.
Note that we are working on OAuth support separately.
Closing as resolved since this support has been added in the latest release. Please update Warp and let us know if any issues.
Note that we are working on OAuth support separately.
Thank you! This works as expected. Cheers!