Truto MCP Stdio Proxy

What is Truto MCP Stdio Proxy?

Truto MCP Stdio Proxy is a CLI program that acts as a stdio proxy for HTTP Streamable MCP servers. It reads newline-delimited JSON-RPC messages from stdin, forwards them as POST requests to a specified MCP server endpoint, and writes the responses to stdout. It is intended for developers using clients (like Claude) that expect a stdio-based MCP server but need to communicate with an HTTP-based Streamable MCP server.

How to use Truto MCP Stdio Proxy?

Download a pre-built binary for your platform (Linux, macOS Intel/Apple Silicon, or Windows) from the GitHub releases page and make it executable. Run it from the command line with the required <API_URL> argument, piping JSON-RPC messages via stdin or reading from a file. For example: echo '{"jsonrpc":"2.0","method":"example","params":{},"id":1}' | ./truto-mcp-stdio-linux-amd64-v1.0.0 https://api.truto.one/mcp/<id>. It can also be configured directly in Claude’s mcpServers settings.

Key features of Truto MCP Stdio Proxy

• Forwards JSON‑RPC messages from stdin to any HTTP Streamable MCP endpoint
• Writes API responses to stdout and error messages to stderr
• Single‑binary, no runtime dependencies beyond the OS
• Supports Linux, macOS (Intel & Apple Silicon), and Windows
• Can be built from source with Go 1.24.2 or later
• Integrates with Claude’s MCP configuration as a stdio server entry

Use cases of Truto MCP Stdio Proxy

• Use MCP tools from a CLI by piping JSON‑RPC requests
• Connect a stdio‑only MCP client (e.g., Claude) to a remote HTTP Streamable MCP server
• Test and debug MCP APIs locally without a full HTTP client

FAQ from Truto MCP Stdio Proxy

What is the required runtime?

Building from source requires Go 1.24.2 or later. Pre‑built binaries have no runtime dependencies.

How does it transport messages?

It uses stdio for input/output and forwards messages to a remote server via HTTP POST (Streamable HTTP transport). Errors are written to stderr.

Can I use it with Claude?

Yes. Add a configuration entry in Claude’s MCP settings with the binary as the command and the API URL as an argument.

What format does the input expect?

Newline‑delimited JSON‑RPC 2.0 messages read from stdin. Output is the raw API response written to stdout.

Does the proxy support authentication?

No authentication options are documented in the README. The API URL is passed directly as a command‑line argument.