Reclaim
SchedulingSchedules focus time, tasks and habits around meetings. Reclaim 2.0 has an official MCP server for supported AI clients; proposed scheduling changes go to Preview Mode for review before application.
Independent review. Unpaid; no partnership with Cal.com. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Scheduling with booking pages, routing forms and an API. Its hosted or local MCP server lets authorized AI assistants list, create, reschedule or cancel bookings. Cal.diy is a separate community edition with different capabilities.
Judgment, not a score. Documentation checked 2026-10-18.
Connections: MCP connections · APIs · Portability and vendor lock-in.
The current page lists Free for one user with unlimited event types, Teams at $12/user/month with yearly billing, Organizations at $28/user/month with yearly billing, and custom Enterprise pricing. Teams includes round-robin and routing forms; Organizations adds sub-teams and SAML SSO/SCIM. Confirm currency, taxes and monthly terms in checkout. source ↗
The hosted MCP endpoint uses Streamable HTTP and OAuth 2.1. The local server uses stdio and an API key. Toolsets can be restricted, but the underlying account's permissions and plan still matter. Review booking changes before execution. source ↗
The official public repository now redirects to Cal.diy, an MIT-licensed community edition with commercial features removed. Its maintainers recommend it for personal, non-production self-hosting. Do not assume Cal.com Teams, Organizations or enterprise features are included. source ↗
How Cal.com connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Cal.com's docs name Claude (incl. Claude Code). A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Cal.com named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Cal.com publishes an API, but this pairing still needs network, authentication and execution-scope checks. Cal.com API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Cal.com is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Cal.com's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Cal.com file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Cal.com has an official MCP server and OpenAI Codex supports MCP, but Cal.com's docs don't name this pairing. Auth setup may differ. Cal.com MCP docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Cal.com publishes an API, but this pairing still needs network, authentication and execution-scope checks. Cal.com API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Cal.com is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Cal.com's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Cal.com file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Cal.com has an official MCP server and Google Antigravity supports MCP, but Cal.com's docs don't name this pairing. Auth setup may differ. Cal.com MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Cal.com publishes an API, but this pairing still needs network, authentication and execution-scope checks. Cal.com API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Cal.com is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Cal.com's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Cal.com file docs ↗Google Antigravity file docs ↗ |
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | Yes | Official docs ↗ (Calendly event import is documented; this does not establish generic CSV upload) |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
No long-form review yet. Verdict is based on research, not hands-on testing.
Schedules focus time, tasks and habits around meetings. Reclaim 2.0 has an official MCP server for supported AI clients; proposed scheduling changes go to Preview Mode for review before application.