Skip to main content
Calendly MCP logo
  • Category: model context protocol
  • Auth: DCR_OAUTH
  • Composio-managed OAuth available? No
  • Tools: 36
  • Triggers: 0
  • Slug: CALENDLY_MCP
  • Version: 20261030_00

Tools

Slug: CALENDLY_MCP_AVAILABILITY_GET_USER_AVAILABILITY_SCHEDULEUse: Fetch details for one named availability schedule. When: User asks about specific schedule rules or needs rules for a named schedule. Needs: Schedule URI from availability-list_user_availability_schedules. Do: Read rules array and timezone for display or to inform event-type updates. Avoid: Writing to this schedule—use event-type-level update for changes. Then: Report schedule details to user or use rules for availability queries.

Input Parameters

string
required
Availability schedule URI. not a browsable link — never show to users.

Output

object
required
The availability schedule set by the user.
Slug: CALENDLY_MCP_AVAILABILITY_LIST_USER_AVAILABILITY_SCHEDULESUse: List all named availability schedules for the connected user. When: User asks about availability schedules or you need to identify one by name. Needs: User URI from users-get_current_user. Do: Use returned uri to fetch schedule details or associate with an event type. Avoid: Confusing user availability schedules with event-type-level schedules. Then: Use schedule URI in availability-get_user_availability_schedule for details.

Input Parameters

string
required
A URI reference to a user

Output

array
required
Slug: CALENDLY_MCP_AVAILABILITY_LIST_USER_BUSY_TIMESUse: List a user’s busy time blocks within a date range. When: User asks a general yes/no “what’s my schedule”, “am I free/busy”, or “do I have any meetings” question with no named event type, invitee, or specific meeting. Default here even when the user says “meetings” — see meetings-list_events instead when the user wants to see or list which meetings they have. Needs: User URI from users-get_current_user and ISO 8601 start/end range. Do: Pass user URI and date range; use returned intervals to report conflicts. Avoid: Substituting for event_types-list_event_type_available_times (event-type bookable slots) or meetings-list_events (only booked Calendly meetings, not full calendar busy blocks) — they differ. Then: Use busy intervals to inform scheduling recommendations.

Input Parameters

string
required
The uri associated with the user
string
required
End time of the requested availability range. Date must be in the future of start_time.
string
required
Start time of the requested availability range. Date cannot be in the past.

Output

array
required
The set of internal and external scheduled calendar events matching the criteria
Slug: CALENDLY_MCP_EVENT_TYPES_CREATE_EVENT_TYPEUse: Create a new event type on the connected account. When: User explicitly asks to create a new event type. Needs: Host user URI from users-get_current_user. Do: Set name, duration, and host URI; omit optional fields unless user specified them. Avoid: Creating duplicates—call event_types-list_event_types first to check for existing types. Then: Confirm the new event type URI and share the scheduling URL.

Input Parameters

object
required
(required)

Output

object
required
A configuration for an Event Type
Slug: CALENDLY_MCP_EVENT_TYPES_GET_EVENT_TYPEUse: Fetch full details for one event type by URI. When: Before updating an event type or confirming its current configuration. Needs: Event type URI. Do: Use the returned fields as the baseline for any patch payload. Avoid: Constructing update payloads without reading current state first. Then: Proceed with event_types-update_event_type using the returned data as base.

Input Parameters

string
required
Event type URI. not a browsable link — never show to users.

Output

object
required
A configuration for an Event Type
Slug: CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPE_AVAILABILITY_SCHEDULEUse: Read the current availability schedule (rules) for an event type. When: Before calling event_types-update_event_type_availability_schedule. Needs: Event type URI. Do: Retain the full rules array verbatim—it is the required base for updates. Avoid: Calling the update endpoint without first reading the current rules. Then: Pass the rules to event_types-update_event_type_availability_schedule with only the needed edits.

Input Parameters

string
required
The URI associated with the event type

Output

array
required
object
required
Pagination
Slug: CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPE_AVAILABLE_TIMESUse: List bookable time slots for an event type within a date range. When: User wants slots, or to confirm availability before booking. Needs: Event type URI and start/end date range (ISO 8601). Do: Pass start_time verbatim to subsequent tool calls; do not rewrite UTC values. Avoid: Stale data, or trusting a prior local label—re-check UTC start_time if questioned. Then: Pass UTC start_time to meetings-create_invitee.

Input Parameters

string
required
End time of the requested availability range. Date must be in the future of start_time.
string
required
The uri associated with the event type
string
required
Start time of the requested availability range. Date cannot be in the past.

Output

