# Cal.com API v2 + MCP vs Reclaim.ai (slim)

> Cal.com API v2 scores 51.1 (D) to Reclaim.ai's 37.9 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cal-com-vs-reclaim-ai.md (~4,650 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/cal-com-vs-reclaim-ai.json · canonical https://www.anchorterminal.com/compare/cal-com-vs-reclaim-ai
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Cal.com API v2 + MCP scores 51.1 (D) on agent readiness against Reclaim.ai's 37.9 (F), and leads in every scored category. Both do calendar access.

- Cal.com API v2 + MCP: D 51.1, rank #1039 of 1510 · https://www.anchorterminal.com/tools/cal-com.min.md
- Reclaim.ai: F 37.9, rank #1371 of 1510 · https://www.anchorterminal.com/tools/reclaim-ai.min.md
- Cal.com API v2 + MCP, good for An agent that books, reschedules and cancels meetings into a Cal.com user's event types, or routes leads with routing forms. Ahead on Reliability, 65 against 45; Schema & documentation, 76 against 28; Agent ergonomics, 50 against 30; Payments & pricing, 30 against 25; Maintenance & community, 35 against 25; Transparency & trust, 80 against 56. Also Runs on your own machine.
- Reclaim.ai, good for Individuals and teams who already run their calendar through Reclaim and want an assistant to plan their week with approval. Also No incidents deducted, where Cal.com API v2 + MCP loses 6 points for them.

| Category | Cal.com API v2 + MCP | Reclaim.ai |
| --- | --- | --- |
| Reliability (16%) | 65 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 28 |
| Agent ergonomics (13%) | 50 | 30 |
| Security & auth (14%) | 56 | 53 |
| Payments & pricing (10%) | 30 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 35 | 25 |
| Transparency & trust (7%) | 80 | 56 |

