If you are using Nginx to reverse proxy MCPHub, please make sure to add the following configuration in your Nginx setup:

proxy_buffering off

🔍 Tech Stack

Backend: Node.js, Express, TypeScript
Frontend: React, Vite, Tailwind CSS
Auth: JWT & bcrypt
Protocol: Model Context Protocol SDK

👥 Contributing

Contributions are welcome!

New features & optimizations
Documentation improvements
Bug reports & fixes
Translations & suggestions

📄 License

Licensed under the Apache 2.0 License.

1d:T2bb3,

MCP Hub

A centralized manager for Model Context Protocol (MCP) servers that provides:

Dynamic MCP server management and monitoring
REST API for tool execution and resource access
Real-time server status tracking
Client connection management
Process lifecycle handling

Overview

Hub Server vs MCP Servers

Hub Server (MCP Hub)
Central management server that connects to and manages multiple MCP servers
Provides unified API endpoints for clients to access MCP server capabilities
Handles server lifecycle, health monitoring, and client connections
Routes requests between clients and appropriate MCP servers
MCP Servers
Individual servers that provide specific tools and resources
Each server has its own capabilities (tools, resources, templates)
Connected to and managed by the Hub server
Process requests from clients through the Hub

Installation

bash npm install -g mcp-hub

Basic Usage

Start the hub server:

bash mcp-hub --port 3000 --config path/to/config.json

CLI Options

bash Options: --port Port to run the server on (default: 3000) --config Path to config file (required) --watch Watch config file for changes (default: false) --shutdown-delay Delay in milliseconds before shutting down when no clients are connected (default: 0) -h, --help Show help information

The server outputs JSON-formatted status messages on startup and state changes:

json { "status": "ready", "server_id": "mcp-hub", "version": "1.0.0", "port": 3000, "pid": 12345, "servers": [], "timestamp": "2024-02-20T05:55:00.000Z" }

Example Integrations

Neovim Integration

The ravitemer/mcphub.nvim plugin provides seamless integration with Neovim, allowing direct interaction with MCP Hub from your editor:

Execute MCP tools directly from Neovim
Access MCP resources within your editing workflow
Real-time status updates in Neovim
Custom commands for common MCP operations

Architecture

Hub Server Lifecycle

Hub Lifecycle

The Hub Server coordinates communication between clients and MCP servers:

Starts and connects to configured MCP servers
Manages client registrations
Routes tool execution and resource requests
Handles server monitoring and health checks
Performs clean shutdown of all connections

MCP Server Management

<

Categories

Current Category: mcp-hub

mcphub

mcp-hub

mcphub.nvim