array
required
The set of available times for the event type matching the criteria
Slug: CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPESUse: List all event types for the connected user or org. When: Start of any event-type task, or when selecting an event type by name. Needs: User URI from users-get_current_user. Do: Filter by current user URI unless user explicitly asks about a different host or org. Avoid: Assuming a cached list is current—call fresh each session. Then: Carry the selected uri into get, update, or availability tools.

Input Parameters

string
Order results by the specified field and direction. Accepts comma-separated list of {field}:{direction} values.Supported fields are: name, position, created_at, updated_at. Sort direction is specified as: asc, desc.
string
View available personal, team, and organization event types associated with the user’s URI.
string
The number of rows to return
string
Return only active event types if true, only inactive if false, or all event types if this parameter is omitted.
string
The token to pass to get the next or previous portion of the collection
string
View available personal, team, and organization event types associated with the organization’s URI.
string
Return only admin managed event types if true, exclude admin managed event types if false, or include all event types if this parameter is omitted.
string
Used in conjunction with user parameter, returns a filtered list of Event Types that use the given primary availability schedule.

Output

array
required
object
required
Pagination
Slug: CALENDLY_MCP_EVENT_TYPES_UPDATE_EVENT_TYPEUse: Update fields on an existing event type. When: User asks to change name, duration, description, or other settings. Needs: Event type URI from event_types-list_event_types or event_types-get_event_type. Do: Read current state first with event_types-get_event_type; patch only requested fields. Avoid: Sending fields not read from current state—partial writes may reset unset fields. Then: Confirm changes with event_types-get_event_type.

Input Parameters

string
required
Event type URI. not a browsable link — never show to users.
object
required
(required)

Output

object
required
A configuration for an Event Type
Slug: CALENDLY_MCP_EVENT_TYPES_UPDATE_EVENT_TYPE_AVAILABILITY_SCHEDULEUse: Overwrite the availability schedule for an event type. When: User requests schedule changes (hours, days, one-off date overrides) for an event type. Needs: Event type URI and current rules from event_types-list_event_type_availability_schedule. Do: Must copy existing rules verbatim, modify only requested entries, send full rules array with IANA timezone. wday rules need wday field; date rules need date field (YYYY-MM-DD); intervals is list of {from, to} in HH:MM 24h. Avoid: Constructing rules from scratch or sending a partial array—this endpoint overwrites all rules. Then: Re-read schedule with event_types-list_event_type_availability_schedule to confirm.

Input Parameters

string
required
Event Type uri in which to update the availability schedule
object
required
(required)

Output

object
required
A configuration for an Event Type Availability Schedule
Slug: CALENDLY_MCP_LIST_CALENDLY_SKILLSList or search available Calendly skill guides. Each skill gives domain-specific context, recommended tool usage, and best practices for working with Calendly MCP tools. Call this when the user’s goal has no obvious single tool (e.g. reschedule or move a meeting). Load a matching skill before using related workflow tools. Use keywords to search by name or description (any keyword may match), and include_header=true to include each skill’s description and related skills.

Input Parameters

string
boolean
Slug: CALENDLY_MCP_LOAD_CALENDLY_SKILLLoad a Calendly skill guide that provides domain-specific context, recommended queries, and best practices for working with Calendly tools. Required after listing when a skill matches; do not guess multi-step flows from tool names alone. Use list_calendly_skills to discover available skills, or load directly by name. Set header_only=true to preview a skill’s description and related skills without loading full content.

Input Parameters

string
required
boolean
Slug: CALENDLY_MCP_LOCATIONS_LIST_USER_MEETING_LOCATIONSUse: List allowed meeting location kinds for a user. When: Before creating bookings that need a location payload. Needs: User URI from users-get_current_user. Do: Read supported location kind values; choose one compatible with the event type. Avoid: Submitting a location kind not configured for the host or event type. Then: Use chosen kind in meetings-create_invitee location payload.

Input Parameters

string
required
The URI associated with the user

Output

array
required
The collection of user meeting locations
Slug: CALENDLY_MCP_MEETINGS_CANCEL_EVENTUse: Cancel a scheduled meeting on behalf of the connected host When: User confirms they want to cancel a specific meeting. Needs: Meeting URI from meetings-list_events or meetings-get_event. Do: Pass meeting URI and optional cancellation reason. Avoid: Canceling without confirmation; this notifies all invitees. For reschedule, surface reschedule_url instead. Then: Inform user the meeting is canceled and optionally list remaining meetings.

Input Parameters

string
required
Scheduled meeting URI. NOT the same as the invitee cancel_url (which is the public link you send to a human). not a browsable link — never show to users.
string
Optional cancellation reason.

Output

object
required
Provides data pertaining to the cancellation of the Event or the Invitee
Slug: CALENDLY_MCP_MEETINGS_CREATE_INVITEEUse: Book a meeting slot for an invitee on a Calendly event type. When: User provides invitee name, email, and a confirmed available time slot. Needs: Event type URI, start_time from event_types-list_event_type_available_times, invitee name and email. Include location if the event type has configured locations. Do: Set invitee name/email as the person being booked; host is the connected user from users-get_current_user. Never swap host and invitee fields. Avoid: Booking without confirming slot availability first, or omitting location when event type requires it. Then: Confirm booking with invitee details and meeting URI.

Input Parameters

object
required
(required)

Output

object
required
An individual who has been invited to meet with a Calendly member
Slug: CALENDLY_MCP_MEETINGS_CREATE_INVITEE_NO_SHOWUse: Mark an invitee as a no-show for a past meeting. When: User reports an invitee did not attend. Needs: Invitee URI from meetings-list_event_invitees. Do: Pass invitee URI; operation is idempotent. Avoid: Marking no-show before the meeting end time. Then: Confirm no-show is recorded and carry forward the no-show URI.

Input Parameters

object
required
(required)

Output

object
required
Provides data pertaining to the associated no show for the Invitee
Slug: CALENDLY_MCP_MEETINGS_DELETE_INVITEE_NO_SHOWUse: Remove a no-show mark from an invitee. When: User asks to undo a no-show marking. Needs: No-show URI from meetings-create_invitee_no_show. Do: Pass no-show URI; operation is idempotent. Avoid: Calling without confirming a no-show record exists. Then: Confirm no-show has been removed.

Input Parameters

string
required
Invitee no-show URI. not a browsable link — never show to users.
Slug: CALENDLY_MCP_MEETINGS_GET_EVENTUse: Fetch details for a single scheduled meeting. When: User asks about a specific meeting or before canceling/examining invitees. Needs: Meeting URI from meetings-list_events. Do: Use returned event_type, start_time, end_time, and location for display or next actions. Avoid: Calling this without a known meeting URI. list meetings first. Then: Use meeting URI in meetings-list_event_invitees or meetings-cancel_event.

Input Parameters

string
required
Scheduled meeting URI. not a browsable link — never show to users.

Output

object
required
Information about a scheduled meeting
Slug: CALENDLY_MCP_MEETINGS_GET_EVENT_INVITEEUse: Fetch details for a single meeting invitee. When: User asks about a specific attendee’s booking details. Needs: Meeting URI from meetings-list_events and Invitee URI from meetings-list_event_invitees. Do: Use returned fields for display or no-show status. Reschedule: surface reschedule_url. Avoid: Calling without known meeting and invitee URIs. Then: Use invitee URI in no-show tools if needed.

Input Parameters

string
required
Scheduled meeting URI. not a browsable link — never show to users.
string
required
Meeting invitee URI. not a browsable link — never show to users.

Output

object
required
An individual who has been invited to meet with a Calendly member
Slug: CALENDLY_MCP_MEETINGS_GET_INVITEE_NO_SHOWUse: Fetch the no-show record for a meeting invitee. When: User asks whether a no-show was recorded for an invitee. Needs: No-show URI from meetings-create_invitee_no_show. Do: Check returned record for no-show status and timestamp. Avoid: Calling if no no-show has been recorded—returns 404. Then: Report no-show status to user.

Input Parameters

string
required
Invitee no-show URI. not a browsable link — never show to users.

Output

object
required
Provides data pertaining to the associated no show for the Invitee
Slug: CALENDLY_MCP_MEETINGS_LIST_EVENT_INVITEESUse: List all invitees for a scheduled meeting. When: User asks who is attending a meeting or you need invitee URIs. Needs: Meeting URI from meetings-list_events. Do: Use returned invitee uri for no-show marking or detail lookups. Avoid: Calling without a meeting URI. list meetings first. Then: Use invitee URI in meetings-get_event_invitee or meetings-create_invitee_no_show. For reschedule, surface each invitee’s reschedule_url.

Input Parameters

string
required
Scheduled meeting URI. not a browsable link — never show to users.
string
Order results by the created_at field and direction specified: ascending (“asc”) or descending (“desc”)
string
The number of rows to return
string
Indicates if the results should be filtered by email address
string
Indicates if the invitee “canceled” or still “active”
string
The token to pass to get the next or previous portion of the collection

Output

