MCP — Model Context Protocol — has gone from a curiosity to enterprise infrastructure in less than a year. Last Friday, the Linux Foundation made it official, formalizing MCP under its new Agentic AI Foundation alongside production integrations from SUSE, AWS, and Fujitsu. Translation: it is now the standard your engineers are building on.

In this episode, Stephen Forte explains:

What MCP actually is — the USB-for-AI analogy, in plain language, no developer experience required
Why it became default — Anthropic, OpenAI, Google, Cursor, LangChain, LiteLLM, IBM LangFlow all support it
Why it cannot be deployed alone — the protocol is open by design, and an open protocol without a wrapper is a powerful electrical outlet with no cover
The AgentOps layer your team needs — gateway, identity, logging — same pattern as DevOps, new layer of the stack
Three direct questions to ask your CTO this quarter, and why naming a single owner matters more than convening a committee

Brex (the corporate-card and spend-management fintech) made the point cleanly this week with the open-source release of CrabTrap — a small proxy that watches every HTTP call an agent makes before it goes out. A 306-practitioner study published this month puts the urgency in numbers: 82% of organizations have agents in production or pilot, and the number-one cited challenge is reliability, not capability.

The protocol your engineers are excited about is genuinely useful and genuinely standard. The work of making it safe to operate is a separate budget line and a separate skill set — and it is the price of admission for running this stuff in a real company.

MCP Is The Plug. You Still Need The Outlet Cover.