MCP Gateway
Related Servers
Alternatives to MCP Gateway
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA unified gateway and web dashboard that aggregates multiple MCP servers into a single Streamable HTTP endpoint. It supports stdio, SSE, and HTTP protocols, featuring optimized tool exposure modes to reduce token consumption for AI clients.5MIT
- AlicenseNot gradedqualityFmaintenanceA universal gateway that aggregates multiple MCP servers into a single interface while providing advanced token optimization, result filtering, and automated summarization. It enables efficient management of large tool catalogs and reduces context usage by up to 95% for major AI clients.39 npm17MIT

Perforce Agentic Gatewayofficial
FlicenseNot gradedqualityAmaintenanceA local MCP gateway that allows AI clients to manage and interact with multiple MCP servers through a single connection, providing token-efficient access to tools and resources.13-- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server gateway that reduces context bloat through progressive tool discovery and Lua-based tool chaining, while centralizing multiple MCP servers into a single endpoint.15MIT
- AlicenseAqualityCmaintenanceA single MCP server gateway that reduces context bloat by providing progressive tool discovery and invocation, dynamically provisioning downstream servers on demand.2680 PyPI23MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to connect through a single multiplexed SSE/HTTP endpoint to multiple local and remote MCP servers, with token authentication, per-tool approval policies, tool namespacing, and live telemetry.39 npm1MIT
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, gateway_list_tools lists tools, gateway_search_tools searches them, gateway_invoke invokes them, and gateway_get_stats provides usage statistics. Tools like gateway_kill_server and gateway_revive_server are complementary but distinct in their actions (disable vs. re-enable).
All tools follow a consistent 'gateway_verb_noun' pattern, such as gateway_list_servers, gateway_set_profile, and gateway_reload_config. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 15 tools, the count is well-scoped for a gateway server that manages backend servers, routing, and monitoring. Each tool serves a specific function in this domain, such as listing, searching, invoking, and controlling servers, without being excessive or insufficient.
The tool set provides complete coverage for gateway operations, including server management (list, kill, revive), tool discovery (list, search), invocation, routing control (profiles), monitoring (stats, cost reports), and configuration (reload). There are no obvious gaps, enabling agents to handle all typical gateway workflows.