A Cal.com MCP for scheduling workflows that reach past the calendar
Connect one API key and availability lookups, slot holds, the booking lifecycle, event types, schedules, busy times, and webhooks become workflow steps. An AI agent can check real availability, hold a slot while it confirms details, and book the meeting, and every new booking can trigger a workflow that opens prep tasks and updates records instead of stopping at the calendar.
What the Cal.com MCP connector does
The Cal.com connector for Mattering Automations is 34 nodes on the Cal.com API v2: event types with full create, update, and delete, the booking lifecycle from listing and lookup through create, cancel, reschedule, confirm, decline, and no-show marking, availability schedules with date overrides, live slot lookups with temporary reservations, connected calendars and their busy times, the webhooks that turn bookings into automation triggers, and team reads. One API key authenticates all of it.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can look up what is actually free with Cal.com: Get Available Slots, place a short self-expiring hold with Cal.com: Reserve Slot while it confirms details, and only then run Cal.com: Create Booking, which is Cal.com automation with the guesswork removed.
Cal.com maintains its own official MCP server, calcom/cal-mcp on GitHub, with a hosted version at mcp.cal.com that authenticates over OAuth. It is a genuine option when all you want is an assistant talking to Cal.com alone. This connector is for the other half of the job, where scheduling is one step among many: on the Mattering canvas the same nodes sit next to every other connector and the platform itself, so a new booking can trigger a workflow that writes the attendee into a database, opens a prep task in Mattering Productivity, and drafts the follow-up, and a booking cancellation can unwind all of it. Use whichever fits, or both.
The safety modeling is stated plainly, because scheduling actions touch real people. Of the 34 nodes, 16 read and 18 act, and eight are classed destructive: creating, cancelling, rescheduling, confirming, or declining a booking sends real email to attendees and hosts that cannot be recalled, and deleting an event type, schedule, or webhook cannot be undone. Workflows gate those nodes behind conditions or approval steps rather than bare triggers. The rest are reversible writes, and the slot reservation pair is deliberately the safe one: a hold expires on its own and emails no one. One more thing the connector absorbs for you: Cal.com v2 versions its endpoint families independently through a cal-api-version header, and the connector pins the current version per family automatically, so you never manage version headers or debug a silently older response shape.
One connection, three surfaces
- Visual automations. Drag Cal.com nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Cal.com node, ready to drop on the canvas
34 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 16
Cal.com: Get Available Slots
Look up bookable time slots for an event type between two dates. Returns a map keyed by date, each date holding an array of slot start times (or start plus end when format is range); an empty object means nothing is free. This is a live availability lookup: re-query it rather than caching results.
Cal.com: Get Booking
Fetch one booking by its UID: status, times, hosts, attendees, location, and booking-field responses. For a recurring booking the UID of the whole series returns every recurrence.
Cal.com: Get Booking Attendees
List every attendee on a booking with name, email, timezone, language, phone number, and absence flag.
Cal.com: Get Busy Times
Read busy intervals from a connected calendar between two dates: each row has a start, an end, and a source. This is a live free-busy lookup: re-query it rather than caching results.
Cal.com: Get Default Schedule
Fetch the account's default availability schedule: the one event types use unless they pin another.
Cal.com: Get Event Type
Fetch one event type by ID: title, slug, duration, locations, booking fields, buffers, limits, schedule, and the public booking URL.
Cal.com: Get My Profile
Fetch the authenticated Cal.com account: id, username, email, timezone, week start, locale, and default schedule id. Works with any valid API key, so it doubles as the connection test.
Cal.com: Get Schedule
Fetch one availability schedule by ID: weekly hours per day, timezone, and date overrides.
Cal.com: Get Team
Fetch one team by ID: name, slug, branding, timezone, and whether it is an organization.
Cal.com: Get Webhook
Fetch one webhook by ID: subscriber URL, trigger events, active flag, secret, and payload template.
Cal.com: List Bookings
List the account's bookings with attendees, hosts, status, and times. Filter by one status (upcoming, past, cancelled, unconfirmed, recurring), attendee, event type, team, or date range. Cursor-paginated at this API version: pass data.pagination.nextCursor back as cursor until data.pagination.hasMore is false.
Cal.com: List Calendars
List the account's connected calendars (Google, Outlook, Apple, and others) with each connection's credentialId and the calendars inside it, plus the destination calendar new bookings are written to. Note the payload is an object: connections are at data.data.connectedCalendars[].
Cal.com: List Event Types
List event types with their titles, slugs, durations, locations, booking fields, and booking URLs. Leave the filters blank to list the authenticated account's event types; pass username to read another user's public event types.
Cal.com: List Schedules
List the authenticated account's availability schedules with their weekly hours, timezone, date overrides, and which one is the default.
Cal.com: List Teams
List the teams the authenticated account belongs to, with names, slugs, and branding. Team ids feed the bookings lister's team filter.
Cal.com: List Webhooks
List the account's webhooks with their subscriber URLs, trigger events, active flags, and payload template.
Action nodes 18
Cal.com: Cancel Booking
DESTRUCTIVE: cancel a booking. This SENDS REAL CANCELLATION EMAILS to the attendees and host, which cannot be recalled, so this node must never run in a blind test matrix. The booking's status becomes cancelled and its calendar events are removed.
Cal.com: Confirm Booking
DESTRUCTIVE: accept a booking that is pending host confirmation. This SENDS THE REAL CONFIRMATION EMAIL to the booker, which cannot be recalled, so this node must never run in a blind test matrix. The booking's status becomes accepted and calendar events are created.
Cal.com: Create Booking
DESTRUCTIVE: book a real meeting on the event owner's calendar. This SENDS REAL CONFIRMATION EMAILS to the attendee and the host, which cannot be recalled, so this node must never run in a blind test matrix; verify the attendee address upstream. The slot must be available (check with Cal.com: Get Available Slots). Cancelling afterwards emails everyone again.
Cal.com: Create Event Type
Create an event type on the authenticated account: title, slug, and duration are required; locations default to Cal Video when omitted. The response includes the new id and public booking URL. Reversible with Cal.com: Delete Event Type.
Cal.com: Create Schedule
Create an availability schedule. Without an availability array Cal.com applies its documented default of Monday to Friday, 09:00 to 17:00. Reversible with Cal.com: Delete Schedule.
Cal.com: Create Webhook
Subscribe a URL to the account's booking events: created, rescheduled, cancelled, no-show, and more. Cal.com POSTs the event payload to the URL as things happen; this is the standard way to trigger an automation from Cal.com. Reversible with Cal.com: Delete Webhook.
Cal.com: Decline Booking
DESTRUCTIVE: reject a booking that is pending host confirmation. This SENDS A REAL REJECTION EMAIL to the booker, which cannot be recalled, so this node must never run in a blind test matrix. The booking's status becomes rejected.
Cal.com: Delete Event Type
DESTRUCTIVE: delete an event type. Its booking page stops working immediately and the configuration cannot be restored; existing bookings made through it are not cancelled.
Cal.com: Delete Schedule
DESTRUCTIVE: delete an availability schedule. Its weekly hours and overrides cannot be restored, and event types pinned to it fall back to other availability.
Cal.com: Delete Slot Reservation
Release a temporary slot hold early, making the slot bookable again. Holds are ephemeral and expire on their own, so nothing permanent is lost; re-reserving recreates the hold.
Cal.com: Delete Webhook
DESTRUCTIVE: delete a webhook. Event deliveries to its URL stop immediately and the subscription (including its secret and template) cannot be restored; pause with Cal.com: Update Webhook (active false) if the stop should be temporary.
Cal.com: Mark Booking Absence
Record a no-show on a past booking: mark the host or specific attendees absent. Reversible by calling again with absent false. Note no-show marks can fire the account's webhooks and workflows.
Cal.com: Reschedule Booking
DESTRUCTIVE: move a booking to a new start time. This SENDS REAL RESCHEDULE EMAILS to the attendees and host, which cannot be recalled, so this node must never run in a blind test matrix. A new booking is created and the old one is marked rescheduled; the response is the NEW booking with its new uid.
Cal.com: Reserve Slot
Place a temporary hold on a slot so nobody else can book it while a flow completes. The hold expires on its own after reservationDuration minutes (default 5) and emails no one. Release early with Cal.com: Delete Slot Reservation using the returned reservationUid.
Cal.com: Update Event Type
Update an event type. Only fields you fill are sent, so existing settings are untouched; note bookingFields and locations REPLACE the whole existing array when sent. Reversible by writing the previous values back (read them first with Cal.com: Get Event Type).
Cal.com: Update My Profile
Update the authenticated account's profile: name, email, timezone, week start, time format, default schedule, locale, bio, or avatar. Only fields you fill are sent; reversible by writing the previous values back (read them first with Cal.com: Get My Profile).
Cal.com: Update Schedule
Update an availability schedule: rename it, change its timezone, replace its weekly hours or overrides, or make it the default. Only fields you fill are sent; reversible by writing the previous values back (read them first with Cal.com: Get Schedule).
Cal.com: Update Webhook
Update a webhook: change its URL, trigger events, payload template, or pause it with active false. Only fields you fill are sent; reversible by writing the previous values back (read them first with Cal.com: Get Webhook).
Connecting Cal.com takes one credential
Cal.com authenticates API requests with an API key sent as a Bearer header. Keys are created in the Cal.com web app on the settings page under the Security tab, in API Keys. Test-mode keys are prefixed cal_ and live-mode keys cal_live_. The key acts as the account it belongs to, so a key minted on the account that owns your event types is the one your workflows want.
Sign in to Cal.com, open Settings, go to the Security tab, and select API Keys.
Create a new API key and copy it. Store it where your automation secrets live; if a key leaks, revoke it from the same screen and mint a new one.
In Mattering Automations, open Connectors, click Add Connector, choose Cal.com, and create a credential with the API key.
Click Test Connection. Mattering calls Cal.com's authenticated profile endpoint: a success returns the account's id and username, and an error means the key is mistyped or revoked.
All 34 Cal.com nodes appear in the canvas palette. Run Cal.com: List Event Types first, because the event type id it returns is what the slot, booking, and reservation nodes ask for.
Common uses for the Cal.com MCP
Bookings that trigger real workflows
Cal.com: Create Webhook subscribes a workflow's inbound URL to booking events: created, rescheduled, cancelled, no-show, and more. From then on every new booking starts an automation instead of just landing on a calendar: fetch the full detail with Cal.com: Get Booking, write the attendee into a Mattering database, open a prep task, and send the internal heads-up. This is the standard way to make Cal.com the front door of a process rather than its end point.
An AI agent that books meetings without guessing
Cal.com: Get Available Slots is a live availability lookup, so the agent sees what is actually free right now. Cal.com: Reserve Slot then places a temporary hold, five minutes by default, that emails no one and expires on its own, which gives the agent time to confirm the attendee's details before Cal.com: Create Booking sends the real confirmation email. If the conversation ends without a booking, the hold simply lapses, or Cal.com: Delete Slot Reservation releases it early.
A host confirmation queue with a human in it
For event types that require host confirmation, Cal.com: List Bookings filtered to unconfirmed shows what is waiting, and a workflow can open an approval task in Mattering Productivity with the attendee's details attached. On approval, Cal.com: Confirm Booking sends the acceptance and creates the calendar events; on rejection, Cal.com: Decline Booking sends the rejection. Both send real email to the booker, which is exactly why the approval step sits in front of them.
No-show follow-up that runs itself
A scheduled workflow reads yesterday's meetings with Cal.com: List Bookings filtered to past, and where someone did not appear, Cal.com: Mark Booking Absence records the no-show against the host or specific attendees. The mark is reversible by calling the node again with absent false, and it can fire the account's own webhooks and workflows, so the follow-up sequence, a reschedule offer or an internal flag, hangs off the same event.
Availability that follows the business
Cal.com: Update Schedule changes weekly hours, timezone, or date overrides on an availability schedule, and Cal.com: Update Event Type adjusts durations, buffers, and booking limits, so seasonal hours, holiday blackouts, and team capacity changes become workflow steps instead of dashboard chores. Both nodes send only the fields you fill, and the read nodes beside them capture the previous values first, which makes every change reversible by writing those values back.
Free-busy reads that feed other systems
Cal.com: List Calendars shows every connected calendar on the account, Google, Outlook, Apple, and others, and Cal.com: Get Busy Times reads the busy intervals between two dates with a source on each row. A workflow can fold that into staffing dashboards, detect double-booked days, or check a person's real load before an agent proposes a meeting time. Both are live lookups: re-query rather than cache, because the answer changes whenever bookings do.
Example: A new booking lands: enrich the record, prep the host, gate the confirmation
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a webhook created with Cal.com: Create Webhook and subscribed to booking-created events fires the workflow's inbound URL the moment someone books.
Cal.com: Get Booking fetches the full booking by its uid: times, status, location, and the answers the booker gave on the booking form.
Cal.com: Get Booking Attendees lists everyone on the booking with name, email, and timezone.
The workflow writes the attendee into a Mattering database and opens a prep task in Mattering Productivity, assigned to the host with the booking details attached.
A condition checks the booking's status: if it is pending host confirmation, the workflow opens an approval task instead of proceeding.
On approval, Cal.com: Confirm Booking sends the acceptance email and creates the calendar events; the destructive-classed step runs only after a person said yes.
Cal.com MCP questions, answered
What Cal.com operations are supported?
34 nodes on the Cal.com API v2: 16 query nodes and 18 action nodes covering event types (list, get, create, update, delete), the booking lifecycle (list with filters and cursor pagination, get, create, cancel, reschedule, confirm, decline, no-show marking, attendees), availability schedules with date overrides, live slot lookups with temporary reserve and release, connected calendars and busy times, user-level webhooks (the automation trigger surface), profile read and update, and team reads. Deliberately not shipped: the organizations admin surface, the separate Platform OAuth-client product, interactive calendar connect flows, Cal Video recordings and transcripts, and routing forms.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Cal.com publishes an official MCP server. Why use this connector?
Cal.com does maintain an official MCP server, calcom/cal-mcp, with a hosted version at mcp.cal.com, and if all you want is an assistant talking to Cal.com alone, it is a genuine option. This connector earns its place when scheduling is one step in a larger workflow: the same canvas holds your other connectors and the Mattering platform itself, so a new booking can write into a database and open a prep task, a pending booking can wait behind a human approval step before the confirmation email goes out, and the email-sending booking actions carry destructive flags that workflows gate. Credentials live in one place with the rest of your connector secrets, and the same nodes serve visual automations and AI agents alike.
How does authentication work?
With a Cal.com API key sent as a Bearer header. Keys are created in the Cal.com web app on the settings page under the Security tab, in API Keys; test-mode keys are prefixed cal_ and live-mode keys cal_live_. Mattering stores the key encrypted and tests the connection against Cal.com's authenticated profile endpoint, which works with any valid key. Cal.com also offers OAuth client credentials through its separate Platform product; this connector uses the API key, which works for every regular account.
What are Cal.com's API rate limits?
Cal.com documents a default of 120 requests per minute for API-key authentication, and notes the limit can be increased by contacting them. Nodes report a rate-limit response on their output rather than silently retrying, so schedule wide sweeps apart and prefer one filtered List call over many Get calls.
Can an AI agent book a meeting without emailing the wrong person?
The guardrails are real rather than implied. Creating, cancelling, rescheduling, confirming, and declining bookings all send real email to attendees or hosts, so all five nodes are flagged destructive and belong behind conditions or approval steps, never on a bare trigger. The designed-for pattern gives the agent a safe middle step: Cal.com: Reserve Slot holds the time without emailing anyone while the agent verifies the attendee's address, and the hold expires on its own if the flow stops. Only the final, verified step sends mail.
What is the cal-api-version header, and do I have to manage it?
No, and that is one of the practical reasons to use the connector. Cal.com v2 versions its endpoint families independently, and each request is expected to carry a cal-api-version header naming the version it wants; a wrong or missing value does not fail, it silently returns an older response shape, which breaks downstream steps in ways that are hard to trace. The connector pins the current documented version for each family, event types, bookings, schedules, slots, and sends the right header on every call automatically.
Do I need a paid Cal.com plan?
Cal.com has a free individual tier, and API keys are created from the standard settings page, so the availability, booking, schedule, event type, and webhook nodes work against a free account. The two team nodes need the account to belong to a team. For anything plan-specific beyond that, check Cal.com's current pricing page rather than this one; plan boundaries change and this page makes no claims about them.
Put Cal.com to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Cal.com is a product of its respective owner; Mattering is an independent platform.