What's the difference between MCP and OpenAI's Agentic Commerce Protocol (ACP) for booking appointments through AI?
TL;DR: MCP (Model Context Protocol) is the open standard that lets an AI assistant call a business's actual tools — like checking calendar availability and creating a booking — inside the conversation. ACP (Agentic Commerce Protocol), which OpenAI launched with Stripe in February 2026, is built for product checkout at retailers, not appointment scheduling. BookRails' booking rail runs on MCP because that's the protocol designed for actions like "hold this slot" and "confirm this appointment," not "complete this purchase."
The claim
MCP and ACP solve different problems and get confused because both let an AI assistant "do something" instead of just answering a question. Local service businesses need MCP-style booking, not ACP-style checkout.
The evidence
- OpenAI's own announcement, "Buy it in ChatGPT: Instant Checkout and the Agentic Commerce Protocol," frames ACP around retail purchases — the launch on February 16, 2026 enabled Instant Checkout for US merchants selling physical products, co-developed with Stripe.
- Trade coverage reports OpenAI scaled back the initial Instant Checkout rollout after roughly a dozen merchants went live, shifting toward a more merchant-controlled checkout model rather than a fully universal one — signaling ACP is still maturing for retail, let alone for services.
- MCP, by contrast, was built as a general, open standard for connecting an AI assistant to external tools and data — calendars, CRMs, booking systems — which is exactly the shape of an appointment-booking action rather than a product purchase.
- A booking is not a checkout: it requires checking live calendar availability, matching a specific staff member or service duration, and syncing to a real calendar (Google Calendar) — capabilities ACP's commerce-focused schema isn't built around today.
Comparison table
| MCP (Model Context Protocol) | ACP (Agentic Commerce Protocol) | |
|---|---|---|
| Built for | Connecting AI to external tools and data (calendars, CRMs, booking systems) | Product checkout inside chat |
| Introduced by | Originated at Anthropic as an open standard, broadly adopted since | OpenAI plus Stripe, launched February 2026 |
| Typical action | "Check availability, book 2pm Tuesday" | "Buy this product, pay now" |
| What BookRails uses | MCP — for real-time appointment booking synced to Google Calendar | Not applicable to appointment booking today |
| Maturity for local services | Purpose-fit, in active use | Retail-focused, still being scaled back and reworked |
Step-by-step: what a local business should actually do
- Don't wait on ACP for appointment booking — it's not designed for scheduling, and its retail rollout is still being reworked.
- Get your booking system MCP-ready: real-time calendar sync (Google Calendar), a defined service and duration list, and staff-assignment logic.
- Make sure whatever books the appointment also writes the booking source back to your CRM or ledger — you want to know a booking came from an AI chat, not just "online."
- If you sell physical retail products alongside services (a salon selling product lines, for example), treat that as a separate consideration from your appointment-booking flow — different protocols, different maturity levels.
- Test the actual flow: ask an MCP-connected assistant to book a real slot and confirm it lands correctly on your calendar before promoting the feature to customers.
- Revisit this quarterly — both protocols are evolving fast in 2026, and today's gap between them may narrow.
FAQ
Can ChatGPT book a haircut appointment using ACP today? No — ACP's public rollout has been retail checkout focused, not appointment scheduling. Booking flows need an MCP-style connection to a calendar and booking system instead.
Is MCP an OpenAI product or an Anthropic product? MCP originated at Anthropic as an open protocol; it has since been adopted broadly across the AI ecosystem, including by tools connecting to ChatGPT.
Does my business need to support both protocols? Not for booking — MCP is the relevant one. ACP only matters if you're selling physical products for direct in-chat checkout, a different use case entirely.
Why did OpenAI scale back Instant Checkout? Reporting attributes it to a shift toward merchant-controlled checkout after an initial cohort of roughly a dozen merchants launched — OpenAI is still refining the retail experience.
How does BookRails handle the actual calendar sync? BookRails' Booking rail uses MCP to let an AI assistant check real-time availability and create the appointment directly on your connected Google Calendar, in the same conversation the customer is already having.
By Pinal Dave Last updated: 2026-07-31