AdCP, AAMP, MCP, ACP: which protocol does what — a guide for the DACH region

MCP, AdCP, AAMP, ARTF, ACP, UCP, A2A: which layer each protocol covers, who is behind it and what a publisher in the DACH region should do today. With a comparison table and checklist.

Anyone who has read trade coverage of "agentic advertising" over the past months has run into a string of acronyms that look confusingly alike: MCP, AdCP, AAMP, ARTF, ACP, UCP, A2A. Some of them sound almost identical and mean something entirely different. For decision makers at publishers, sales houses, agencies and advertisers in Germany, Austria and Switzerland, this is more than a vocabulary problem: mixing up the layers means investing in the wrong integration, or expecting a standard to do something it was never meant to do. This article sorts the protocols by one simple question: what does the protocol actually govern — transport, the buying of advertising, delivery, or the purchase of a product? Every statement about another organisation rests on the sources linked at the end, with the relevant date. The basic pattern: four layers Before looking at the individual protocols, it helps to picture four layers: Transport — how an AI model talks to a tool or to another agent in the first place. MCP and A2A belong here. Advertising vocabulary — the terms a buying agent and a selling agent must share in order to find inventory, negotiate an offer, book a campaign and pull reporting. AdCP belongs here. Real-time delivery — what happens inside the auction, in milliseconds. ARTF, as part of AAMP, belongs here. Checkout — how an agent buys and pays for a product on behalf of a person. ACP and UCP belong here. Most misunderstandings arise when a layer-4 protocol is taken for an advertising protocol, or when people assume a vocabulary standard replaces OpenRTB. MCP — the Model Context Protocol What it governs: MCP is an open standard for connecting AI applications such as Claude or ChatGPT to external systems — data sources, tools, workflows. The project site compares it to a USB-C port for AI applications. MCP says nothing about what a campaign is or what a CPM means. It defines how a model calls a tool and gets an answer back. Who governs it: MCP was developed by Anthropic and is one of the three founding projects of the Agentic AI Foundation, announced by the Linux Foundation on 9 December 2025 (alongside Block's goose and OpenAI's AGENTS.md). Status: The current specification carries the version 2026-07-28. The release candidate was locked on 21 May 2026, and the final version was announced for 28 July 2026. According to the official blog, …

Author

Nexbid

Published

2026-11-08

Topics

Agentic, Protocol Commerce, Ad Tech, Research