Connect Cal.com to Claude to find available slots and propose booking changes. Configure tool permissions so you approve each change before it is made.
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 arranging appointments from scheduling requests.
Test time zones, duplicates and cancellations before approving changes. 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.
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
You confirm every booking change.
Watch out for
Keep the human approval step: You confirm every booking change.
Starter prompt
Goal: Handle scheduling back-and-forth in one message. Tools involved: Cal.com, Claude. I will confirm each booking change. Work step by step, show me each draft or proposed change, and wait for my approval before anything is sent, published, signed, filed or changed in a live system.
Assembled from this page’s goal and steps. Paste it into your AI platform and adjust it to your situation.
Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Gemini
To verify
Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Cal.com: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Cal.com: 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
Hosted server.Cal.com’s MCP server is at https://mcp.cal.com/mcp and wraps Cal.com API v2. It signs you in with OAuth, so no API key is needed. A self-hosted version runs locally with an API key.
Tools.Cal.com lists 72 tools, including get_availability, create_booking, reschedule_booking, cancel_booking and confirm_booking. You can limit a session to some toolsets by adding a parameter to the URL, for example ?toolsets=bookings,availability.
Plans. The MCP page doesn’t name a plan requirement. Cal.com lists $0 for one user, Teams at $12 and Organizations at $28 per user a month billed yearly (checked 2026-10-18).
Set it up
Connect Cal.com to Claude, limited to the bookings and availability toolsets.
Ask in plain language: “Find 30 minutes with Sam next week and propose it for my approval” or “Propose moving tomorrow’s 2 pm to Thursday; do not change it yet.”
Claude proposes the change and drafts a short note to attendees.
Configure the client to require approval for booking writes, then approve the exact attendee, timezone and change before execution. Prompt wording alone does not enforce approval. Cal.com’s confirm_booking tool accepts a pending reservation; it is not an assistant permission control.
Verification limits and implementation checks
The page is documentation-reviewed; the complete workflow has not been run by IonBin.
Test timezone handling, permissions and notifications on a harmless booking before wider use.