Book and reschedule meetings from chat

Sales, CRM & outreach · Ops & admin automation · checked 2026-10-17

Connect Cal.com’s MCP server to Claude, then ask it to find a slot, book, reschedule or cancel. Claude confirms with you before each change.

Independent review. IonBin has no partnership with any tool on this page and was not paid for this page. Our evaluation is our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Goal

Handle scheduling back-and-forth in one message.

Connects through: MCP

Steps

#WhoWhat happensHowStatus
1Cal.com Finds availability and books, reschedules or cancels MCP Confirmed · source ↗
2Claude Proposes the change and drafts the note to attendees AI platform Confirmed
3You Confirm each booking change Human step Confirmed

Confirmed means the vendor documents it (linked). It doesn't mean IonBin has tested it. AI-platform and human steps need no source.

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. Your part: finds availability and books, reschedules or cancels; proposes the change and drafts the note to attendees. 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.

Tools in this workflow

ToolRoleOfficial site
Cal.comMCP cal.com ↗
ClaudeAI platform claude.ai ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) Confirmed Every MCP and API step is documented for this platform.
OpenAI Codex To verify Cal.com: pairing not named in vendor docs
Google Antigravity To verify Cal.com: pairing not named in vendor docs
ChatGPT To verify Cal.com: pairing not named in vendor docs
Gemini To verify Cal.com: pairing not named in vendor docs
Perplexity To verify Cal.com: pairing not named in vendor docs

Computed from the MCP and API steps only: "Confirmed" needs the tool's docs to name the platform and the platform to support the connection. Browser, upload and human steps work from any platform.

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-17).

Set it up

  1. Connect Cal.com to Claude, limited to the bookings and availability toolsets.
  2. Ask in plain language: “Find 30 minutes with Sam next week and book it” or “Move tomorrow’s 2 pm to Thursday.”
  3. Claude proposes the change and drafts a short note to attendees.
  4. Confirm each change before Claude makes it.

Sources

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.