The Protocol Beneath the Product
How MCP became the connective tissue of the agent era
In April 1956, a trucking magnate named Malcolm McLean loaded fifty-eight metal boxes onto a converted tanker called the Ideal X and sailed it from Newark to Houston. What was inside didn’t matter. What mattered was the box: a standard size, standard fittings, a shape a crane in any port could grab without caring what it held. Within two decades the container had rerouted global trade, hollowed out old port cities, and turned the contents of world commerce into an afterthought. The interface won. The cargo became a detail.
That’s the argument Marc Benioff (co-founder and CEO of Salesforce) made in a recent conversation with the channel Tiff In Tech, just after Salesforce announced thirty new Slackbot capabilities in a single keynote. Benioff’s claim was big. He wants people to look back and see the moment Slack became the user interface not just to Salesforce, but to the whole AI ecosystem. Microsoft is making the same bet with Teams and Copilot. Google is making it with Gemini. Every platform company wants to be the one surface every model runs through. The received wisdom says the winner will be whoever builds the best assistant. That isn’t how this plays out.
What Anthropic actually shipped
The reason Slack might pull this off has nothing to do with Salesforce’s sales team. It has to do with a protocol most people outside engineering have never heard of.
In November 2024, Anthropic open-sourced the Model Context Protocol, or MCP. Before it, every time you wanted an AI model to talk to an outside tool, someone wrote a custom integration. Want Claude to read your Postgres database? Custom code. Also pull from Slack? Different code. Also Jira? A third integration. Every pairing of model and tool needed its own bespoke wiring, and the wiring multiplied like a tangle of proprietary chargers in a drawer.
MCP is the USB-C of that drawer. One standard interface between the model and the world: any model that speaks MCP can reach any tool that runs an MCP server. The adoption curve is the tell. By early 2026, MCP had crossed 97 million monthly SDK downloads, with more than 500 public servers and official kits in Python, TypeScript, C#, and Java. OpenAI adopted it across ChatGPT. Google and Microsoft support it. Anthropic handed the spec to the Linux Foundation. In roughly eighteen months a side project became the connective tissue of the entire agent stack.
Why Slack points both directions
Benioff’s ecosystem instinct shows up in the wiring. In February 2026, Slack launched its own MCP server, so any external client (Claude, Perplexity, OpenAI) could pull data from Slack and act inside it. A month later Slack became an MCP client too, meaning Slackbot can reach outward into any service that runs a server. The traffic runs both ways. Agents talk to Slack; Slack talks to agents. And because the protocol is open, Salesforce didn’t build a separate integration with each AI company. They built one MCP implementation, and every model that speaks the protocol plugs in.
Under that interface sits the part most people skip. Below Slack is Agentforce, the orchestration layer; below that, applications like Sales Cloud and Service Cloud; below those, a data layer Salesforce calls Data 360. Benioff describes it as federated but harmonized, which is a polite phrase for a genuinely hard problem. Your CRM stores a customer one way, your support tickets another, your email threads with no schema at all. For an agent to do useful work across all of it, something has to reconcile those schemas in real time. MCP lets the agent reach the data. Whether the answer is any good depends on the messy translation layer underneath, and that’s the engineering nobody puts on a slide.
The fight is one layer down
The number Benioff kept returning to was 60 percent: the amount by which Anthropic, running this whole stack, accelerated its own deals using Slackbot. That figure is why every platform company is making the same architectural wager. Microsoft has Copilot Studio behind Teams. Google has Gemini wired into Workspace. OpenAI launched Frontier as an orchestration layer with SaaS companies feeding it from underneath. Each is a different answer to one question: who owns the space between a human and an AI agent?
Benioff thinks the next turn goes past language entirely, into multi-sensory models pulling from video, audio, location, and sensors. MCP was built to be extended, and that extension is about to get stress-tested. The opportunity he points engineers toward is the unglamorous one. The spec is public, anyone can build a server, and whoever builds the best one for a particular domain owns a real edge while the giants fight over the surface.
He told a computer science junior at MIT, mid-doubt about her major, not to switch. The work is about to get more valuable, not less. The crane operators of this era won’t be the people with the smartest chatbot. They’ll be the people who built the box everything else fits inside. As Benioff put it, watching his own company get adopted: they’re using our stack, not just our Slack.