AP2 vs MCP

Last verified 2026-05-31

Short answer: AP2 and MCP are not competitors. MCP, the Model Context Protocol (Anthropic, 25 November 2024), is the context layer that connects AI agents to tools and data; it carries no payments. AP2, the Agent Payments Protocol (Google, 16 September 2025), is a payment-agnostic framework to authorize agent-led payments, explicitly designed as an extension of MCP and the A2A protocol. In a typical stack, MCP provides connectivity and AP2 adds the payment-authorization layer on top.

Filter standards:
Criterion AP2MCP
Author / steward Google (60+ orgs)Anthropic, now Linux Foundation (AAIF)
Announced 16 Sep 202525 Nov 2024
Open-source status Open specification (public GitHub)Open source, MIT
What it is Agent payments frameworkAgent-to-tool/data context layer
Payment type Payment-agnostic (cards, stablecoins, bank transfers)None (not a payment protocol)
Transport Extension of A2A and MCPJSON-RPC 2.0 (stdio, HTTP)
Primary use Authorize agent-led payments across platformsConnect agents to tools and data
Notable adoption Mastercard, PayPal, Amex, Adyen, CoinbaseClaude, Cursor, Copilot, Gemini, VS Code, ChatGPT

Table last verified .

Frequently asked questions

Is AP2 a replacement for MCP?
No. AP2 is designed as an extension of MCP and the A2A protocol; they operate at different layers.
Does MCP handle payments?
No. MCP is the tool and context layer; payment protocols such as AP2, ACP and x402 connect to or extend it.
Who maintains AP2 and MCP?
AP2 is led by Google with 60+ organizations. MCP was created by Anthropic and donated to the Linux Foundation’s Agentic AI Foundation on 9 December 2025.