Overview
Features
STDIO-to-Streamable HTTP bridge
Relays MCP requests from STDIO-based clients to a Streamable HTTP MCP Server, enabling HTTP transport without rewriting clients.
Broad client compatibility
Enables MCP clients that only support STDIO to work with Streamable HTTP servers.
Env-based configuration
Configure connection with URI (required), MCP_NAME (optional for multiple servers), and BEARER_TOKEN (optional for Authorization header).
Multiple provider configurations
Configure several providers referencing the same MCP server with different environment variables.
Npx or local build deployment
Deploy via npx or build a local index.js to run the adapter in your environment.
Debugging with MCP Inspector
Use the MCP Inspector for debugging via the npm run inspector script.
Claude Desktop and LibreChat readiness
Provides example configurations to integrate with Claude Desktop and LibreChat environments.
Development workflow
Standard npm workflows: install, build, and watch for auto-rebuild during development.
Who Is This For?
- MCP integrators:Bridge STDIO MCP clients to Streamable HTTP MCP Servers to enable HTTP transport.
- Claude Desktop users:Configure Claude Desktop to access Streamable HTTP MCP Servers via this adapter.
- LLM developers:Connect LLMs to MCP servers via STDIO-to-HTTP bridging.




