F
licenseA
qualityD
maintenanceAggregates multiple MCP servers into a single gateway with unified top-level tools, reducing LLM context usage and enabling IDE compatibility by consolidating many tools into fewer interface functions.
4
18
-
MetaMCP
Officialby dataware-co
Related Servers
Alternatives to MetaMCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAggregates multiple MCP servers and custom Python tools behind a single endpoint, with intelligent context and tool discovery for AI agents.-
- AlicenseNot gradedqualityDmaintenanceAggregates multiple MCP servers into a single endpoint, enabling LLM clients to access tools, resources, and prompts from various backends through one connection.9 npmMIT
- AlicenseAqualityDmaintenanceAggregates tools from multiple MCP servers, acting as a proxy to provide unified access to various AI agents and tools.1018 npm3MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server that aggregates, manages, and proxies other MCP servers, enabling LLMs to discover, add, configure, enable/disable, and use tools from multiple servers dynamically.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to manage and proxy multiple MCP servers, dynamically extending capabilities by adding, configuring, enabling, disabling, and aggregating their tools through a unified interface.-
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: discovery of servers/tools, provisioning, forwarding tool calls, code execution, skill discovery, and skill readiness checking. No two tools have overlapping functionality.
Naming Consistency5/5
All tools follow the 'mcp_<verb>' pattern, with skill-specific tools adding 'skill_' for clarity. The naming is consistent and predictable.
Tool Count5/5
With 6 tools, the set is well-scoped for a meta-server. It covers the essential operations without being excessive or insufficient.
Completeness4/5
The tool surface covers discovery, provisioning, calling, execution, and skill support. Minor gaps exist (e.g., no explicit unprovisioning or server management), but core agent workflows are well-supported.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive