Cal.com MCP integration for AI agents.
Connect AI agents to Cal.com through 47 structured actions, including get available slots info, add attendee, cancel booking, and confirm booking by uid. Rev…
- ACTION CONTRACTS
- 47
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Cal.com integration exposes
The Cal.com Agent App exposes 47 provider-backed actions for productivity and communication work. Its current contract lets an authorized agent compatibility action returning available slots for a user, team, or event type, add an attendee to a cal.com booking, and cancel a cal.com booking by uid, optionally providing a cancellation reason. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Cal.com account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cal.com capabilities.
Showing 12 of 47 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_available_slots_infoREADCompatibility action returning available slots for a user, team, or event type.
INPUTS: eventTypeId / eventTypeSlug / username / usernames / teamSlug
add_attendeeWRITEAdd an attendee to a Cal.com booking.
INPUTS: bookingUid / name / email / timeZone / phoneNumber
cancel_bookingHIGH IMPACTCancel a Cal.com booking by UID, optionally providing a cancellation reason.
INPUTS: bookingUid / seatUid / cancellationReason / cancelSubsequentBookings
confirm_booking_by_uidREVIEWConfirm a Cal.com booking by UID.
INPUTS: bookingUid
cancel_booking_via_uidHIGH IMPACTCompatibility alias for cancelling a Cal.com booking by UID.
INPUTS: bookingUid / seatUid / cancellationReason / cancelSubsequentBookings
create_bookingWRITECreate a Cal.com booking.
INPUTS: start / attendee / eventTypeId / eventTypeSlug / username
create_event_typeWRITECreate a Cal.com event type for the authenticated user.
INPUTS: title / slug / lengthInMinutes / description
create_scheduleWRITECreate a schedule for the authenticated Cal.com user.
INPUTS: name / timeZone / isDefault / availability / overrides
create_user_availability_scheduleWRITECompatibility alias for creating a Cal.com user availability schedule.
INPUTS: name / timeZone / isDefault / availability / overrides
decline_booking_with_reasonREVIEWDecline a Cal.com booking by UID with an optional reason.
INPUTS: bookingUid / reason
delete_event_typeHIGH IMPACTDelete a Cal.com event type by numeric ID.
INPUTS: eventTypeId
delete_event_type_by_idHIGH IMPACTCompatibility alias for deleting a Cal.com event type by ID.
INPUTS: eventTypeId
INPUT CONTRACTS
Know what the action needs before it runs.
get_available_slots_info
eventTypeIdOPTIONAL- The numeric Cal.com event type ID.
eventTypeSlugOPTIONAL- The Cal.com event type slug.
usernameOPTIONAL- The Cal.com username to scope the request to.
usernamesOPTIONAL- A comma-separated list of usernames to query availability for.
teamSlugOPTIONAL- The Cal.com team slug.
add_attendee
bookingUidREQUIRED- The unique Cal.com booking UID.
nameREQUIRED- The attendee's display name.
emailREQUIRED- The attendee's email address.
timeZoneREQUIRED- The IANA time zone used for this request.
phoneNumberOPTIONAL- The attendee's phone number.
cancel_booking
bookingUidREQUIRED- The unique Cal.com booking UID.
seatUidOPTIONAL- The seat UID to cancel for seat-based bookings.
cancellationReasonOPTIONAL- The reason shown for cancelling the booking.
cancelSubsequentBookingsOPTIONAL- Whether subsequent recurring bookings should also be cancelled.
confirm_booking_by_uid
bookingUidREQUIRED- The unique Cal.com booking UID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Available Slots Info
Compatibility action returning available slots for a user, team, or event type. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_available_slots_infoControl Add Attendee
Add an attendee to a Cal.com booking. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_attendeeVerify with Add Attendee
Add an attendee to a Cal.com booking. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_attendeeSAFETY BOUNDARY
Operate Cal.com with explicit limits
- Authorize Cal.com with OAuth 2.0 and grant only the provider access required by the selected actions.
- 19 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `cancel_booking`, `cancel_booking_via_uid`, and `delete_event_type` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `BOOKING_WRITE`, `EVENT_TYPE_WRITE`, `SCHEDULE_WRITE`, and `BOOKING_READ`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Cal.com task completed successfully.
CONNECTION MODEL
OAuth 2.0
Cal.com uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 20
- WRITE SIGNALS
- 13
- HIGH IMPACT
- 6
- REVIEW SIGNALS
- 8
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Cal.com.