Designing Mcp Gateway

Uber has published the design of the gateway it uses to make internal services available to agents through the Model Context Protocol. Rather than asking every team to rewrite a service as an MCP server, the gateway acts as a proxy that translates MCP calls into the protocols Uber already runs, including HTTP, gRPC and TChannel. A registry and a discovery layer that crawls existing APIs help find what can be exposed, and a control plane handles authoring and hosting. Security and observability are handled once, at the gateway, instead of per service. Uber reports more than 800 MCP servers and over 5,000 tools running on it. For organizations with large service estates, the post is a concrete reference architecture: one translation layer with shared discovery and policy, instead of hundreds of separately maintained MCP wrappers.