Cal.com to MCP: Bookings, Free Slots and Call Transcripts in any AI Agent

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Cal.com, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Cal.com

Read a Cal.com scheduling account from Claude, ChatGPT or Copilot: event types, bookings with attendees, Cal Video recordings and transcripts, free time slots, availability schedules and connected calendars. Booking, rescheduling and cancelling are included but installed switched off.

Setup

Setting up takes about 2 minutes. You need a Cal.com account (any plan) to create a personal API key. The key acts as the user who created it.

1. Sign in to Cal.com and open Settings → Developer → API Keys (at app.cal.com, or at app.cal.eu if your account is in Cal.com's EU region).
2. Click New, give the key a name (for example AnythingMCP) and an expiry, and copy it. It starts with cal_live_ (or cal_test_ in test mode) and is shown only once.
3. Paste the key alone, without the word Bearer, into CALCOM_API_KEY.
4. Set CALCOM_API_HOST to https://api.cal.com if you sign in at app.cal.com, or to https://api.cal.eu if you sign in at app.cal.eu. Enter it without /v2, a path or a trailing slash: the connector adds /v2 itself. A key only works in its own region.
5. Install the connector and run calcom_get_me: it shows the user the key belongs to, with time zone and default schedule, and confirms that key and host belong together.

Whose data it sees: the key owner's event types, bookings and schedules, plus team bookings where that user is a host or admin. Everyone using the connector works with that one account, so use the key of the person (or team admin) whose meetings the AI should see.

What it reads: your event types (the bookable meeting templates) with length, locations, booking fields, buffers, minimum notice and booking link; bookings with status, times, meeting link, hosts, attendees with email and time zone, guests and the answers to booking questions; the Cal Video recordings and transcripts of a booking; the free slots of an event type; your availability schedules with weekly hours and date overrides; and the connected calendars (Google, Outlook, Apple, CalDAV), including the ones checked for conflicts and the one new bookings are written to.

Booking uid, not id: booking tools take the booking's uid, a string the AI gets from calcom_list_bookings, not the numeric id. The uid of a recurring booking returns every occurrence. Bookings can be filtered by status (upcoming, past, cancelled, unconfirmed), attendee, event type, team or dates, and come in pages.

Time zones: free slots come back in the time zone you think in, which the AI passes to calcom_get_available_slots, while booking start times go to Cal.com in UTC. The slots already take your calendars, buffers, minimum notice and limits into account.

Recordings and transcripts: only Cal Video meetings have them, and only the organizer, a team admin or an organization admin can read them. Meetings held on Zoom, Google Meet or Teams have none here. A transcript exists when someone clicked Transcribe during the call, and its download link works for one hour, so the AI fetches a fresh one when needed.

Switched off at install: calcom_create_booking, calcom_reschedule_booking and calcom_cancel_booking. They email real attendees and change real calendars: a new booking sends confirmations and invitations (paid event types may ask the attendee to pay), rescheduling cancels the old booking and creates a new one with a new uid, and a cancellation cannot be undone (on a recurring booking it cancels every occurrence). An administrator can turn them on one by one.

Asks before every change: once a write tool is on, the AI first checks the time with calcom_get_available_slots, then shows you the event type, the time in your time zone, the attendee and guests or the reason, and waits for your yes.

Limits: Cal.com allows about 120 requests a minute per API key. After a 429 the AI waits a minute before trying again.

Common errors: 401 Invalid API Key means the key is wrong, expired or deleted, or belongs to the other region. 403 means the key works but this user cannot see that booking, event type or team: use the key of the organizer or a team admin. 404 usually means a numeric id was used where a booking uid is needed. 400 names the field Cal.com did not accept, often a start time that is not a free slot.

The connector does not change event types, availability schedules or connected calendars, and it does not take or refund payments.

Prerequisites: CALCOM_API_HOST, CALCOM_API_KEY

Install the connector locally

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Open http://localhost:3000/connectors/store, pick Cal.com and paste in the env vars listed under Prerequisites.

Available tools

Example prompts

• "What meetings do I have tomorrow, and who are the attendees of each one?"
• "Find three free slots next week for my Intro call event type, in Berlin time, so I can offer them to a client."
• "Get the transcript of yesterday's call with Acme and list the action items we agreed on."
• "Which bookings were cancelled or rescheduled this month, and what reasons did people give?"
• "What are my working hours in my default schedule, and which calendars does Cal.com check for conflicts?"

Next steps

• Connect to Claude
• Connect to ChatGPT