Calendly
by Calendly
Book, cancel and reschedule meetings, edit event types and adjust availability from your AI assistant. 36 tools, OAuth sign-in, and separate read and write scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Calendly via MCP
https://mcp.calendly.com/Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Calendly Tools & Capabilities (36)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- It can cancel real meetings, and the invitee is emailed.
meetings-cancel_eventis in both Anthropic's listing and Calendly's own table, mapped to the cancellation endpoint. Cancelling is not a local state change — the person who booked receives a Calendly cancellation email. No server-side confirmation step is documented, so whether you are asked first is entirely your MCP client's tool-approval setting. - It cannot reschedule. Calendly's FAQ states no API endpoint supports rescheduling an event or invitee. Anything an assistant calls "rescheduling" is either handing you a
reschedule_urlfor the invitee to use, or cancelling and rebooking — which generates two emails, not a quiet move. - Cancelling a group event cancels it for everyone. Calendly's FAQ states the cancel endpoint can cancel a group event but not an individual invitee within one. There is no cancel-one-attendee tool.
- Invitee personal data flows into the chat transcript.
meetings-list_event_inviteesandmeetings-get_event_inviteereturn invitee records, which Calendly's own AI agents guide shows carrying name, email address, timezone,questions_and_answersfrom your booking form, tracking parameters and cancel/reschedule URLs. Those are third parties' details, and once read they live wherever your assistant's conversation history lives. Calendly's own QA checklist advises that logs redact PII — advice worth extending to the transcript. - Booking requires a paid plan; routing forms require Teams or higher. Calendly's supported-tools table asterisks five rows:
meetings-create_inviteeneeds a paid plan, and all fourrouting_forms-*tools need Teams or above. Connecting is free; those six tools are not. Everything else works on Free. - The write scope is not per-tool.
mcp:scheduling:writecovers creating event types, editing availability, booking, cancelling, inviting organization members and generating links, in one grant. And because Calendly documents that:writeimplicitly includes:read, there is no write-without-read option either. - DCR is mandatory, so some clients simply cannot connect. Calendly states in a warning on its own MCP page that a client requiring a console-issued
client_idandclient_secretwill not work today. Personal access tokens are also explicitly unsupported for MCP, though they remain valid for Calendly's REST API. - The path is not
/mcp. The endpoint is the bare host with a trailing slash. We verified on 2026-08-18 thathttps://mcp.calendly.com/mcpreturns HTTP 404 while the bare host returns a 401 challenge. - Webhooks are not part of this connector. Calendly's REST scope catalogue includes
webhooks:readandwebhooks:write, but neither is among the two MCP scopes and no webhook tool appears in either tool list. Real-time notification of bookings and cancellations stays a REST-API job, and Calendly's FAQ notes webhook subscriptions need a paid Standard, Teams or Enterprise plan. - No MCP rate limits are published. Calendly documents a 31-day ceiling on the available-times endpoint and heavy rate limiting on the DCR registration endpoint, but publishes no per-minute request budget for the MCP server itself. Do not assume one protects you.
- No prompts, and no schema detail. Anthropic's snapshot records zero prompts. Because the endpoint is OAuth-gated we read no tool descriptions, parameters or safety annotations — Calendly says its tools carry
readOnlyHint,destructiveHintandidempotentHint, but that is its claim, not our observation. - We did not authenticate and we called nothing. Our check was an anonymous protocol request that returned an OAuth challenge, plus reads of the server's own well-known descriptors. We never signed in, never booked a meeting and never cancelled one. Everything above about behaviour comes from Calendly's documentation or Anthropic's directory listing, each dated below.
Frequently asked questions
What Calendly subscription do I need to use the API?
Any plan, including Free, for most of it. Calendly's developer FAQ states that GET and POST requests can be made on behalf of a user on any subscription plan, with a few Enterprise-only endpoints excepted, and that webhook subscriptions require a paid Standard, Teams or Enterprise plan. Calendly's help centre says the same for MCP specifically: no paid plan is needed to connect, though some actions vary by plan.
Can I cancel or reschedule an event through the API?
Cancelling yes, rescheduling no. Calendly's developer FAQ states that an event is cancelled with a POST request to the cancel event endpoint, and that no API endpoint supports rescheduling an event or invitee. Reschedule and cancel URLs are published on the invitee resource and in webhook payloads instead, so an assistant can retrieve and pass on the link but cannot move the meeting itself.
Can I schedule an event through the API?
Yes. Calendly's developer FAQ states that the Scheduling API books meetings directly from apps, workflows or AI assistants. The MCP tool behind it is meetings-create_invitee, which Calendly's supported-tools table maps to POST /invitees and marks as requiring a paid Calendly plan. Its AI agents guide adds that invitation emails and texts fire from the event type's own notification settings.
How long is a single-use scheduling link valid for?
Ninety days. Calendly's developer FAQ states that single-use scheduling links which have not been used to book an event expire after 90 days. The connector creates them two ways: scheduling_links-create_single_use_scheduling_link makes an uncustomised link, and shares-create_share makes a customised one from an existing event type.
Can I update my schedule or availability through the API?
Yes. Calendly's developer FAQ states that an event type's availability is updated by calling the Update Event Type Availability Schedules endpoint. Two tools cover this: event_types-update_event_type_availability_schedule writes the schedule, and availability-list_user_availability_schedules and availability-list_user_busy_times read it. Calendly's own example prompt is removing Fridays from a coaching session's available days.
What are the conditions that result in an access token being revoked?
Three account changes revoke tokens automatically. Calendly's developer FAQ states that both OAuth and personal access tokens are revoked if the account's login email, password or login method is changed. Tokens can also be revoked manually — OAuth tokens through the revoke token endpoint. Any of these ends the assistant's access immediately, so a password reset disconnects the connector.
Does Calendly sell my data or use it to train AI models?
No. Calendly's AI help centre article states plainly that Calendly does not sell customer data or use it to train AI models, and that no third-party AI provider is allowed to train on your data. It adds that data you submit and responses you receive serve only your own experience and are not shared between customers. Calendly names OpenAI as its current LLM provider for AI features.
Sources
- Calendly MCP Server documentation (retrieved 2026-08-18) — hosting statement, DCR requirement and its warning box, the OAuth discovery walkthrough, example prompts, and the annotation-metadata claim · retrieved 2026-08-18
- Calendly MCP: Supported Tools (retrieved 2026-08-18) — the vendor's complete 36-row tool table with REST endpoint mappings and the five plan-gate asterisks, read from raw HTML to confirm the gates · retrieved 2026-08-18
- Calendly developer FAQ (retrieved 2026-08-18) — the source of six of the seven questions above: subscription requirements, cancellation and rescheduling, scheduling, availability updates, single-use link expiry and token revocation conditions · retrieved 2026-08-18
- Authorization Scopes (retrieved 2026-08-18) — the REST scope catalogue, and the rule that a
:writescope implicitly includes the matching:read· retrieved 2026-08-18 - Schedule Events with AI Agents (retrieved 2026-08-18) — the booking flow, the invitee payload fields, the paid-plan requirement for the Scheduling API, the 31-day available-times limit and the PII-redaction advice · retrieved 2026-08-18
- Connect Calendly to your AI tools (retrieved 2026-08-18, article updated 2026-07-13) — the Claude and ChatGPT connection steps, the example prompts, and the statement that no paid Calendly plan is required to connect · retrieved 2026-08-18
- AI at Calendly (retrieved 2026-08-18, article updated 2026-08-10) — the data-handling answers quoted in the FAQ above · retrieved 2026-08-18
- Calendly MCP blog announcement (published 2026-05-29, retrieved 2026-08-18) — additional example prompts and the free-tier statement · retrieved 2026-05-29
- Live auth posture check against
https://mcp.calendly.com/— an anonymousinitializereturns - Authorization server metadata —
https://calendly.com/.well-known/oauth-authorization-serverreturns HTTP 200 withregistration_endpoint: "https://calendly.com/oauth/register",code_challenge_methods_supported: ["S256"]andtoken_endpoint_auth_methods_supported: ["none"], and noscopes_supportedkey. The same path onmcp.calendly.comreturns HTTP 404. Our own observation, 2026-08-18. · retrieved 2026-08-18 - Anthropic Connectors Directory entry — — the 36 tool names, the
partnertier, the productivity category, the streamable-HTTP transport, thehttps://mcp.calendly.com/endpoint and the "Read and write" permission label, from our committed snapshot dated 2026-08-16 · retrieved 2026-08-16 - Calendly privacy notice
developer.calendly.com/robots.txt(retrieved 2026-08-18) allows all paths, names the sitemap we used to resolve every page URL above without guessing, and carries noContent-Signaldirectives.calendly.com/robots.txtallows/help/and/blog/while disallowing/app/and query strings, and likewise carries noContent-Signaldirectives. Neither host serves a usablellms.txton the developer domain —developer.calendly.com/llms.txtreturns the Gatsby 404 SPA shell with HTTP 200, as does appending.mdto any page URL. · retrieved 2026-08-18
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Calendly
- Tools
- 36
- Domain
- mcp.calendly.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.