array
required
The set of event invitees matching the criteria
object
required
Pagination
Slug: CALENDLY_MCP_MEETINGS_LIST_EVENTSUse: List scheduled meetings for user/org. When: Upcoming/past meetings or to find meetings by date. Needs: User/org URI via users-get_current_user. Do: Filter status (active/canceled), date range; carry uri. Avoid: Fetching unfiltered when the user has a specific date. Not for a yes/no busy/free check phrased as “meetings” (e.g. “do I have any meetings tomorrow”) — use availability-list_user_busy_times instead. Then: Enrich via meetings-list_event_invitees before listing/naming meetings, unless asked for only a count; then uri in meetings-get_event/meetings-cancel_event.

Input Parameters

string
Order results by the specified field and direction. Accepts comma-separated list of {field}:{direction} values. Supported fields are: start_time. Sort direction is specified as: asc, desc.
string
Return events that are scheduled with the user associated with this URI
string
The number of rows to return
string
Return events that are scheduled with the group associated with this URI
string
Whether the scheduled event is active or canceled
string
The token to pass to get the next or previous portion of the collection
string
Return events that are scheduled with the organization associated with this URI
string
Return events that are scheduled with the invitee associated with this email address
string
Include events with start times prior to this time (sample time format: “2020-01-02T03:04:05.678123Z”). This time should use the UTC timezone.
string
Include events with start times after this time (sample time format: “2020-01-02T03:04:05.678123Z”). This time should use the UTC timezone.

Output

array
required
The set of scheduled events matching the criteria
object
required
Pagination
Slug: CALENDLY_MCP_ORGANIZATIONS_CREATE_ORGANIZATION_INVITATIONUse: Invite a user to the organization by email. When: User asks to add a new member. Needs: Org URI and invitee email address. Do: Check organizations-list_organization_invitations first to avoid duplicate invites. Avoid: Calling without confirming no pending invite exists for this email. Then: Confirm invitation sent and optionally show pending invitations.

Input Parameters

string
required
Organization URI. not a browsable link — never show to users.
object
required
(required)

Output

object
required
Organization Invitation object
Slug: CALENDLY_MCP_ORGANIZATIONS_GET_ORGANIZATIONUse: Fetch details for the connected user’s organization. When: User asks about the org or you need the org URI for org-scoped list tools. Needs: Org URI from users-get_current_user (resource.current_organization). Do: Use returned uri for org-scoped event type or membership queries. Avoid: Calling without an org URI. Then: Use org URI in organizations-list_organization_memberships.

Input Parameters

string
required
Organization URI. not a browsable link — never show to users.

Output

object
required
Organization object
Slug: CALENDLY_MCP_ORGANIZATIONS_GET_ORGANIZATION_MEMBERSHIPUse: Fetch details for a single org membership. When: You need role or status for a specific member. Needs: Membership URI from organizations-list_organization_memberships. Do: Check role and status fields for permissions context. Avoid: Calling without a known membership URI. Then: Use membership data to confirm before invite or removal actions.

Input Parameters

string
required
Organization membership URI. not a browsable link — never show to users.

Output

object
required
OrganizationMembership
Slug: CALENDLY_MCP_ORGANIZATIONS_LIST_ORGANIZATION_INVITATIONSUse: List pending invitations for the organization. When: User asks to see pending invites or check if someone was already invited. Needs: Org URI from users-get_current_user. Do: Check returned list before sending a new invite to avoid duplicates. Avoid: Sending a new invitation without checking for existing pending ones. Then: Use invitation URI in organizations-revoke_organization_invitation if needed.

Input Parameters

string
required
Organization URI. not a browsable link — never show to users.
string
Order results by the field name and direction specified (ascending or descending). Returns multiple sets of results in a comma-separated list.
string
The number of rows to return
string
Indicates if the results should be filtered by email address
string
Indicates if the results should be filtered by status (“pending”, “accepted”, or “declined”)
string
The token to pass to get the next or previous portion of the collection

Output

array
required
object
required
Pagination
Slug: CALENDLY_MCP_ORGANIZATIONS_LIST_ORGANIZATION_MEMBERSHIPSUse: List all members of an organization. When: User asks who is in the org or you need to find a member’s user URI. Needs: Org URI from users-get_current_user. Do: Use returned user.uri for per-user event-type or availability queries. Avoid: Fetching the full list when you only need the connected user—use users-get_current_user instead. Then: Use member URI in user-scoped tools or organizations-get_organization_membership.

Input Parameters

string
Indicates if the results should be filtered by role
string
Indicates if the results should be filtered by user
string
The number of rows to return
string
Indicates if the results should be filtered by email address
string
The token to pass to get the next or previous portion of the collection
string
Indicates if the results should be filtered by organization

Output

