mcp-connect

MCP Connect is a production-ready proxy and multiplexer for the Model Context Protocol (MCP). It lets you connect local MCP clients to remote HTTP MCP servers with OAuth support, manage multiple remote servers through a single connection, and auto-generate IDE configurations for editors like Zed, VSCode, and Cursor. The tool supports registry-based server discovery, token-based authentication, and a centralized .mcp-connect.json configuration file to orchestrate multiple remote MCP servers with namespace routing. You can start a single connection quickly with npx, or manage a multi-server setup by initializing a configuration, adding servers from the MCP Registry, configuring credentials, generating IDE configurations, and starting the proxy with serve. The architecture includes a registry client, a remote proxy, and a client-side component to multiplex requests across servers using namespaces, making it easier to manage access to several remote MCP endpoints from one place.

Prerequisites:

• Rust toolchain (Rust 1.75+ recommended) for building from source
• Optional: Node.js 14+ if you plan to use the npm/npx installation workflow for quick starts

Install from source (recommended for development):

git clone https://github.com/dreygur/mcp-connect.git
cd mcp-connect
cargo install --path crates/mcp-connect

Install a pre-built binary (from releases):

• Download the appropriate binary for Linux/macOS/Windows from the releases page
• Ensure it is in your PATH, e.g. mv mcp-connect /usr/local/bin/

Install via Cargo (builds from crates):

cargo install --git https://github.com/dreygur/mcp-connect

Quick start with npx (no install required):

npx @dreygur/mcp https://remote.server/mcp

If you prefer the npm approach for client-side tooling, ensure Node.js is installed and then run the npm-based install:

npm install -g @dreygur/mcp

Tips and common considerations:

• The MCP Connect configuration is centralized in a .mcp-connect.json file where you can define multiple remote MCP servers under a single namespace and use routing to select servers.
• If you encounter OAuth-related errors, verify that your environment variables (e.g., tokens or client credentials) are correctly configured in an .env file or in the environment before starting the server.
• When generating IDE configurations, the tool can produce configuration snippets for Zed, VSCode, and Cursor to streamline development workflows.
• You can register and discover servers via the MCP Registry to simplify adding new remote endpoints to your configuration.
• Ensure that the remote MCP servers you connect to support the same MCP version and authentication flow expected by MCP Connect to avoid incompatibilities.
• For multi-server setups, namespace routing allows you to address each remote server with a distinct path, enabling clean separation of intents and access control.