The API Experience Podcast S2 E14 - The Deja Vu of MCP
Jan 16, 2026
Markus Müller, Global CTO for API management at Boomi, shares insights on the Model Context Protocol (MCP) and its relevance to AI. He discusses the evolution of APIs and highlights the need for governance amid API sprawl. Markus explains the origins of MCP and how it addresses developer friction. The conversation explores the balance between traditional API patterns and the unique demands of MCP. Markus also covers practical adoption methods for enterprises, emphasizing the importance of integrating deterministic workflows with AI-driven processes.
AI Snips
Chapters
Transcript
Episode notes
MCP Solved A Real AI Developer Pain
- MCP emerged because AI developers needed a single standard interface to connect agents to external systems.
- Adoption grew quickly because it solved real developer friction around agent integration.
Speed Created API Sprawl — AI Raises The Stakes
- API sprawl grew because speed was prioritized over governance during microservice adoption.
- AI and MCP increase governance urgency by exposing undocumented or legacy APIs to agents.
Link Governance To Agent Productivity
- Tie API governance directly to agent productivity to secure funding and attention.
- Show how managed APIs improve AI outcomes to convert governance from cost to business value.