HOT RADAR
agentHEAT 11.9°

AI CURATED HOT STORY · 11/18/2026

Uber Builds MCP Gateway Spanning 800 Servers and 5000 Tools

1 reports archived1 independent sourcesupdated 11/18/2026, 14:33:01
Synthesis & Latest Updates
1 Sources Cross-Validated

Uber has built a unified MCP Gateway that governs over 800 MCP servers and 5,000 tools, separating a Registry control plane from a Proxy runtime so existing APIs can be exposed as MCP tools without modifying underlying services. The design is widely read as the API gateway pattern reborn for the agent era, while surfacing familiar distributed-systems problems such as discovery, authorization and observability at tool scale.

LATEST/Uber has built a unified MCP Gateway that governs over 800 MCP servers and 5,000 tools, separating a Registry control plane from a Proxy runtime so existing APIs can be exposed as MCP tools without modifying underlying services. The design is widely read as the API gateway pattern reborn for the agent era, while surfacing familiar distributed-systems problems such as discovery, authorization and observability at tool scale.

Hourly heat curve

2 fully observed hours
Fewer than 3 fully observed hours; trend not plotted yet.

Coverage timeline

Total 1 reports · Latest first
  1. InfoQ 中文T2·78 pts
    • Registry and Proxy are split: the control plane owns tool definitions, schemas and ownership, while the runtime translates MCP requests into HTTP, gRPC or TChannel calls
    • AutoCrawler scans Protobuf and Thrift IDL registries to auto-generate MCP schemas and uses LLMs to write tool descriptions, lowering onboarding cost
    • Response Projection lets agents request only needed fields instead of full payloads, easing context bloat
    • Practitioners note the design closely mirrors existing API and GraphQL gateways, and that security and governance concerns persist under MCP