A Model Context Protocol Server that runs as stdio, wrapping a Streamable HTTP server, so any MCP-supporting client can use Streamable HTTP MCP
MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol Server that runs as stdio, wrapping a Streamable HTTP server, so any MCP-supporting client can use Streamable HTTP MCP Servers.
Once MCP is connected, these are the calls the assistant has available:
URI — The URL of the Streamable HTTP MCP Server. This is requiredMCP_NAME — The name of the MCP Server. This is optional. If you configure multiple, this is required so they do not have the same namesBEARER_TOKEN — The Bearer token for the Streamable HTTP MCP Server. This is optional. If specified, this will be sent along in the Authorization headerConfiguration — You can use it via npx in your Claude Desktop configuration like this:Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPAcknowledgements — The Acknowledgements tool exposed by this serverThe server ships on npm as args, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 2 environment variables: MCP_NAME, BEARER_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — URI, MCP_NAME, BEARER_TOKEN and 3 more — is a fair guide to whether it matches your workflow. It is maintained by ferrants; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| 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: |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script: |
| Acknowledgements | The Acknowledgements tool exposed by this server. |
{
"mcpServers": {
"my-saas-app-development": {
"command": "npx",
"args": [
"@pyroprompts/mcp-stdio-to-streamable-http-adapter"
],
"env": {
"URI": "http://localhost:3002/mcp",
"MCP_NAME": "local-custom-streamable-http-adapter"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_NAME | Configuration value read at startup. | Optional |
| BEARER_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.