Calendly

This connector uses the Calendly API v2.

Setup:

1. Sign in to https://calendly.com → Integrations & Apps → API & webhooks → Personal Access Tokens → Create new token.
2. Give it a name (e.g. 'AnythingMCP'). The token is shown ONCE, copy it immediately. Personal Access Tokens never expire and inherit your user permissions.
3. Set CALENDLY_PERSONAL_ACCESS_TOKEN to the token.

Authentication: Bearer token. Calendly also supports OAuth2 for multi-user apps but Personal Access Tokens are the right fit for single-account agent use.

The URI model: every Calendly resource is identified by a full HTTPS URI, NOT a bare ID. For instance a user is https://api.calendly.com/users/AAAAAAAAAAAAAAAA, not just AAAAAAAAAAAAAAAA. List endpoints expect these URIs as query parameters (e.g. ?user=https%3A%2F%2Fapi.calendly.com%2Fusers%2F...). Always grab the URI from a prior tool's response — the easiest starting point is calendly_get_current_user, whose resource.uri is your user URI. Same model for organizations, event types, and scheduled events.

Pagination: cursor-based. Each list response has pagination.next_page_token. Pass it as page_token on the next call.

Cancelling a meeting: counter-intuitively uses POST, not DELETE (POST /scheduled_events/{uuid}/cancellation). Body accepts a reason text that's shown to the invitee. The adapter exposes this as calendly_cancel_scheduled_event.

Availability windows: calendly_list_event_type_available_times returns the open slots between start_time and end_time for an event type. The span MUST be ≤ 7 days; longer ranges return 400. For multi-week scans, call it once per week.

Single-use scheduling links: calendly_create_single_use_scheduling_link produces a URL that can be booked ONCE (max_event_count=1) for a specific event type. Useful when an agent wants to invite one specific person without exposing your generic Calendly profile.

Read-mostly: Calendly's API is heavier on reads than writes. There's no 'create new event type' or 'create new booking on behalf of someone' endpoint — bookings come from invitees clicking a scheduling link.

Rate limits: 100k requests / day per account, with a burst window. On 429, back off.

Webhooks out of scope (/webhook_subscriptions is supported via API but receiving the payloads needs a hosted endpoint).

Plan gating: certain endpoints (organizations, memberships, routing forms) require Teams or Enterprise plans. Personal accounts get 403 — error message identifies the plan required.