MCPHub
Acts as a unified gateway for the GitHub MCP server, allowing AI clients to interact with GitHub repositories, issues, and environment variables through a single managed endpoint.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCPHubshow the status and available tools for all my connected servers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🔱 MCPHub
One gateway to rule them all
A unified gateway and dashboard for managing multiple MCP (Model Context Protocol) servers. Think "Docker Compose + Dashboard" for MCP servers.
Quick Start · Features · Config Reference · Contributing
😩 Why MCPHub?
If you work with AI tools in 2026, you probably have multiple MCP servers — filesystem, GitHub, databases, APIs. Managing them is painful:
❌ Scattered configs — every AI client needs its own MCP server list
❌ No visibility — which servers are running? What tools are available?
❌ No single endpoint — each client connects to each server separately
❌ Restart hell — add a server = restart everything
MCPHub fixes all of this:
✅ One YAML file to define all your MCP servers
✅ One gateway endpoint that routes to the right server
✅ Beautiful dashboard showing status, tools, and stats
✅ Hot reload — edit config, servers update instantly
🏗️ Architecture
┌─────────────────────────────────────────────────┐
│ AI Clients │
│ (Claude, Cursor, Copilot, etc.) │
└──────────────────┬──────────────────────────────┘
│ MCP Protocol (stdio)
▼
┌─────────────────────────────────────────────────┐
│ 🔱 MCPHub Gateway │
│ │
│ ┌──────────┐ ┌──────────┐ ┌───────────────┐ │
│ │ Registry │ │ Router │ │ Health Check │ │
│ └──────────┘ └──────────┘ └───────────────┘ │
│ │
│ ┌──────────────────────────────────────────┐ │
│ │ 🌐 Web Dashboard (:3000) │ │
│ └──────────────────────────────────────────┘ │
└──────┬──────────────┬──────────────┬────────────┘
│ │ │
▼ ▼ ▼
┌────────────┐ ┌────────────┐ ┌────────────┐
│ filesystem │ │ github │ │ postgres │
│ server │ │ server │ │ server │
└────────────┘ └────────────┘ └────────────┘🚀 Quick Start
1. Install
npm install -g mcphub2. Create mcphub.yaml
mcphub:
port: 3000
servers:
- name: filesystem
command: npx
args: ["-y", "@modelcontextprotocol/server-filesystem", "/home/user"]
- name: github
command: npx
args: ["-y", "@modelcontextprotocol/server-github"]
env:
GITHUB_TOKEN: "${GITHUB_TOKEN}"3. Run
mcphubOpen http://localhost:3000 to see the dashboard 🎉
✨ Features
Feature | Description |
🔱 Unified Gateway | Single MCP endpoint that routes to all downstream servers |
📋 One Config | Define all MCP servers in one |
🌐 Web Dashboard | Beautiful dark-themed UI showing servers, tools, and stats |
🔄 Hot Reload | Edit config → servers update automatically, no restart needed |
🔍 Tool Discovery | Auto-discovers all tools from all connected servers |
💓 Health Checks | Periodic health monitoring of all downstream servers |
📊 Usage Stats | Request counts and error tracking per server |
🔌 Env Variables | Reference |
📖 Config Reference
mcphub:
port: 3000 # Dashboard port (default: 3000)
log_level: info # debug | info | warn | error
servers:
- name: my-server # Unique server name (required)
command: npx # Command to start the server (required)
args: ["-y", "pkg"] # Command arguments (optional)
enabled: true # Enable/disable without removing (optional)
env: # Environment variables (optional)
KEY: "value"
SECRET: "${FROM_ENV}" # Reference host env varsEnvironment Variable Substitution
Use ${VAR_NAME} in any string value to reference the host environment:
env:
GITHUB_TOKEN: "${GITHUB_TOKEN}" # From host env
DATABASE_URL: "${DATABASE_URL}"🔧 Using with AI Clients
Configure your AI client to connect to MCPHub instead of individual servers:
{
"mcpServers": {
"mcphub": {
"command": "mcphub",
"args": ["/path/to/mcphub.yaml"]
}
}
}All tools from all configured servers are now available through this single connection.
🤝 Contributing
Contributions are welcome! Here's how:
Fork the repo
Create your feature branch:
git checkout -b feat/amazing-featureCommit:
git commit -m 'Add amazing feature'Push:
git push origin feat/amazing-featureOpen a Pull Request
Development
git clone https://github.com/NeuZhou/mcphub.git
cd mcphub
npm install
npm run dev📄 License
MIT © Kang Zhou
🔱 One gateway to rule them all 🔱
If MCPHub helps you, consider giving it a ⭐
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
One PAT, any MCP agent: Vercel, GitHub, Cloudflare, Supabase, GCP — unified dev infra gateway.
Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NeuZhou/mcphub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server