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.
What is AgentDNS Node?
AgentDNS Node is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to 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, individ...
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.
This server falls under the Cloud Services category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- AgentDNS·Node makes it easy to manage and scale multiple MCP
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx agentdns-nodeConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use AgentDNS Node
AgentDNS Node is a hub-and-router for MCP servers that aggregates multiple downstream MCP servers into flexible Streamable HTTP endpoints, making it easy to manage and scale AI agent tool infrastructure. It provides a unified /mcp endpoint that exposes all registered servers' tools at once, plus server-specific and group-based endpoints for fine-grained routing. Teams use it to consolidate sprawling collections of MCP servers behind a single address, apply semantic tool discovery, and manage access control via named server groups.
Prerequisites
- Docker installed (for the recommended deployment method)
- Node.js 18+ and pnpm if running locally from source
- At least one downstream MCP server to register (e.g., an SSE or stdio server)
- An MCP-compatible client that supports HTTP/SSE transport such as Claude Desktop or Cursor
- Port 3000 available on the host machine
Create the server settings file
Create a mcp_settings.json file that lists the downstream MCP servers AgentDNS Node should aggregate. Each entry defines a server name, transport type, and connection details.
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": ["mcp-server-fetch"]
},
"playwright": {
"command": "npx",
"args": ["@playwright/mcp"]
}
}
}Start with Docker (recommended)
Run AgentDNS Node via Docker, mounting your mcp_settings.json file into the container. The service will start on port 3000.
docker run -p 3000:3000 \
-v ./mcp_settings.json:/app/mcp_settings.json \
samanhappy/mcphubOr run locally with pnpm
If you prefer running from source without Docker, clone the repository and start the development server with pnpm.
git clone https://github.com/jsjfai/AgentDNS-Node.git
cd AgentDNS-Node
pnpm install
pnpm devAccess the management dashboard
Open http://localhost:3000 in your browser. Log in with the default credentials (admin / admin123) to view registered servers, manage groups, and monitor tool routing.
Configure your MCP client
Point your MCP client at the AgentDNS Node unified endpoint. All tools from all registered servers will be available through a single connection.
{
"mcpServers": {
"agentdns": {
"url": "http://localhost:3000/mcp"
}
}
}Use group or server-specific endpoints
For more granular access, connect clients to specific server or group endpoints instead of the unified /mcp route.
# All servers:
http://localhost:3000/mcp
# Specific server:
http://localhost:3000/mcp/fetch
# Server group:
http://localhost:3000/mcp/my-group
# Semantic smart routing:
http://localhost:3000/mcp/$smartAgentDNS Node Examples
Client configuration
Claude Desktop configuration connecting to the AgentDNS Node unified endpoint for access to all aggregated MCP servers.
{
"mcpServers": {
"agentdns": {
"url": "http://localhost:3000/mcp"
}
}
}Prompts to try
Example prompts that benefit from having multiple aggregated MCP tools available through a single AgentDNS Node endpoint.
- "Fetch the content of https://example.com using the fetch server."
- "Use the Playwright browser to take a screenshot of the Hacker News homepage."
- "List all the MCP tools currently available through this server."
- "Search Slack for messages about the project deadline using the Slack integration."
- "Use the smart routing endpoint to find the right tool for looking up map directions."Troubleshooting AgentDNS Node
Docker container starts but downstream MCP servers fail to connect
Check that the mcp_settings.json is correctly mounted and that the command/args for each server (npx, uvx) are available inside the Docker container. For servers requiring API keys, add an env block to each server entry in mcp_settings.json.
MCP client cannot reach http://localhost:3000/mcp
Verify Docker has published port 3000 with -p 3000:3000 and that no other service occupies the port. On macOS with Docker Desktop, ensure the port binding is active in the Docker Dashboard under the container's port settings.
Default admin credentials rejected on dashboard login
The default credentials are admin / admin123. If these have been changed, check the container's environment variables or configuration for the updated credentials. You can reset by restarting the container with a fresh mcp_settings.json.
Frequently Asked Questions about AgentDNS Node
What is AgentDNS Node?
AgentDNS Node is a Model Context Protocol (MCP) server that 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. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install AgentDNS Node?
Follow the installation instructions on the AgentDNS Node GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with AgentDNS Node?
AgentDNS Node works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is AgentDNS Node free to use?
Yes, AgentDNS Node is open source and available under the Apache-2.0 license. You can use it freely in both personal and commercial projects.
AgentDNS Node Alternatives — Similar Cloud Services Servers
Looking for alternatives to AgentDNS Node? Here are other popular cloud services servers you can use with Claude, Cursor, and VS Code.
Open WebUI
★ 138.2kUser-friendly AI Interface (Supports Ollama, OpenAI API, ...)
Anything LLM
★ 60.4kThe all-in-one AI productivity accelerator. On device and privacy first with no annoying setup or configuration.
LocalAI
★ 46.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
Nacos
★ 33.0kan easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.
Xiaozhi ESP32
★ 26.7k本项目为xiaozhi-esp32提供后端服务，帮助您快速搭建ESP32设备控制服务器。Backend service for xiaozhi-esp32, helps you quickly build an ESP32 device control server.
Gateway
★ 11.8kA blazing fast AI Gateway with integrated guardrails. Route to 1,600+ LLMs, 50+ AI Guardrails with 1 fast & friendly API.
Browse More Cloud Services MCP Servers
Explore all cloud services servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up AgentDNS Node in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use AgentDNS Node?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.