On April 16th, Salesforce opened their entire stack to the Model Context Protocol. This is a big deal for RevOps teams, and it’s worth understanding why.

What Happened

Salesforce now supports MCP across its full product suite. This means AI agents and tools that speak MCP can interact directly with Salesforce — reading data, triggering automations, and operating across Sales Cloud, Service Cloud, and the platform layer without custom API integrations for each use case.

Why This Matters for RevOps

If you’ve spent time building Salesforce integrations, you know the pain: custom API calls, middleware, authentication flows, and maintenance every time Salesforce updates something. MCP changes the interaction model fundamentally.

Instead of building point-to-point integrations, your AI tools can now have a standardized conversation with Salesforce. Need to pull pipeline data into a forecast model? Query account health scores for a QBR? Update opportunity stages based on signals from another system? MCP provides a common protocol for all of it.

This matters most for teams that are already using AI-assisted workflows. If you’re running an AI agent that helps with deal inspection or forecast preparation, it can now talk to Salesforce the same way it talks to any other MCP-enabled tool — no Salesforce-specific integration code required.

What to Watch

Outreach opened up to MCP back in February, and now Salesforce has followed. The pattern is clear: RevOps tools are converging on MCP as the standard protocol for AI interaction. The teams that understand this shift early will have a significant advantage in how they architect their tech stacks going forward.

This ties directly into the Tech Stack pillar — understanding how your tools communicate isn’t just an IT concern anymore. It’s a RevOps strategy decision.