mcp-http2stdio

Wrap an upstream HTTP MCP server as a local stdio MCP server.

Quick Start

Run directly with npx:

npx -y @yglabs/mcp-http2stdio@latest --url <upstream-mcp-http-url>

Global install:

npm install -g @yglabs/mcp-http2stdio
mcp-http2stdio --url <upstream-mcp-http-url>

Usage

mcp-http2stdio --url <upstream-mcp-http-url> [--account <upn>] [--client-id <guid>]

Options:

• --url: required upstream HTTP MCP server URL.
• --account: optional MSAL account hint.
• --client-id: optional OAuth client id. Defaults to aebc6443-996d-45c2-90f0-388ff96faa56.

Behavior

• Local transport is stdio MCP.
• Upstream transport is HTTP MCP.
• Requests and notifications are transparently proxied to the upstream server.
• initialize is not handled locally; it is forwarded upstream like any other MCP request.
• default client-id is aebc6443-996d-45c2-90f0-388ff96faa56

MCP Client Configuration

[mcp_servers.http_proxy]
enabled = true
command = "npx"
args = ["-y", "@yglabs/mcp-http2stdio@latest", "--url", "<upstream-mcp-http-url>"]

Authentication

Authentication follows the @microsoft/workiq MSAL flow as closely as practical, with one intentional local change:

• token cache root: ~/.mcp-http2stdio
• token cache file: ~/.mcp-http2stdio/msal_token_cache.dat

On Windows this resolves to:

C:\Users\<user>\.mcp-http2stdio\msal_token_cache.dat

macOS Broker

macOS defaults to browser-based auth (http://localhost redirect). To enable the broker path used by @microsoft/workiq, create:

~/.mcp-http2stdio/.mcp-http2stdio.json

with:

{
  "enableMacBroker": "true"
}

Development

Build the project:

dotnet build McpHttp2Stdio.slnx

Publish native binaries into the npm package layout:

npm run publish:npm

Verify the npm tarball layout and executable shim:

npm run release:verify

Create a local tarball:

npm run pack:npm

Publish to npm:

npm publish --access public