Connecting one agent to one tool with MCP takes minutes. Rolling MCP out across a large engineering organization is a different job. Hundreds of servers stood up independently, credentials copied into clients, no inventory, and nowhere to say no. The protocol scales. The deployment is what fails.
This session covers deploying MCP as governed infrastructure. A registry as the source of truth for which servers exist, who owns them, and what an agent may discover. A gateway as the single path between agents and tools, where identity, authorization, rate limiting, and policy are enforced instead of rebuilt per server. An AI gateway as the governed route to inference, holding credentials centrally and running guards on the way in and out.
Then the rollout: phased rather than switch-flipped, the control plane managed through GitOps, admission control so an unsanctioned server cannot land, runtime detection for the tool-execution surface, and workload identity so the gateway knows which agent is calling.
We close on what breaks at fleet scale: the violations a gateway catches cleanly, the ones that slip past, version skew, and the paths agents find around the control plane.