OpenBooking’s Cal.com connector (beta) puts an MCP server in front of a Cal.com account, hosted or self-hosted, through the Cal.com API v2. AI assistants search your event types’ availability, hold a slot with a Cal.com reservation, and book only after the customer confirms your cancellation terms.
npx create-openbooking my-salon
Install the connector, pass your Cal.com API key, and serve it with the OpenBooking server.
user_confirmed// npm install @openbooking-sh/provider-calcom @openbooking-sh/server import { CalcomBookingProvider } from '@openbooking-sh/provider-calcom'; import { createOpenBookingApp, listen } from '@openbooking-sh/server'; const provider = new CalcomBookingProvider({ apiKey: process.env.CAL_API_KEY, venue: { id: 'studio', name: 'Studio Nord', timezone: 'Europe/Oslo', currency: 'NOK' }, }); const { app } = createOpenBookingApp({ provider, baseUrl }); await listen(app); // Claude and ChatGPT book your Cal.com at /mcp
A hold becomes a Cal.com slot reservation for the hold’s lifetime, so nobody else can take the time meanwhile.
Cal.com doesn’t expose cancellation rules over its API, so you set them in the connector and agents show them before booking.
Confirmed bookings are re-checked with Cal.com when read, so a cancellation made in Cal.com shows up.
Yes. Point the connector at your own Cal.com instance; it uses the Cal.com API v2.
All of the account’s event types by default, or only the ones you list with eventTypeIds.
It’s in beta. Holds and booking mappings are kept in memory by default; use a durable store in production.