MCP (Model Context Protocol)

MCP, short for Model Context Protocol, is an emerging protocol for letting agents call external tools, data sources, and other agents in a structured, interoperable way. Marketleaf is bullish on MCP — not because it is the only such protocol, but because it has accumulated enough adoption across providers and platforms to be a credible interop layer rather than a single-vendor abstraction.

The practical effect of MCP adoption in a marketing-stack context is that the tool layer (CRM, CDP, analytics, content systems, email platforms, social schedulers) can be exposed to the agent layer through a common interface rather than through a proliferation of custom integrations. The work to expose a system once via MCP pays off across every agent that consumes it, instead of having to be rebuilt per agent. This compounds quickly when the workforce includes many specialist agents that each need access to overlapping subsets of the marketing-stack tool layer.

The most useful framing for buyers is that MCP support is a real evaluation criterion when assessing both tools (does the tool expose itself cleanly via MCP) and agentic platforms (does the platform consume MCP-exposed tools cleanly). Vendors that handle this layer well make the rest of the stack composable. Vendors that handle it badly produce a stitched-stack experience that is more painful than the older custom-integration approach was, because the agentic layer above is more demanding of the tool layer below than the older campaign-orchestration tools ever were.