Does sparfenyuk/mcp-proxy support Streamable HTTP on the client side?
I'm using sparfenyuk/mcp-proxy to relay between an LLM client and a local MCP server over SSE. My client (e.g., Copilot) only supports Streamable HTTP and SSE is being deprecated. Can I make the client-to-proxy leg use Streamable HTTP, or do I need a different proxy?
Originally asked on GitHub: https://github.com/sparfenyuk/mcp-proxy/issues/74
4 answers
This is still open as of the last comment (2025-08-28): sparfenyuk/mcp-proxy does not support Streamable HTTP on the client-facing side, and no maintainer has posted a fix or timeline. If you need Streamable HTTP between the client and the proxy today, the thread's practical answer is to switch proxies. Commenters suggested punkpeye/mcp-proxy as an alternative that supports Streamable HTTP between the client and the proxy, and supercorp-ai/supergateway as another replacement. The thread does not include configuration examples for either.
For the original sparfenyuk/mcp-proxy, no workaround is given in the thread; the only route is to use a different proxy. One commenter also suggested considering WebSocket instead of SSE for LLM-to-proxy communication (for more flexible bidirectional flows) and adding retries, observability, and scalability planning, but that is a design suggestion, not something implemented in mcp-proxy.
General advice: before switching, check the README of the alternative proxy for the required transport URL and MCP client settings, and confirm your client version supports the transport you configure.
Did this work for you?What @CXwudi tried on GitHub (Outcome unclear)
A commenter recommended using supercorp-ai/supergateway instead of waiting for Streamable HTTP support in sparfenyuk/mcp-proxy.
Source: https://github.com/sparfenyuk/mcp-proxy/issues/74#issuecomment-3235289079 (opens external site)
Did this work for you?What @CXwudi tried on GitHub (Outcome unclear)
A commenter suggested punkpeye/mcp-proxy as an alternative that supports Streamable HTTP between the client and the proxy, which the original proxy lacks.
Source: https://github.com/sparfenyuk/mcp-proxy/issues/74#issuecomment-2952853825 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
A commenter suggested considering WebSocket instead of SSE for LLM-to-proxy communication, plus adding retries, error handling, observability, and scalability planning. This was a design suggestion, not a tested change.
Source: https://github.com/sparfenyuk/mcp-proxy/issues/74#issuecomment-3232764060 (opens external site)
Did this work for you?
Related questions
- AttributeError: module 'mcp.server' has no attribute 'stdio_server' while running mcp-proxy against an SSE server
- mcp-proxy Docker on AMD64: "no matching manifest for linux/amd64"
- mcp-proxy stdio mode fails in Cline but works in Claude Desktop
- mcp-proxy gets 405 Method Not Allowed when connecting to a StreamableHTTP server
- mcp-proxy --headers doesn't send Authorization header to local MCP server