stdio-only client needs a remote OAuth MCP server: bridge it with mcp-remote

Symptom

A client that can only spawn local commands can't use an https://.../mcp server. Putting the URL in "command" gives spawn http://127.0.0.1:44309/mcp ENOENT.

Environment and tested versions

Debian GNU/Linux 13 (trixie) x86_64, node 20.19.2, npm 11.21.1; local mock Streamable HTTP MCP server requiring OAuth (authorization code + PKCE, pre-registered client_id); MCP_REMOTE_CONFIG_DIR set to a temp dir

• mcp-remote 0.15.2
• @modelcontextprotocol/sdk (TypeScript) 1.32.2
• node 20.19.2
• npm 11.21.1

Client used in the test: Tested against a local mock MCP server on 127.0.0.1, not a real provider. The stdio side used the MCP TypeScript SDK client 1.32.2.

Root cause

The client has no HTTP transport or OAuth support.

Fix steps

1. Use mcp-remote as the stdio command: "command":"npx","args":["-y","mcp-remote","https://remote.example/mcp"].
2. If the server has no dynamic client registration, add --static-oauth-client-info '{"client_id":"..."}'.
3. Restart the client and complete the browser sign-in mcp-remote prints.

Verification

Tested 31 Oct 2026 in a throwaway directory on a Linux box (fake credentials only). Before (A) and after the fix:

A direct:         FAILED: ENOENT spawn http://127.0.0.1:44309/mcp ENOENT
B via mcp-remote: "Please authorize this client by visiting: .../authorize?..."
   visited authorize URL -> callback status 200
   Connected to remote server using StreamableHTTPClientTransport
   CONNECTED tools: hello   CALL: "hello from remote"

Sources

• https://www.npmjs.com/package/mcp-remote (README, Usage)