MCP
An open protocol for AI applications to interact with tools, resources and context providers through a standard interface. It is not a commerce or payment protocol; it is a capability-access layer for agents.
Why it matters
Agentic commerce combines model reasoning with deterministic transaction systems. Tool access, commerce state, payment authorization and user intent are not the same thing; each layer needs explicit boundaries and an authority model.
What does it look like in practice?
A travel agent may use MCP or provider APIs for capabilities, prepare checkout through a commerce contract such as UCP/ACP, and involve separate authorization/payment layers such as AP2, MPP or x402. These protocols do not solve the same problem.
Implementation questions
- Which capabilities can the agent access?
- What action and amount did the user explicitly authorize?
- Is transaction state held in a deterministic system independent of the model?
- Where are audit trails and human-approval checkpoints?
Common mistakes
- Treating an LLM decision as payment authorization
- Equating tool access with purchase authority
- Treating protocol names as one interchangeable agentic-commerce standard
Where does it appear in the travel stack?
MCP commonly appears across agentic layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
ACP, UCP, AP2, MPP, x402, MCP and A2A: Protocol Landscape for Travel
Compare ACP, UCP, AP2, MPP, x402, MCP and A2A by the architecture layer they solve in agentic travel commerce.
Explore →Canonical Offer, Order and Booking State Model
Design canonical Offer, Order and Booking lifecycle boundaries with an explicit booking state machine for travel integrations.
Explore →Google Places as Supplemental Hotel Context
Use Google Places as supplemental property/location context without turning Place IDs, ratings or reviews into hotel inventory source-of-truth.
Explore →NDC Offer/Order Lifecycle: Search to Servicing
Model NDC Offer/Order lifecycle across search, offer, revalidation, order creation, payment, ticketing, servicing and reconciliation states.
Explore →Payment + Booking Distributed Transaction
Model payment and supplier booking as a distributed transaction using authorization, capture, compensation, UNKNOWN outcomes and reconciliation.
Explore →Taxes & Fees Mismatch Troubleshooting
Diagnose hotel tax and fee differences through explicit base/total semantics, currency handling, occupancy and market context.
Explore →