Official description3 sourcesMCP servers3d ago

pyroprompts/mcp-stdio-to-streamable-http-adapter

STDIO to Streamable HTTP proxy

View on GitHub ↗Direct link · no redirect page

Official descriptionr MCP Server Integrate any MCP Client that has STDIO MCP Server Support (most do) with the Streamable HTTP MCP Servers If you have a Streamable HTTP MCP Server, forking this, hardcoding the URI and publishing will give you a repo that you can point to, add to directories and let people use via STDIO.

Source: collected from the abordage/awesome-mcp list · type: MCP server
Harvest history: first seen 2026-10-14 · last seen 2026-10-16 · seen 4× · listed by 3 sources
Score: score 303 · 3 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

first catalogued 2026-10-14；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

mcp-stdio-to-streamable-http-adapter MCP Server

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

Integrate any MCP Client that has STDIO MCP Server Support (most do) with the Streamable HTTP MCP Servers
If you have a Streamable HTTP MCP Server, forking this, hardcoding the URI and publishing will give you a repo that you can point to, add to directories and let people use via STDIO.
_Note_: This has similarities to the mcp-remote package
Why?
The MCP Spec to add a Streamable HTTP Transport landed end of March 2025 and as of the end of April, no clients have adopted support. The typescript-sdk has merged the code, but not released. The Python SDK is still in development to support it. The Inspector supports it, but that's it.
This leaves developers in an awkward position. Develop the MCP Server using STDIO or SSE (deprecated) so it works with clients or develop with Streamable HTTP transport, but nobody can use it.
I (ferrants) want to start integrating the Streamable HTTP MCP Servers beyond just the inspector, so I need a way to connect them to clients and LLMs right away!
This package aims to bridge the cap by being a STDIO MCP Server that relays to your Streamable HTTP MCP Server. This makes all MCP Clients support Streamable HTTP right away. And now developers can develop the Streamable HTTP MCP Servers and provide an installation method.
Installation
To add OpenAI to Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Env Vars
- URI: The URL of the Streamable HTTP MCP Server. This is required.
- MCP_NAME: The name of the MCP Server. This is optional. If you configure multiple, this is required so they do not have the same names.
- BEARER_TOKEN: The Bearer token for the Streamable HTTP MCP Server. This is optional. If specified, this will be sent along in the Authorization header.
Configuration
You can use it via npx in your Claude Desktop configuration like this:
Or, if you clone the repo, you can build and use in your Claude Desktop configuration like this:
You can add multiple providers by referencing the same MCP server multiple times, but with different env arguments:
With these three, you'll see a tool for each in the Claude Desktop Home:
And then you can chat with other LLMs and it shows in chat like this:
Or, configure in LibreChat like:
And it shows in LibreChat:
Development
Install dependencies: