Tell your agent who. It finds when.
Cal.com started as a link you send. Now your agent books for you: it finds the person in your organization, reads both calendars, holds the first slot that works and books it when you say yes. Connect any MCP client to mcp.cal.com, free, on your agent's own tokens.
Why your agent books through Cal.com
The calendar is where your life gets decided. Here is what changes when an agent can read it and book into it, beat by beat.
From a link to your agent
Why not just a calendar?
Three people, or the whole team
It remembers who you saw
Anyone on Discover
Nobody double-books
Connect in a minute
One URL for any MCP client. It's free, and your agent runs on its own tokens.
- 1Add the serverPaste https://mcp.cal.com/mcp into Claude, ChatGPT, Cursor or any client that speaks MCP. Claude Code takes one command.
- 2Sign in with Cal.comOAuth, in the browser. Each person grants access to their own calendar, and there's no API key to copy.
- 3Ask for a meeting"Book 15 minutes with Rick Astley on Thursday morning." Your agent finds the time and books it.
Connect Cal.comFree. Your agent uses your own tokens.
Connect to the Cal.com MCP server at https://mcp.cal.com/mcp, sign in with OAuth, then book 15 minutes with Rick Astley on Thursday morning.Building your own assistant? Five ways in.
You bring the user, we bring the data: the calendars, availability, event types and bookings your assistant acts on. Start with the surface closest to how your agent already works.
- REST API v2 for every scheduling primitive.
- The Agent API, when one message should do the whole job.
- Atoms, React components for when a person confirms.
- A CLI with --json output for agents that run a shell.
Create a booking
Book on the user's behalf; the confirmation lands on their calendar.
1POST /v2/bookings2cal-api-version: 2024-08-1334{5 "eventTypeId": 123,6 "start": "2026-10-06T08:30:00Z",7 "attendee": {8 "name": "Ada",9 "email": "ada@example.com",10 "timeZone": "Europe/Berlin"11 },12 "metadata": { "source": "my-assistant" }13}
When the booking has to happen over the phone
Not every business has an API. Cal.ai voice agents make and take calls: they book appointments over the phone, send reminders and run follow-ups, so your assistant can close the loop with the real world.
+1 (415) 873-1159
Cal.ai Agent
Cal.ai Agent
Hi, Alex. This is Sally from Deel. How are you doing today?
I’m doing great Sally, thanks for asking. How are you?
Cal.ai Agent
I’m great! I’m just calling to see if you can still make the call tomorrow?
Phone booking
Your assistant asks for a dentist next week; Cal.ai calls the practice, agrees on a time against the user's real availability and creates the booking.
24 hours before event starts
Call attendee with Cal.ai Voice Agent
Reminders and follow-ups
Built on Cal.com Workflows, so the reminder the evening before and the no-show follow-up run on the booking without extra code.
- Trigger calls on bookings, cancellations and no-shows
- Combine with email and SMS automations
Cal.ai Agent
Hi, Alex. This is Sally from Deel. How are you doing today?
I’m doing great Sally, thanks for asking. How are you?
Cal.ai Agent
I’m great! I’m just calling to see if you can still make the call tomorrow?
Transcripts your agent can read
Every call is transcribed onto the booking, so your assistant knows what was agreed and can tell the user.
Your agent sees available slots. Not the calendar.
Calendar credentials and event data stay encrypted inside Cal.com. When your assistant asks what is free, it gets free times: not meeting titles, attendees or notes.
Encrypted calendar data
Per-user consent
Usage-based credits
Give your agent a calendar.
Connect it to mcp.cal.com in a minute. Free, on your agent's own tokens.
Connect your agentRead the docs

