MCP Proxy Server

简体中文

✨ Key Features Highlight

• 🌐 Web UI Management: Easily manage all connected MCP servers through an intuitive web interface (optional, requires enabling).
• 🔧 Granular Tool Control: Enable or disable individual tools, and override names/descriptions via the Web UI.
• 🛡️ Flexible Endpoint Authentication: Secure your HTTP-based endpoints (/sse, /mcp) with flexible authentication options (Authorization: Bearer <token> or X-API-Key: <key>).
• 🔄 Robust Session Handling & Concurrency:
  • Improved SSE session handling for client reconnections (relying on server-sent endpoint events) and support for concurrent connections.
  • Streamable HTTP endpoint (/mcp) also supports concurrent client interactions.
• 🚀 Versatile MCP Operations (Server & Proxy):
  • Acts as a Proxy: Connects to and aggregates multiple backend MCP servers of various types (Stdio, SSE, Streamable HTTP).
  • Acts as a Server: Exposes these aggregated capabilities through its own Streamable HTTP (/mcp) and SSE (/sse) endpoints. Can also run in a pure Stdio mode.
• ✨ Real-time Install Output: Monitor Stdio server installation progress (stdout/stderr) directly in the Web UI.
• ✨ Web Terminal: Access a command-line terminal within the Admin UI for direct server interaction (optional, use with caution due to security risks).

---

This server acts as a central hub for Model Context Protocol (MCP) resource servers. It can:

• Connect to and manage multiple backend MCP servers (Stdio, SSE, and Streamable HTTP types).
• Expose their combined capabilities (tools, resources) through a single, unified SSE interface, a Streamable HTTP interface, or act as a single Stdio-based MCP server itself.
• Handle routing of requests to the appropriate backend servers.
• Aggregate responses if needed (though primarily acts as a proxy).
• Support multiple simultaneous SSE client connections with optional API key authentication.

Features

Resource & Tool Management via Proxy

• Discovers and connects to multiple MCP resource servers defined in config/mcp_server.json.
• Aggregates tools and resources from all connected active servers.
• Routes tool calls and resource access requests to the correct backend server.
• Maintains consistent URI schemes.