A
licenseNot graded
qualityB
maintenanceSelf-hosted workspace MCP gateway that registers MCP servers, stores secrets encrypted, mints agent keys, and shares a unified tool library across multiple AI harnesses.
1
Apache 2.0
Why this server?
Self-hosted workspace MCP gateway that registers MCP servers, stores secrets encrypted, and shares a unified tool library across AI harnesses — directly matching the guide's workflow of adding servers to a gateway with encrypted credentials and a single tool list.
Why this server?
Paid remote MCP endpoint for a gateway registry with team tool listing and tool-call routing, matching the 'tool list comes back empty / endpoint returns tools' troubleshooting described in the guide.
FlicenseNot gradedqualityDmaintenanceA paid remote MCP endpoint for the AI SDK MCP gateway registry, providing tools for team tool listing, tool call routing, permission state reading, and gateway log export with token-based access and usage receipts.-Why this server?
Aggregates all your MCP servers behind one Streamable HTTP endpoint with automatic registry discovery and OAuth2 authentication, mirroring the Glama gateway add-server-and-run pattern.
FlicenseNot gradedqualityCmaintenanceA self-hosted MCP gateway that aggregates all your MCP servers behind a single Streamable HTTP endpoint, with automatic registry discovery (19,000+ servers), on-demand Docker provisioning, multi-device support via SSH, OAuth2 PKCE authentication, and a workflow engine for saving and replaying multi-step tool sequences.-Why this server?
Gateway that federates multiple MCP servers and wraps REST APIs as MCP tools with an admin dashboard — the same class of unified gateway the user is configuring.
Why this server?
One local gateway for all your MCP servers with lazy discovery and keys kept in the OS keychain, comparable to the single-endpoint token model used by the Glama gateway.
Why this server?
Registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint with per-tool access control and usage logs, closely matching the guide's endpoint/tool-list behavior.
AISIX AI Gatewayofficial
AlicenseAqualityAmaintenanceSelf-hosted MCP gateway that registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint: per-tool access control by caller API key, guardrails over tool arguments and results, rate limits, and usage logs. The same Rust gateway also proxies LLM and A2A agent traffic.21191Apache 2.0Why this server?
Universal gateway that aggregates multiple MCP servers into a single interface with token optimization, the underlying pattern behind a registry-backed tool list.
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.32 npm17MITWhy this server?
Open-source gateway that aggregates MCP tools behind a unified endpoint with governance and observability, relevant to diagnosing an empty tool list on an aggregated gateway.
Bifrost MCP Gatewayofficial
AlicenseNot gradedqualityBmaintenanceOpen-source MCP and LLM gateway that aggregates MCP tools behind a unified endpoint with governance, observability, and explicit execution controls.8,832Apache 2.0Why this server?
Gateway for hosting your own tools and forwarding/curating tools from other MCP servers with policy hooks before execution, matching adding-registry-servers-to-a-gateway use.
AlicenseAqualityCmaintenanceA zero-dependency MCP gateway: host your own tools, forward and curate tools from other MCP servers, expose them leanly to cut agent token cost, and gate every call through your own policy hooks before it runs.434 npm38MIT