who-mcp-http

Local no-auth HTTP wrapper for the remote Who MCP service.

This wrapper exposes a local MCP endpoint and forwards JSON-RPC requests to the remote MCP endpoint. Local clients do not need to send ACCESS_CODE or Authorization.

For the remote server, the wrapper defaults to fetching a Microsoft tenant AAD token via Azure CLI and sending it as Authorization: Bearer ....

Run

Install from npm after publishing:

npm install -g who-mcp-http
who-mcp-http

Or run from this checkout:

cd who-mcp-http
cp .env.example .env
npm start

Default local endpoint:

http://127.0.0.1:12346/mcp

Health check:

curl http://127.0.0.1:12346/health

List tools:

curl -sS -X POST http://127.0.0.1:12346/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Configuration

Environment variables can be set in the shell or in who-mcp-http/.env.

• HOST: local bind host, defaults to 127.0.0.1
• PORT: local port, defaults to 12346
• REMOTE_MCP_URL: remote MCP endpoint, defaults to https://who.ttthree.space/mcp
• REMOTE_AUTH_MODE: remote auth mode, defaults to azure-cli; set to none to send no remote auth
• AZURE_TENANT_ID: tenant used for Azure CLI token, defaults to Microsoft tenant 72f988bf-86f1-41af-91ab-2d7cd011db47
• AZURE_TOKEN_RESOURCE: token resource, defaults to https://management.core.windows.net/
• REMOTE_ACCESS_CODE: optional ACCESS_CODE sent only to the remote server
• REMOTE_AUTHORIZATION: optional Authorization header sent only to the remote server

Run az login --tenant 72f988bf-86f1-41af-91ab-2d7cd011db47 first if Azure CLI has no usable cached account.

CLI options override environment values:

who-mcp-http --port 12346 --remote https://who.ttthree.space/mcp

Publish

cd who-mcp-http
npm pack --dry-run
npm publish

The package exposes a who-mcp-http binary and has no npm runtime dependencies. It requires Node.js 18+ and Azure CLI when REMOTE_AUTH_MODE=azure-cli.