[Feature] Add Streamable HTTP support #10
Description
What feature would you like to see?
Add Streamable HTTP support to Auto MCP. In practice, this means exposing a single /mcp endpoint that speaks the new protocol, while still serving the current HTTP + SSE route for anyone who needs it. The CLI could toggle it with something like --transport streamable-http.
Why is this feature useful?
Simpler deployments – one endpoint covers both the request and the streamed reply, so we can drop the extra /sse route and the long-lived connection headaches.
Future-proof – Streamable HTTP is on track to replace HTTP + SSE in the spec (see modelcontextprotocol/modelcontextprotocol#206 ). Supporting it keeps Auto MCP aligned with the rest of the MCP ecosystem.
Upstream momentum – The client side already supports Streamable HTTP, and server support is queued for merge in mark3labs/mcp-go#228 (tracked in mark3labs/mcp-go#219 ). As soon as that lands we can plug it in.
Additional context (optional)
We’re essentially waiting for mark3labs/mcp-go#228 to merge. Once that’s released:
Bump mcp-go to the new version that exposes server.NewStreamableHTTPServer.
Wire up the new transport behind the --transport streamable-http flag (CLI and web).