home / mcp / mcp http-stdio proxy mcp server

MCP HTTP-stdio Proxy MCP Server

Bridges stdio MCP clients with HTTP-based MCP servers, handling session management, authentication, and retries.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "kiennh-mcp-http-stdio": {
      "url": "https://your-remote-mcp-server.com/mcp",
      "headers": {
        "UPSTREAM_AUTH": "Bearer YOUR_TOKEN",
        "MCP_SESSION_ID": "<MCP_SESSION_ID>",
        "MCP_TIMEOUT_MS": "15000",
        "UPSTREAM_MCP_URL": "https://your-remote-mcp-server.com/mcp"
      }
    }
  }
}

You can bridge stdio-based MCP clients with HTTP-based MCP servers using a dedicated proxy. This MCP HTTP-stdio Proxy translates stdio JSON-RPC to HTTP, manages sessions, and lets you work with remote or HTTP-hosted MCP servers as if they were local stdio servers. It also supports optional authentication, automatic retries, and a configurable timeout.

How to use

To connect a stdio MCP client to a remote HTTP MCP server, run the proxy and point it to the upstream server URL. You can interact with the upstream MCP server through your familiar stdio client as if it were local.

Two common usage approaches are shown: running the proxy directly with a URL and using a package runner. Choose the approach that fits your workflow.

How to install

Prerequisites: ensure you have Node.js and npm installed on your machine.

Install dependencies for the proxy project.

npm install

Available tools

update

A built-in tool that refreshes the upstream connection by clearing the local session cache and forcing a reinitialization on the next request.