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.
FlicenseNot gradedqualityDmaintenanceA 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.1Why 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.
FlicenseNot gradedqualityNot gradedmaintenanceBridges STDIO-based MCP clients with SSE-based MCP servers, allowing applications like Claude Desktop to connect to remote MCP servers that use SSE transport.9Why 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.
AlicenseNot gradedqualityDmaintenanceActs 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.15ISCWhy 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.
AlicenseNot gradedqualityDmaintenanceA MCP Proxy (Local <-> SSE) with token based authentication.1MIT