Calendly

Calendly

Calendly's hosted MCP lets agents inspect availability and routing context, manage event types, create bookings or scheduling links, cancel events, and maintain organization invitations.

Events & live engagementSystem of engagementExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityExtensible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Users, organizations and memberships, invitations, event types, availability schedules and busy times, scheduled events, invitees, no-shows, scheduling links, shares, routing forms and submissions.

02 · Data you can retrieve

Read event types and availability, scheduled events and invitees, no-show status, users and organization membership, invitations, routing forms and submissions, and meeting locations.

03 · Actions and write paths

Create or update event types and availability, book or cancel events, create single-use links and shares, manage no-show state, and create or revoke organization invitations.

04 · Authentication and permissions

Calendly uses OAuth 2.1 Authorization Code with PKCE and Dynamic Client Registration. Public clients receive no secret and are assigned scheduling read and write scopes.

05 · Monitoring, approval, and recovery

Treat booking, cancellation, no-show changes and organization invitations as externally consequential; expose invitee, host, event type, availability, time zone and notification context before action.

06 · Limits and caveats

Creating an invitee requires a paid Calendly plan; routing-form tools require Teams or higher. Availability and actions remain bounded by the authenticated user's organization.

First-party MCP tool catalog

34 named MCP tools · Calendly-hosted MCP server

The complete exact tool list published for Calendly's hosted server at mcp.calendly.com. Reviewed Jul 10, 2026. Calendly hosts the server and does not support self-hosting. Authentication requires OAuth 2.1 Authorization Code with PKCE and dynamic client registration; static client credentials and personal access tokens are unsupported. The server currently issues both scheduling read and write scopes. Booking requires a paid plan, and routing tools require Teams or higher. Booking, cancellation, availability changes, and organization invitations require explicit confirmation.

First-party exact listPublisher-described complete catalogCalendly hosted MCP
34 shown
Event types7
event_types-create_event_typewriteevent_types-update_event_typewriteevent_types-list_event_typesreadevent_types-get_event_typereadevent_types-list_event_type_available_timesreadevent_types-list_event_type_availability_schedulereadevent_types-update_event_type_availability_scheduleconsequential write
Meeting locations1
locations-list_user_meeting_locationsread
Events, invitees, and no-show status9
meetings-list_eventsreadmeetings-get_eventreadmeetings-cancel_eventconsequential writemeetings-create_inviteeconsequential writemeetings-list_event_inviteesreadmeetings-get_event_inviteereadmeetings-create_invitee_no_showwritemeetings-get_invitee_no_showreadmeetings-delete_invitee_no_showwrite
Scheduling links and shares2
scheduling_links-create_single_use_scheduling_linkwriteshares-create_sharewrite
User availability3
availability-list_user_availability_schedulesreadavailability-get_user_availability_schedulereadavailability-list_user_busy_timesread
Routing forms4
routing_forms-list_routing_formsreadrouting_forms-get_routing_formreadrouting_forms-list_routing_form_submissionsreadrouting_forms-get_routing_form_submissionread
Users and organizations8
users-get_current_userreadusers-get_userreadorganizations-get_organizationreadorganizations-list_organization_membershipsreadorganizations-get_organization_membershipreadorganizations-list_organization_invitationsreadorganizations-create_organization_invitationconsequential writeorganizations-revoke_organization_invitationconsequential write

Agent access

MCP support

Official MCP serverCalendly hosted scheduling MCPCurrent documented service

Support: Official MCP server

Read scope: Expose only authorized organization, scheduling, availability, invitee and routing reads while preserving user, event type, event, invitee, schedule, link, form and submission identifiers.

Write scope: 11 of 34 reviewed named tools have a write, draft, or mixed action label, including event_types-create_event_type, event_types-update_event_type, event_types-update_event_type_availability_schedule, meetings-cancel_event, meetings-create_invitee, and others. Read each catalog boundary before enabling them.

Authentication: The hosted server requires a DCR-capable public client using OAuth 2.1 Authorization Code and PKCE; Calendly issues a client ID but no client secret.

Approval boundary: Confirm host, invitee, event type, selected time and time zone, location, routing context and notifications before booking; confirm affected people and reason before cancellation or invitation changes.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Calendly ships them.

Single-platform patterns

  • Meeting routing and account-preparation workspace
  • Event operations cockpit
  • Attendee intelligence room
  • Webinar follow-up studio
Use in the brief builder →

Multi-platform compositions

  • Calendly + CRM or lifecycle system: event operations cockpit
  • Calendly + media-production platform + work-management or analytics system: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
MCP / agent-role validationRepresentative source
https://developer.calendly.com/calendly-mcp-server ↗

Calendly documents a hosted endpoint at https://mcp.calendly.com with OAuth 2.1 and read/write scheduling scopes.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

Developer portalSource inventory
https://developer.calendly.com/ ↗

First-party API documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://calendly.com/ ↗

Product overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

MCP tool catalogTargeted review
Calendly MCP: Supported Tools ↗

Named catalog evidence used on this profile.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party catalog review

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.