array
required
object
required
Pagination
Slug: CALENDLY_MCP_ORGANIZATIONS_REVOKE_ORGANIZATION_INVITATIONUse: Revoke a pending organization invitation. When: User asks to cancel a pending invite. Needs: Organization URI from users-get_current_user and Invitation URI from organizations-list_organization_invitations. Do: Confirm with user before revoking; this cannot be undone. Avoid: Revoking without confirming the invite is still pending. Then: Confirm revocation and optionally refresh invitations list.

Input Parameters

string
required
Pending invitation URI. not a browsable link — never show to users.
string
required
Organization URI. not a browsable link — never show to users.
Slug: CALENDLY_MCP_ROUTING_FORMS_GET_ROUTING_FORMUse: Fetch details for a single routing form. When: User asks about a specific form or its questions. Needs: Routing form URI from routing_forms-list_routing_forms. Do: Use returned question IDs for submission filtering. Avoid: Calling without a known form URI. Then: Use form details to answer user questions or list submissions.

Input Parameters

string
required
Routing form URI. not a browsable link — never show to users.

Output

object
required
Information about a routing form.
Slug: CALENDLY_MCP_ROUTING_FORMS_GET_ROUTING_FORM_SUBMISSIONUse: Fetch details for a single routing form submission. When: User asks about a specific submission or response. Needs: Submission URI from routing_forms-list_routing_form_submissions. Do: Read questions_and_answers for the submitted values. Avoid: Calling without a known submission URI. Then: Report submission details to user.

Input Parameters

string
required
Routing form submission URI. not a browsable link — never show to users.

Output

object
required
Information about a Routing Form Submission.
Slug: CALENDLY_MCP_ROUTING_FORMS_LIST_ROUTING_FORMSUse: List routing forms for the org. When: User asks about routing forms or you need to find a form by name. Needs: Org URI from users-get_current_user. Do: Use returned uri to fetch form details. Avoid: Assuming form names without listing first. Then: Use form URI in routing_forms-get_routing_form.

Input Parameters

string
Order results by the specified field and direction. Accepts comma-separated list of {field}:{direction} values. Supported fields are: created_at. Sort direction is specified as: asc, desc.
string
The number of rows to return
string
The token to pass to get the next or previous portion of the collection
string
required
View organization routing forms associated with the organization’s URI.

Output

array
required
object
required
Pagination
Slug: CALENDLY_MCP_ROUTING_FORMS_LIST_ROUTING_FORM_SUBMISSIONSUse: List submissions for a routing form. When: User asks to see form responses or analyze routing data. Needs: Routing form URI from routing_forms-list_routing_forms. Do: Use pagination params for large result sets. Avoid: Fetching all submissions without date/count filters on high-volume forms. Then: Use submission URI in routing_forms-get_routing_form_submission.

Input Parameters

string
required
View routing form submissions associated with the routing form’s URI.
string
Order results by the specified field and direction. Accepts comma-separated list of {field}:{direction} values. Supported fields are: created_at. Sort direction is specified as: asc, desc.
string
The number of rows to return
string
The token to pass to get the next or previous portion of the collection

Output

array
required
object
required
Pagination
Slug: CALENDLY_MCP_SHARES_CREATE_SHAREUse: Create a single-use share link for a one-on-one event type with per-link overrides When: User wants a single-use link with any customization (duration, scheduling window, location, or availability). Needs: Event type URI from event_types-list_event_types. Do: Set only fields to override; omitted fields inherit from event type. Avoid: Group event types (one-on-one only). Then: Share the returned booking_url. To prefill the invitee’s name on the booking page, append a name query parameter with the URL-encoded value, e.g. {booking_url}?name=Pat+Tester.

Input Parameters

object
required
(required)

Output

object
required
Share
Slug: CALENDLY_MCP_USERS_GET_CURRENT_USERUse: Resolve the connected host account and canonical user URI. When: Start any scheduling, booking, event-type, or availability workflow. Needs: No inputs. Do: Call once and keep resource.uri, timezone, and scheduling_url for downstream calls. Avoid: Skipping this and guessing host identity. Then: Use resource.uri in list/get tools unless the user explicitly names another host.

Output

object
required
Information about the user.
Slug: CALENDLY_MCP_USERS_GET_USERUse: Fetch profile for a specific user by URI. When: User asks about another person’s account or you hold a user URI from org/membership data. Needs: User URI. Do: Pass the user URI from org/membership data; do not use this to look up the connected user. Avoid: Calling this without a known URI - use users-get_current_user for the connected user. Then: Use returned resource.uri and resource.timezone for event-type or availability lookups scoped to that user.

Input Parameters

string
required
User URI. not a browsable link — never show to users.

Output

object
required
Information about the user.