MCP Server Hub / Gateway

Created By
bsmi021a year ago
This project provides a central gateway to manage multiple MCP (Model Context Protocol) servers, preventing the need to configure and run duplicate server processes for each LLM client (like Cline, Cursor, etc.). Connect your LLM client to the single gateway-client endpoint provided by this project to access tools from all your managed MCP servers
Overview

What is MCP Server Hub / Gateway?

MCP Server Hub / Gateway is a project that provides a central gateway to manage multiple Model Context Protocol (MCP) servers, allowing users to connect their LLM clients to a single endpoint without the need for duplicate server processes.

How to use MCP Server Hub / Gateway?

To use the MCP Server Hub, clone the repository, install dependencies, build the project, configure the mcp_hub_config.json file, and start the server. Connect your LLM client to the gateway-client endpoint to access tools from all managed MCP servers.

Key features of MCP Server Hub / Gateway?

  • Centralized management of multiple MCP servers.
  • Dynamic configuration reloading without server restarts.
  • WebSocket support for real-time communication with LLM clients.
  • Namespaced tool access for organized tool management.

Use cases of MCP Server Hub / Gateway?

  1. Managing multiple LLM clients like Cline and Cursor through a single gateway.
  2. Dynamically updating server configurations and tools without downtime.
  3. Simplifying the integration of various tools and services in a unified interface.

FAQ from MCP Server Hub / Gateway?

  • What is the purpose of the MCP Server Hub?

It centralizes the management of multiple MCP servers, making it easier to connect LLM clients to various tools.

  • Is it necessary to configure each MCP server individually?

No, you can manage all servers through the central gateway configuration.

  • Can I use this with any LLM client?

Yes, as long as the client supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bsmi021
Star
0
Language
TypeScript
License
GPL-3.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago