Best for
- Developers needing to integrate local MCP servers with cloud AI services
- Those needing to bridge existing stdio MCP servers over HTTP
- Users requiring session management and secure authentication
M
MCP Connect
Community
Lightweight bridge that exposes local MCP servers as HTTP APIs
GitHub source repository ↗
40FMRS · D
MCP Connect provides a practical bridge solution for converting local MCP servers into HTTP-callable services. It addresses the limitation of cloud AI services that cannot directly use stdio protocol, supports multiple invocation modes, and enhances security. Suitable for developers needing remote integration of MCP tools, but care must be taken with security configurations. Open source under MIT license.
MCP Connect is an HTTP gateway that lets you call local MCP servers (that speak stdio) through Streamable HTTP or a classic request/response bridge. It supports session management, Bearer token authentication, CORS allowlist, built-in Ngrok tunnel, and one-click deploy to E2B cloud sandbox. Features dual modes: Streamable HTTP mode with unique routes per MCP server, and a non-standard /bridge endpoint. Suitable for integrating local MCP tools into remote cloud AI clients.
Tools
The tool list has not been reviewed yet.
Setup
- Clone the repo: git clone https://github.com/EvalsOne/MCP-connect.git && cd mcp-connect
- Install dependencies: npm install
- Copy .env.example to .env and set ACCESS_TOKEN (required).
- (Optional) Edit mcp-servers.json to configure MCP servers for Streamable HTTP mode.
- Build and start: npm run build && npm start.
- Check http://localhost:3000/health to verify status.
Fit and risk
Not for
- Scenarios requiring fully native MCP protocol without extra bridging
- Pure local MCP use without remote access
- Users seeking minimal configuration
Required permissions
- Requires setting ACCESS_TOKEN environment variable
- May need to configure ALLOWED_ORIGINS to restrict cross-origin
- If using Ngrok, provide NGROK_AUTH_TOKEN
- If using E2B, provide E2B_API_KEY
Risks and side effects
- Exposing local services to the public internet carries security risks
- Bridging may introduce latency
- Misconfiguration may prevent the server from starting
Troubleshooting
- Verify ACCESS_TOKEN is set, otherwise startup fails
- Ensure mcp-servers.json is configured, otherwise Streamable HTTP endpoints are unavailable
- Check /health endpoint for server status
- Inspect combined.log or error.log for details
Use cases
Allow cloud AI tools to access local MCP servers
Expose MCP servers as HTTP endpoints for remote clients
Provide public access to local MCP via Ngrok
Quickly deploy MCP servers in E2B cloud sandbox
Supported clients
Supported clients have not been confirmed yet.