1. Conduid
  2. Browser
  3. Connect
MCP server · Browser

Connect

A Rust implementation of the Model Context Protocol (MCP) remote proxy that bridges local MCP clients (IDEs/LLMs) with remote MCP servers via HTTP/SSE transport.

Unclaimed last commit 6 months ago climcpmcp-clientmcp-serverproxyrust
34Low

Scored 4 days ago · breakdown

About Connect

Connect is an MCP server published by dreygur in the Browser category: a Rust implementation of the Model Context Protocol (MCP) remote proxy that bridges local MCP clients (IDEs/LLMs) with remote MCP servers via HTTP/SSE transport.

The repository has 6 stars and 0 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/dreygur/mcp-connect

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Connect

Powered by Claude · Grounded in docs

I know everything about Connect. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 2 hours ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • ✓Tests presentA test suite exists in the repository.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.

1 check has not been run yet.

Releases

v0.3.6v0.3.6 · 7 Jan 2026
v0.3.5v0.3.5 · 6 Jan 2026
v0.3.4v0.3.4 · 6 Jan 2026
v0.3.3v0.3.3 · 5 Jan 2026
v0.3.2v0.3.2 · 5 Jan 2026

README

MCP Connect

Rust npm GitHub stars

A production-ready proxy and multiplexing server for the Model Context Protocol (MCP). MCP Connect enables seamless integration between local MCP clients and remote HTTP servers with OAuth support.

Works With

Connect your favorite AI agents to remote MCP servers:

Agent Description
Claude Desktop Anthropic's official desktop app
Claude Code Anthropic's CLI coding assistant
Cursor AI-powered code editor
Windsurf Codeium's AI IDE
Zed High-performance code editor
Continue Open-source AI assistant for VSCode/JetBrains

Features

  • Remote Server Support - Connect to multiple remote MCP servers via HTTP/HTTPS
  • OAuth Authentication - Automatic OAuth 2.0 flow with token caching
  • Centralized Configuration - Manage all servers in a single .mcp-connect.json file
  • Registry Integration - Search and discover servers from the official MCP Registry
  • Multiplexing - Access multiple servers through a single connection with namespace routing
  • IDE Integration - Auto-generate configuration for Zed, VSCode, and Cursor

Installation

npx (no install)

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

npm (global install)

npm install -g @dreygur/mcp

Shell script (Linux/macOS)

curl -fsSL https://raw.githubusercontent.com/dreygur/mcp-connect/main/scripts/install.sh | bash

PowerShell (Windows)

irm https://raw.githubusercontent.com/dreygur/mcp-connect/main/scripts/install.ps1 | iex

Cargo

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

# From crates.io (when published)
cargo install mcp-connect

From source

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

Pre-built binaries

Download from releases page for:

  • Linux (x86_64)
  • macOS (x86_64, ARM64)
  • Windows (x86_64)

Quick Start

One-off connection (no config needed):

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

With auth token:

npx @dreygur/mcp https://api.example.com/mcp --auth-token "your_token"

Multi-server setup:

# Initialize configuration
mcp-connect init

# Add a server from registry
mcp-connect config add github modelcontextprotocol/github-mcp-server

# Configure credentials
echo "GITHUB_TOKEN=your_token" >> .env

# Generate IDE configuration
mcp-connect generate --ide vscode

# Start the server
mcp-connect serve

Documentation

Full documentation is available at dreygur.js.org/mcp-connect

Architecture

crates/
├── mcp-types/      # Common types and traits
├── mcp-server/     # Server-side MCP (STDIO)
├── mcp-client/     # Client for remote HTTP servers
├── mcp-proxy/      # Message forwarding and routing
├── mcp-registry/   # MCP Registry API client
├── mcp-config/     # Configuration management
└── mcp-connect/    # CLI

See ARCHITECTURE.md for details.

Configuration Example

{
  "version": "1.0",
  "envFile": ".env",
  "routing": {
    "method": "namespace-prefix",
    "separator": "/"
  },
  "servers": {
    "github": {
      "name": "github-mcp-server",
      "remote": {
        "type": "streamable-http",
        "url": "https://api.githubcopilot.com/mcp",
        "headers": [
          {
            "key": "Authorization",
            "value": "Bearer ${GITHUB_TOKEN}"
          }
        ]
      }
    }
  }
}

Requirements

  • Node.js 14+ (for npm installation)
  • Rust 1.75+ (for building from source)

Contributing

See Contributing Guide for details.

License

MIT License - see LICENSE for details.

Support

If you find MCP Connect useful, please consider giving it a star on GitHub! It helps others discover the project.

Star on GitHub

Acknowledgments

  • RMCP - Rust SDK for Model Context Protocol
  • Tokio - Asynchronous runtime for Rust

README fetched from the repository 2 hours ago. The original is authoritative.

Questions

About Connect

How do I install Connect?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Connect safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 4 of the 5 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Connect still maintained?

The last commit was 6 months ago and 6 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.