punkpeye/mcp-remote

Health v2 · maintenance only

Adoption not part of the score

1562 stars · 285 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A Node.js CLI proxy that lets MCP clients which only support local stdio servers connect to remote MCP servers over HTTP/SSE, including OAuth authorization flows. It is dropped into the standard mcpServers config of clients like Claude Desktop, Cursor, and Windsurf as a one-line npx command.

Use cases

• connect Claude Desktop to a remote MCP server
• use remote MCP servers in Cursor or Windsurf that only support stdio
• add OAuth-authenticated remote MCP servers to a stdio-only client
• pass custom authorization headers to a remote MCP server
• run multiple isolated OAuth sessions against the same remote MCP server
• bridge local MCP clients to SSE-based servers without native remote support

When to choose

• your MCP client only supports local stdio servers but you need a remote server
• you need OAuth flows for remote MCP servers that your client doesn't implement
• you want a quick npx-based bridge with no install step

When to avoid

• your MCP client already natively supports remote HTTP/SSE servers with auth
• you need a production-hardened solution rather than a proof-of-concept
• you only use local stdio MCP servers

Facets

cli-tool · maturity experimental

mcp auth proxy http-client developer-tools developer-tools apis security cross-platform cli mcp-proxy stdio-to-sse oauth model-context-protocol remote-servers ai-agents nodejs

Member repositories

For agents

markdown · JSON · MCP: product_card(name="punkpeye/mcp-remote")