官方说明3 个来源MCP 服务3 天前

EvalsOne/MCP-connect

Cloud AI access to local Stdio MCP servers

在 GitHub 查看 ↗直链 · 无中转页

来源明细: 收录自 abordage/awesome-mcp 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
收录与活跃: 收录于 2026-10-14 · 最近见到 2026-10-16 · 共见到 4 次 · 被 3 个来源列出
评分构成: 综合分 303 · 3 个来源 · mcp

常见问题（答案都来自我们的记录）

怎么安装？

我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。

它适合谁 / 用来做什么？

我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。

谁维护它、还在更新吗？

我们收录于 2026-10-14；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。

第三方质量标记

MCP Connect

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

███╗ ███╗ ██████╗██████╗ ██████╗ ██████╗ ███╗ ██╗███╗ ██╗███████╗ ██████╗████████╗
████╗ ████║██╔════╝██╔══██╗ ██╔════╝██╔═══██╗████╗ ██║████╗ ██║██╔════╝██╔════╝╚══██╔══╝
██╔████╔██║██║ ██████╔╝ ██║ ██║ ██║██╔██╗ ██║██╔██╗ ██║█████╗ ██║ ██║
██║╚██╔╝██║██║ ██╔═══╝ ██║ ██║ ██║██║╚██╗██║██║╚██╗██║██╔══╝ ██║ ██║
██║ ╚═╝ ██║╚██████╗██║ ╚██████╗╚██████╔╝██║ ╚████║██║ ╚████║███████╗╚██████╗ ██║
╚═╝ ╚═╝ ╚═════╝╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═══╝╚═╝ ╚═══╝╚══════╝ ╚═════╝ ╚═╝
**Lightweight bridge that exposes local MCP servers as HTTP APIs**
---
What Is MCP Connect?
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.
What's New
- Added Streamable HTTP mode on top of the classic request/response bridge
- New quick-deploy scripts and configs under deploy/e2b for launching in an E2B sandbox
How It Works
**Key Features**
| Feature | Description |
|--------|-------------|
| 🚀 Dual modes | Call local stdio MCP servers via Streamable HTTP or the classic HTTP bridge |
| 🔄 Session management | Maintain conversational continuity with sessions |
| 🔐 Security | Bearer token auth + CORS allowlist |
| 🌐 Public access | Built-in Ngrok tunnel to expose endpoints externally |
| ☁️ Cloud deploy | One-click deploy to E2B cloud sandbox |
---
Quick Start
Prerequisites
- Node.js >= 22.0.0 (recommended)
- npm or yarn
1) Install
2) Preparations
**A. Set up initial environment variables**
Set ACCESS_TOKEN in .env before starting the server. Startup fails if it is empty.
**B. Configure MCP servers**
For Streamable HTTP method, each MCP server needs to be configurated separately, edit file to add more configurations other than the existing sample servers.
3) Run
After you see the startup banner, visit http://localhost:3000/health to check server status.
---
Usage
Mode 1: Streamable HTTP bridge
General-purpose and compatible with any MCP client that supports Streamable HTTP.
In Streamable HTTP mode, each MCP server is assigned a unique route. Example: add the fetch MCP server in mcp-servers.json.
Once started, access the fetch MCP server with your favorite MCP client (e.g. Claude Code, Cursor, Codex, GitHub Copilot...)
Note: You must configure mcp-servers.json before starting the service, otherwise the server won't be available.
---
Mode 2: Classic request/response bridge
Non-standard invocation where you implement methods like tools/list, tools/call, etc.
Include Authorization: Bearer in every request header. ACCESS_TOKEN is required at startup.
Example 1: List available tools
Example 2: Call a tool
Security
Authentication
MCP Connect requires a token-based authentication system. Set ACCESS_TOKEN in .env before startup. If it is empty, the server exits with a configuration error.
Allowed Origins
In production, set ALLOWED_ORIGINS to restrict cross-origin requests:
If ALLOWED_ORIGINS is set, non-matching origins are rejected.
---
API Reference