OpenBooking serves one booking system to every kind of AI agent: MCP for chat assistants, WebMCP for AI browsers, the Universal Commerce Protocol (UCP, draft) for agentic commerce, and an A2A Agent Card for discovery. Every protocol shares the same engine, so holds, consent and no-double-booking rules apply everywhere.
npx create-openbooking my-salon
One server, mounted on one app. Agents pick the protocol they speak.
user_confirmed// one createOpenBookingApp(), every agent surface /mcp // Claude, ChatGPT, Cursor: Model Context Protocol /book + embed.js // booking page; WebMCP tools for AI browsers /ucp // Universal Commerce Protocol (draft booking extension) /.well-known/agent-card.json // A2A discovery (task endpoint next) /studio // dashboard for the business
Consent, holds, idempotency and cancellation terms live in one engine, not in each adapter.
The booking page carries schema.org data, so search engines and answer engines understand the business.
Apache-2.0, TypeScript, on npm. Run it yourself or use the hosted service.
MCP and WebMCP are supported. UCP follows the draft booking extension. A2A has an Agent Card for discovery; the task endpoint is next.
Agents need more than endpoints: holds that expire, explicit consent, idempotent retries and terms they can show. OpenBooking provides those on every protocol.
Yes. The one-line embed adds a Book button and registers WebMCP tools, so AI browsers can book on your own site.