AgentDNS-Node
AgentDNS·Node makes it easy to manage and scale multiple MCP (Model Context Protocol) servers by organizing them into flexible Streamable HTTP (SSE) endpoints—supporting access to all servers, individual servers, or logical server groups.
claude mcp add --transport stdio jsjfai-agentdns-node npx -y @amap/amap-maps-mcp-server \ --env AMAP_MAPS_API_KEY="your-api-key"
How to use
AgentDNS-Node acts as a unified hub for multiple MCP servers. It organizes individual MCP instances into a single, streamable HTTP interface, allowing clients to connect to all servers collectively, to specific servers, or to logical groups. The dashboard provides real-time visibility into server status and performance, while the SSE/HTTP endpoints enable seamless integration with AI clients and tools. Tools available through this hub include a diverse set of MCP servers (examples shown in the configuration: amap for maps MCP, playwright MCP, fetch MCP, and a Slack MCP) and the ability to route requests to them via the /mcp endpoints or via group/server-scoped endpoints. You can also enable Smart Routing to automatically discover and execute relevant tools using vector search over tool embeddings.
How to install
Prerequisites:
- Node.js and npm (or pnpm) installed on your system
- Optional: Docker if you prefer containerized deployment
- Access to required MCP server packages (via npm/npx) as shown in the configuration
- Clone the repository (or download the release package):
- git clone https://github.com/samanhappy/mcphub.git
- cd mcphub
- Install dependencies (choose package manager you prefer):
- pnpm install or
- npm install
- Prepare your MCP configuration file (mcp_settings.json):
- Create a file named mcp_settings.json in the project root
- Paste the configuration from the README (see mcp_config example) and replace placeholder values with real credentials (e.g., API keys, tokens)
- Start the server:
- Using pnpm (development):
- pnpm dev
- Or build/run a specific mode according to your setup (see Docker option below)
- Verify the dashboard and endpoints:
- Open http://localhost:3000 to access the dashboard
- Use the /mcp endpoint (e.g., http://localhost:3000/mcp) to connect clients to the unified streamable interface
Additional notes
Tips and notes:
- The mcp_settings.json supports hot-swapping; you can add, remove, or update MCP servers without downtime.
- If you’re running behind a reverse proxy (e.g., Nginx), consider disabling proxy buffering as recommended in the docs.
- For Docker deployments, you can mount your custom mcp_settings.json as shown in the Docker example to avoid rebuilding the image for config changes.
- Smart Routing is an optional feature that relies on PostgreSQL with pgvector and an OpenAI-compatible embedding service; ensure these services are available and configured in the hub settings to enable it.
- Group-based endpoints allow you to isolate access per environment or team; remember that group name takes precedence if a server name overlaps with a group name.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud