Gateway endpoints: many MCP servers, one URL
Blog post from Speakeasy
Speakeasy’s Gateway endpoints consolidate multiple Model Context Protocol (MCP) servers behind one URL, reducing client configuration overhead and preventing agents from loading every server’s full tool catalog into the context window before work begins. Instead, agents receive four gateway tools that let them list accessible servers, inspect a selected server’s tool descriptions, retrieve schemas only for tools they intend to use, and execute those tools through the member server’s existing path. This staged discovery model aims to reduce context use, simplify tool selection, and avoid validation failures caused by guessing tool arguments. Member servers retain their own authentication, permissions, audit logs, and execution behavior, meaning users connected to the same endpoint may see different available servers based on access rights. Gateway endpoints support Speakeasy-hosted, third-party, and privately tunneled MCP servers, require user sign-in by default, and can be created through the dashboard by naming an endpoint, adding and ordering members, and connecting clients to the resulting URL.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| MCP | 13 | 10,589 | 923 | 216 | +14% |
| Observability | 1 | 2,762 | 731 | 188 | -15% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.