| Fact (where they differ) | Cal.com API v2 + MCP | Reclaim.ai |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Cal.com | Reclaim.ai Inc. |
| Hosted endpoint | `https://api.cal.com/v2` | `https://mcp.reclaim.ai` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Licence | Proprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licence | none |
| Tools exposed | 63 | none |
| llms.txt | yes | no |
| Last release | 2026-09-15 | none |
| Terms last updated | no date given | 2024-04-08 |
| Privacy policy last updated | 2026-10-01 | 2025-06-25 |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 30 stars, 786 npm/wk | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Schema & documentation, Cal.com API v2 + MCP +48: Cal.com API v2 + MCP 76 (OpenAPI 3.0 document for API v2 (25). llms.txt and Markdown copies of reference pages (10). Reference pages explain each endpoint and parameter, but the hosted MCP's tool descriptions aren't public since the code went closed (12). Typed parameters with ranges, such as `limit` 1 to 100 with a default of 50 and enumerated booking statuses (12). Examples on reference pages. The response envelope has `status` success or error, but we found no error catalogue (8). Date-based `cal-api-version` per endpoint (2026-05-01 for bookings, 2024-09-04 for slots), and release notes come as blog posts rather than an API changelog (9). Docs readings are per the 1 October check, not re-read on 4 November (cal.com hosts paused). Total 76.); Reclaim.ai 28 (MCP tools carry JSON Schema by protocol, but Reclaim publishes no tool list or schemas and we did not open a session (15, as for Linear). No llms.txt (404) (0). Tool descriptions not readable (5). Input typing not verifiable (5). Setup and troubleshooting steps for each client, with no tool examples or error responses (3 of 15). No changelog or versioning for the MCP server found (0). 15 + 0 + 5 + 5 + 3 + 0 = 28.)
- Transparency & trust, Cal.com API v2 + MCP +24: Cal.com API v2 + MCP 80 (Closed source since 14 April 2026. The Terms of Service were rewritten as version 2.0, effective 1 November 2026, naming Cal.com, Inc., a Delaware corporation, under Delaware law, and they say Cal.diy and Cal.com's other open-source releases are governed by their own licences (MIT for Cal.diy). Closed with clear terms (15, from 12). Privacy policy (20 August 2026) says nothing is used to train models, account data is kept while active with a 30-day export window after closure, and logs exclude personal data. DPA in the compliance portal (22). Platform deprecation dated 15 December 2025 and date-pinned API versions. The new terms promise prior notice by email or in product for updates that materially reduce a customer's rights, and name a periodic changelog for deprecations (14). Subprocessors are listed in the trust centre per the privacy policy, which we didn't open, and data sits in the US with EU residency on request (13). Privacy, DPA and trust readings are per the 1 October check, not re-read on 4 November. Total 64.); Reclaim.ai 56 (Closed service under terms of 8 April 2024 naming Reclaim.ai Inc. (15 of 30). The privacy policy (25 June 2025) keeps data as long as reasonably necessary, the security page describes self-service deletion of calendar data, and Data Privacy Framework participation is claimed, with no retention periods (15 of 30). Reclaim 1.0 users are moved to 2.0, and no deprecation policy or dates were found (3 of 20). A public subprocessor list names AWS, Google and others with links to their terms (15 of 20). 15 + 15 + 3 + 15 = 48.)
- Reliability, Cal.com API v2 + MCP +20: Cal.com API v2 + MCP 65 (OpenStatus page at status.cal.com with App, Website and API components and an events log back to February 2024, per the 1 October reading (20). cal.com hosts are paused for this run under the terms of 1 November 2026, so the page wasn't re-read. In the readable part of the window, the 31 August outage (1 hour 14 minutes of HTTP 500s on /v2/slots and /v2/bookings, US East only) hit one region and two endpoints, and the 15 September event was a 1 hour 19 minute degradation of App and API. This run reads one region or a group of calls as partial, so both count as minor. 1 October to 4 November is unread and not credited (20, from 10). 120 requests a minute per key or OAuth token, raisable to 200 and then to 800 on request (15). No 429 behaviour, rate-limit headers or retry guidance in the docs or the OpenAPI spec (0). Enterprise lists "SLA guarantees" with no published figure or document, and a listed SLA nobody could read gives 0 in this run (0, from 5). API v2 is GA (10). Total 65.); Reclaim.ai 45 (Graded as a hosted service on the MCP server at mcp.reclaim.ai. Statuspage at status.reclaim.ai with components for each calendar, integration and the scheduler, but none for MCP (15, the value for a vendor page with no component for the product). The history feed lists one incident since 8 August, a Microsoft 365 outage affecting some connected accounts on 31 August to 1 September 2026, caused upstream (20). No rate limits found (0). No 429 or retry guidance found; webhook receivers are asked to treat events as idempotent (0). No SLA found (0). The MCP server is not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.)
- Agent ergonomics, Cal.com API v2 + MCP +20: Cal.com API v2 + MCP 50 (63 tools on the hosted MCP (5), with a `toolsets` query parameter to load only the groups you need and catalogue meta-tools (find, describe and call an API operation) (+10). Cursor pagination with `limit`, and filters on status, attendee, event type, team and start, end, created and updated times (20). Error envelope without documented codes (8). No idempotency key on bookings found, and we couldn't read the hosted tools for readOnlyHint or destructiveHint (0). No official REST SDK in two languages (Atoms is React components), and every endpoint needs the right version header (7). Per the 1 October check, not re-read on 4 November. Total 50.); Reclaim.ai 30 (Tool count not published (5). Paging and filtering not documented (5 of 20). No documented error responses (3 of 20). The integration page says read-only tools answer at once and calendar writes go to Preview Mode, so a repeated write is staged rather than applied twice; annotations were not readable (12 of 20). One URL with OAuth and no SDK (5 of 15). 5 + 5 + 3 + 12 + 5 = 30.)
- Maintenance & community, Cal.com API v2 + MCP +10: Cal.com API v2 + MCP 35 (The newest dated change found for the hosted API is the v6.9 changelog post of 15 September 2026, 50 days before this check, and cal.com hosts are paused so the blog wasn't re-read (20, from 30, cause time). One dated changelog post in the 90 days partly meets the three-entry line, so the earlier partial value is kept, pending the founder's rule on in-between values (5). The @calcom/cal-mcp repository's last commit is 0.0.6 on 22 May 2025, and calcom/cal.com now holds the Cal.diy fork, whose last version tag (v6.2.0) is dated 1 March 2026, so neither adds a release. A 4 November Cal.diy commit says @calcom/atoms is now published from a separate repository at 2.6.12; npm wasn't readable, so its dates are unchecked. Public blog changelog and support, no public issue tracker for the closed product (10). No current official REST SDKs, and the npm MCP package has sat at 0.0.6 since 22 May 2025 (5). The cal-mcp repository's test workflow has its test step commented out (0). Total 40.); Reclaim.ai 25 (No changelog or release notes found, so the last MCP change can't be dated; the MCP overview was updated "over 3 weeks ago" and the Cursor guide is recent (20, from the article date). No dated release entries (0). Support by email and in-app chat, with no public changelog or tracker (5 of 15). Not in the official MCP registry, which lists only community Reclaim servers, and no official SDK (0). No package to check (0). 20 + 0 + 5 + 0 + 0 = 25.)
- Payments & pricing, Cal.com API v2 + MCP +5: Cal.com API v2 + MCP 30 (No x402, MPP or L402 (0). Seat prices published ($12 and $28 a user a month billed yearly) but nothing per call or per booking (10). Free plan for one user with API access, no card (20). Browser signup, and OAuth clients need admin approval (0).); Reclaim.ai 25 (No x402, MPP or L402 (0). Per-seat plan prices are public, with nothing per call (10). Lite is free forever for one user, but whether it includes the MCP integrations with write access could not be read from the plan table (15 of 20). A person signs up in a browser and approves OAuth (0). 0 + 10 + 15 + 0 = 25.)