OpenBooking is an open-source TypeScript SDK that makes any app or booking platform bookable by AI assistants. Implement one BookingProvider over your own system, and OpenBooking serves it over MCP, WebMCP and UCP with holds, consent, idempotency and cancellation rules built in.
npx create-openbooking my-salon
Six methods over your API or database. The engine does the agent safety, and the adapters do the protocols.
user_confirmedimport type { BookingProvider } from '@openbooking-sh/core'; import { createOpenBookingApp, listen } from '@openbooking-sh/server'; class MyPlatform implements BookingProvider { info = { name: 'My platform' }; async listVenues() {} // your businesses async searchAvailability(q) {} // free slots, price, policy async createHold(req) {} // reserve atomically async confirmHold(req) {} // hold → booking async getBooking(id) {} async cancelBooking(req) {} } const { app } = createOpenBookingApp({ provider: new MyPlatform(), baseUrl }); await listen(app); // /mcp, /ucp, booking page, WebMCP
MCP for chat assistants, WebMCP for AI browsers, UCP for agentic commerce. New protocols are adapters.
Consent, hold expiry, idempotency and cancellation fees are enforced by the engine, not by each integration.
provider-memory is a complete configured booking system with Postgres storage, Studio and a booking page.
No. Implement BookingProvider over your existing API or database. Your system stays the source of truth; OpenBooking translates for agents.
Every mutation is atomic, two overlapping holds never both succeed, and expired holds stop blocking inventory. The recipes include a full example.
Node 22 and 24, on any host. It’s a Hono app with web-standard fetch handlers, and deploys to Vercel out of the box.
Yes. We help booking platforms with their first integration for free. Get in touch from the developers page.