Topic
30 facts from 15 episodes, in date order. These are what speakers said on the shows, each linked to the moment it was said. They aren't independently verified.
2024
Pete Johnson said Anthropic published the Model Context Protocol on the Monday before Thanksgiving two years earlier, and competitors adopted it by March.
“MC published MCP on like Monday before Thanksgiving two years ago, and by March, all of their competitors had embraced it as a protocol”
2025
Pavel Veller says MCP-style connectivity did not exist about three months before the recording, when everyone wrote their own integrations.
“So it's this connective tissue that did not exist three months ago, three months ago. Everybody was writing their own”
Undated
Pavel Veller says DIAL is evolving to use MCP and runs at roughly twenty-some EPAM clients.
“Now it's evolving clearly towards what MCP can bring in, cause now you can connect a lot more things to it through MCP. So I think it's running at like 20 something clients by now.”
Undated
DIAL apps, which implement a streaming API that returns text plus interactive UI elements, predate MCP.
“We have dial apps, um, they predate MCP, but the idea is that you so dial itself has a contract, um, an API that you implement.”
Undated
Pavel Veller describes MCP as a way to connect existing software to large language models, comparing its role to HTTP for browsers.
“MCP allows to connect the existing software world to LLMs in a way.”
Undated
Pavel Veller says the IntelliJ IDE exposes itself as an MCP server.
“IntelliJ exposes itself as an MCP server to do things that ID IDE can do.”
Undated
Alexandra Samuel describes MCP as an emerging standard protocol that lets external resources be plugged into an AI.
“the development of a new protocol that's sort of emerging as a standard in the AI world that lets you plug external resources into an AI.”
Undated
Kleinerman said the Model Context Protocol (MCP) is gaining traction, and that agent-to-agent protocols are also emerging.
“There's also a number of interoperability protocols emerging. MCP is gaining a lot of traction.”
Undated
Sean Brown explained that MCP stands for Model Context Protocol and lets large language models and agents connect to external tools, data and systems.
“MCP stands for Model Context Protocol. It basically enables large language models and agents to connect to external tools and data and sources and systems.”
Undated
Rich Isenberg compared the Model Context Protocol to VHS against Betamax, saying it has become the dominant standard for agent access to tools.
“it very well might be the VHS to other people's Betamax, but it's clearly the 800 pound gorilla that's already won”
Undated
Rich Isenberg said an MCP gateway should be treated like API gateways and firewalls, as a key control for data access, observability and central kill switches.
“An MCP gateway should not be viewed any different. It is going to be a key control to be able to get as you start to scale to hundreds of agents”
Undated
Tim Crawford said agentic AI governance now has to account for technologies such as MCP, agent-to-agent communication and ephemeral agents.
“you start thinking about MCP, you start thinking about a two A, you start thinking about ephemeral agents.”
Undated
Herzig says MCP servers work easily for ten APIs, but with hundreds of APIs the model's context overflows, and SAP has far more.
“for ten API is not an issue, hundred, you get already, uh, context, blowed and all these these challenges”
Undated
Anthropic created the Model Context Protocol, which describes outside tools in simple natural language backed by a JSON schema so language models can use them.
“what Anthropic did was start to describe the outside world in relatively simplistic natural language terms. Uh, with a JSON schema backing it.”
Undated
McLuckie says an MCP platform has four pieces: a runtime, a registry, a gateway and a control plane.
“I think of as being four pieces that go into that. The 1st piece that goes into that is I need a runtime, I need somewhere where I can run this thing”
Undated
McLuckie says developers commonly run MCP servers by pulling a package from the internet with npx and running it locally, which risks running exploited code.
“In the case of, you know, most development technologies, people go npx run. They basically just pull a package down from the internet and it runs locally.”
Undated
McLuckie says the MCP specification was grounded in OAuth 2 workflows, where a user's OIDC token identifies them to an MCP server.
“MCP as a specification was really grounded in, like O, O, O, two workflows.”
Undated
McLuckie says pulling in three or four MCP servers can create around 150 tools and use 20-30k tokens on each interaction.
“you may have 150 tools. You may be burning 20 30k tokens every every interaction.”
Undated
Daniel Whitenack said some enterprise software vendors like NetSuite provide connectors into the AI world, often via MCP, on the assumption that their value lies in their data platform.
“Which is often MCP, right? So their value is, maybe they're assuming their value is in their data platform, how they organize data”
Undated
Swamy lists multi-model orchestration, autonomous agents, MCP servers and coding-tool skills as capabilities institutions must absorb.
“multi model orchestration with new models, agentic, fully agentic, and autonomous agents, M C P servers, skills that you use in Claude Code or Codex”
Undated
The host said the Model Context Protocol went from an Anthropic project to use by about 40 percent of software companies.
“It went from an anthropic project to something like 40% of software companies saying that they're already running it”
Undated
The host said Anthropic handed the Model Context Protocol to a vendor-neutral foundation by the end of the previous year.
“by the end of last year, Anthropic had handed it off entirely to a vendor neutral foundation, so no single company owns it.”
Undated
The Goose agent originated at Block, and the Model Context Protocol (MCP) originated at Anthropic.
“Goose came from Block and MCP came from Anthropic.”
Undated
Angie Jones describes the Model Context Protocol (MCP) as what agents use to connect to applications and tools.
“MCP is the model context protocol. This is what agents use to connect to applications and tools”
Undated
Jones points to the MCP Discord server as an example of competing companies collaborating on open-source work.
“all you gotta do is go in the MCP Discord server. It's a thing of beauty.”
Undated
MCP stands for model context protocol, which Wade Foster describes as a way for agents to talk to other agents and tools.
“now there's this new thing, uh, MCP, you called it stands for model context protocol, but effectively it's just a way for agents to talk to other agents.”
Undated
An MCP gateway registers MCP servers and controls which servers and tools an agent can access.
“you basically register MCP servers to this gateway and the gateway kind of controls access, so to speak, and regulates that.”
Undated
Nick Kuhn says user credentials should pass through the MCP gateway to servers like GitHub's rather than using one generic service account.
“I don't want it just to be like, well, here's our general generic service account for the entire organization.”
Undated
Routing agent traffic through an MCP gateway produces metrics on tool calls and events, according to Nick Kuhn.
“because it's all flowing through that gateway, we get metrics out of it. So we can see all the tool calls and all the all the events happening”
Undated
OpenAI says some Model Context Protocol (MCP) connectors from major data providers had error rates above 40% in its testing.
“Some, some of the MCPs that we connected, some big names, 40% plus error rate on their MCPs, right?”
Episodes