Why this server?
This Python-based proxy directly addresses the user's need by explicitly stating it 'bridges local MCP STDIO clients with remote MCP SSE servers,' acting as the desired connect mode.
-securityFlicense-qualityA minimal Python-based proxy that bridges local MCP STDIO clients with remote MCP SSE servers. It enables bidirectional JSON-RPC message passing between standard command-line tools and web-based remote endpoints.Last updated 2 months ago1Why this server?
This server is a perfect fit as it 'Bridges STDIO-based MCP clients with SSE-based MCP servers,' directly enabling a remote SSE server to be exposed as a STDIO server for local clients.
-securityFlicense-qualityBridges STDIO-based MCP clients with SSE-based MCP servers, allowing applications like Claude Desktop to connect to remote MCP servers that use SSE transport.Last updated 9 months ago9Why this server?
This proxy specifically 'Acts as a proxy between a local Stdio connection and a remote Model Context Protocol server running over Server-Sent Events,' which is precisely what the user is looking for to bridge an SSE server to a stdio interface.
-securityFlicense-qualityActs as a proxy between a local Stdio connection and a remote Model Context Protocol server running over Server-Sent Events. It specifically enables Stdio-based MCP clients to connect to the SwiftZilla remote SSE endpoint.Last updated 4 months ago8Why this server?
Described as 'A MCP Proxy (Local <-> SSE),' this project indicates a direct bidirectional connection between a local interface (typically STDIO for local MCP clients) and an SSE server, fitting the requirement for a bridge mode.
-securityAlicense-qualityA MCP Proxy (Local <-> SSE) with token based authentication.Last updated 9 months ago1MIT