Universal MCP server aggregator for combining multiple MCP servers into a single endpoint
MCP Aggregator MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Aggregator directly instead of describing what you should do. Universal MCP server aggregator for combining multiple MCP servers into a single endpoint.
A universal aggregator for combining multiple MCP (Model Context Protocol) servers into a single endpoint for AI assistants to access various tools and capabilities.
The server ships on npm as @mcp/aggregator, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by dwillitzer; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Aggregator's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"aggregator": {
"command": "mcp-aggregator",
"args": ["start", "--stdio"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.