Uber standardizes agents with internal MCP Gateway
Uber’s central MCP Gateway proxies internal Protobuf, Thrift, and HTTP endpoints as standardized MCP servers, creating a "USB-C interface" for AI agents to access corporate services. The system centralizes security and telemetry, allowing autonomous agents to safely perform complex migrations, upgrades, and bug fixes across the company's vast monorepo.
Uber’s shift to a configuration-driven MCP architecture demonstrates how the Model Context Protocol is graduating from a developer tool to a foundational layer for enterprise agentic infrastructure.
- –Centralized gateway handles authentication and logging, mitigating the primary security risks of granting autonomous agents access to sensitive data.
- –Abstracting legacy services into MCP servers enables teams to "agent-ize" their internal tools via simple configuration changes rather than custom integration code.
- –The system powers the "Minion" platform, which runs parallel background agents to handle "boring" engineering toil at scale.
- –Adoption has reached a critical mass: 84% of Uber developers now use agentic workflows, with over 65% of IDE code being AI-generated as of March 2026.
- –A built-in Registry and Sandbox lower the barrier to entry, making agent capabilities discoverable and testable for every engineering team.
DISCOVERED
73d ago
2026-03-17
PUBLISHED
73d ago
2026-03-17
RELEVANCE
AUTHOR
Ben Davis
