Issuer MCP stdio proxy

This package lets MCP clients that only support stdio connect to your local Issuer MCP server over Streamable HTTP.

The npm package does not contain or deploy the Issuer Java service. It only contains a tiny Node.js stdio-to-HTTP bridge for npx. Your Java service still runs locally and exposes /mcp.

MCP client config

{
  "mcpServers": {
    "issuer": {
      "command": "npx",
      "args": [
        "-y",
        "@snn-syy-799/issuer-mcp-stdio",
        "--url",
        "http://127.0.0.1:8080/mcp"
      ],
      "env": {
        "ISSUER_MCP_TOKEN": "Bearer <mcp-token>"
      }
    }
  }
}

For local development:

{
  "mcpServers": {
    "issuer-local": {
      "command": "node",
      "args": [
        "/absolute/path/to/issuer/mcp-stdio-proxy/bin/issuer-mcp-stdio.js",
        "--url",
        "http://127.0.0.1:8080/mcp"
      ],
      "env": {
        "ISSUER_MCP_TOKEN": "Bearer <mcp-token>"
      }
    }
  }
}

Publish

cd mcp-stdio-proxy
npm install
npm publish --access public

If you publish to a private company registry, set the registry before publishing:

npm publish --registry https://registry.example.com

Runtime options

npx -y @snn-syy-799/issuer-mcp-stdio --url http://127.0.0.1:8080/mcp --token 'Bearer <mcp-token>'

Supported environment variables:

• ISSUER_MCP_URL, default http://127.0.0.1:8080/mcp
• ISSUER_MCP_TOKEN
• ISSUER_MCP_AGENT_RUN_ID, optional; defaults to a generated UUID and is forwarded as X-Agent-Run-Id

ISSUER_MCP_TOKEN and --token both accept either the raw token or Bearer <token>. The proxy adds Bearer automatically when it is missing.

Use -H "Header: value" when extra gateway headers are required.

Why not curl?

stdio MCP needs a long-running process that reads JSON-RPC from stdin and writes JSON-RPC to stdout. curl makes one HTTP request and exits, so it cannot be the stdio MCP server by itself. Use npx @snn-syy-799/issuer-mcp-stdio in the stdio command instead.