MCP Connect
A proxy and multiplexing server bridging local MCP clients to remote HTTP servers.
MCP Connect lets local Model Context Protocol clients reach remote MCP servers over HTTP/HTTPS, with OAuth handled for them. It removes the assumption that every MCP server has to run as a local process on the developer's machine.
Run without installing
npx @dreygur/mcp https://remote.server/mcpThe gap it fills
MCP clients generally expect to spawn servers locally over stdio. That works for a local filesystem tool and stops working as soon as the server is a hosted service that needs credentials.
MCP Connect sits between the two: the client talks to it as a normal local MCP server, and it talks to remote servers over HTTP/HTTPS.
Authentication
The OAuth 2.0 flow runs automatically, with token caching, so the client does not need to know that authentication happened at all.
Multiplexing
Several remote servers are reachable through a single connection, with namespace routing keeping their tools distinct.
Servers are declared in one `.mcp-connect.json` file rather than scattered across per-client configuration, and MCP Connect can generate the client-side configuration for Zed, VSCode, and Cursor from it.
Discovery
Registry integration searches the official MCP Registry, so finding a server does not mean already knowing its URL.
Clients it works with
Claude Desktop, Claude Code, Cursor, Windsurf, Zed, and Continue — anything speaking MCP over stdio.
Installation paths
Available through npx with no install, npm as a global package, a shell installer for Linux and macOS, PowerShell for Windows, and Cargo from source.