Claude reads your upcoming Calendly events and availability through Calendly's hosted MCP server and drafts a short weekly scheduling review. You decide on any availability change yourself.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For reviewing appointments and available buffers.
Switching requires new calendar mappings and verified time zones. Choose one for arranging and reviewing appointments; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Explicit availability comes before broader automation. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Verify time zones, permissions and calendar scope. Retest routing after a switch; appointment booking is not focus-time planning.
Reviewed 2026-10-21. This page applies a shared comparison for “arranging and reviewing appointments” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Drafts a review that flags back-to-back meetings, days over your limit and event types with no open slots
AI platformConfirmed
03
You
Decide whether to change availability or move meetings, and make the change yourself
Human stepConfirmed
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
Claude only reports. Any availability change or booking is your decision.
Watch out for
The Calendly connection is granted both read and write scopes, so the same client could change availability or book meetings. Keep the prompt explicit about reporting only, and check any change your client proposes before approving it.
Starter prompt
Using the Calendly MCP server, list my scheduled events for next Monday to Friday and my event types. Flag back-to-back meetings with no gap, any day with more than 5 meetings and any event type with no open slots next week. Don't change availability or book anything; just give me the list.
Written for this workflow. Paste it into your AI platform and adjust it to your situation.
Calendly: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked (2026-10-18)
Calendly MCP server.Calendly hosts the server at mcp.calendly.com and doesn’t support self-hosting. Clients register themselves and sign in with OAuth 2.1 and PKCE. The documented scopes are mcp:scheduling:read and mcp:scheduling:write, and full access needs both.
Tools. The tools map to Calendly API v2 and carry hints that mark read-only and destructive actions. Calendly’s example prompts include listing event types, finding open slots, changing availability and booking a meeting.
Set it up
Connect Calendly in Claude and complete the OAuth sign-in for the account whose calendar you want to review.
On Friday afternoon, run the prompt above.
Check flagged days in Calendly itself, since a connected calendar may hold events that aren’t Calendly bookings.
Make any availability change in Calendly yourself, or approve each change your client proposes, one at a time.
Pilot it on a small sample first, and keep the human step even when the output looks right. This is a proposed sequence based on documented tools, not a tested account integration.