MCP

Infrastructure, Not an Advertising Protocol

MCP, the Model Context Protocol, is not specific to advertising. It's a general-purpose standard, developed by Anthropic, that defines how an AI model connects to external tools and data sources — any model, any tool, regardless of who built either one.

It shows up throughout this protocol landscape not because advertising needed its own version of it, but because ARTF, AAMP, and AdCP all rely on it for the same underlying job: letting an agent call a tool without a custom integration for every pairing.

What MCP Actually Standardizes

Before MCP, connecting a model to a tool meant writing a bespoke integration — this model, that data source, this specific way of formatting the request. Every new pairing meant new code. MCP replaces that with a shared interface: a tool exposes itself in a standard way, and any MCP-compliant model can discover and use it, without either side needing to know the other's internals in advance.

That's the whole scope. MCP doesn't define what a "good" tool call looks like for advertising specifically, doesn't know what a bid is, and has no concept of a publisher or a buyer agent. It only knows: here is a tool, here is how to call it, here is what comes back.

Where MCP Shows Up in This Stack

MCP appears as a dependency inside protocols built for advertising, not as an advertising protocol itself:

ARTF includes an MCP server interface so natural-language agents can invoke low-level tools — like requesting a specific mutation to a live bid request — without a custom connector for every host platform.

AdCP is built on top of MCP for tool execution, alongside A2A for the agent-to-agent messaging layer. A buyer agent's use of MCP is what lets it reach AdCP-formatted tools without a bespoke integration for every supply intelligence provider it works with.

AAMP incorporates MCP interfaces directly into its specification, so agents operating inside AAMP's governance and workflow layer can safely interact with lower-level delivery systems using the same standard access pattern.

Why This Matters

None of the advertising-specific protocols in this landscape had to solve "how does a model call a tool" from scratch. MCP already solved that, generally, once. What ARTF, AAMP, and AdCP each add is domain-specific meaning on top: what tools exist, what they do, and what the advertising-specific rules are for using them.

Understanding MCP isn't about learning a fourth advertising standard. It's about recognizing that the other three didn't have to reinvent tool access — they just had to decide what tools were worth exposing.