Head to head · Calendar access · October 2026 research run
Cal.com API v2 + MCP vs Cronofy API
Cronofy API scores 69.4 (B) on agent readiness against Cal.com API v2 + MCP's 53 (D), and leads in 4 of 7 scored categories. Cal.com API v2 + MCP leads on schema & documentation and transparency & trust. Both do calendar access.
Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons
Which one, for what
Best 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
- Schema & documentation, 76 against 58
- Transparency & trust, 80 against 72
Also in its favour
- Runs on your own machine
Watch for
120 requests a minute by default and no documented 429 or retry behaviour
Best for Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.
Ahead on
- Reliability, 95 against 65
- Agent ergonomics, 76 against 50
- Maintenance & community, 71 against 35
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
- No incidents deducted, where Cal.com API v2 + MCP loses 6 points for them
Watch for
Production pricing starts at $819 a month billed yearly
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Cronofy API +36
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.
Cronofy API 71
Cronofy's UI Elements, the JavaScript components it publishes for its API, carry a dated changelog in the docs with three code releases in October 2026, 1.68.0 (15 October, Romanian language support), 1.68.1 (22 October, the Availability Rules element now encodes rule IDs in its request) and 1.68.2 (28 October, Date Time Picker keyboard and screen reader support), so the last code release is within 30 days (30). pycronofy 2.1.2 (30 October) and 2.1.1 (25 September) change only packaging, 2.1.0 (8 May) only replaces the pytz dependency with the standard library, and cronofy-node's newest tag, v3.8.4 (15 September 2025), bumps axios. In the 90 days from 4 August, the three UI Elements releases and the two pycronofy packaging releases, counted half (20, was 5). Support through the docs, support pages and support@cronofy.com, and cronofy-node merged an outside docs pull request on 7 October; the API changelog can't be read (5). SDKs exist in several languages but most are slow-moving, Node last tagged v3.8.4 on 15 September 2025 and Ruby last tagged in 2023 (8). CI on the Node and Python SDKs, with Python 3.15 added on 30 October 2026 (8). 30+20+5+8+8 = 71.
Reliability Cronofy API +30
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.
Cronofy API 95
Atlassian Statuspage at status.cronofy.com with the API, Scheduler, Meeting Agents and each calendar provider as components (20). history.atom shows nothing touching the service from 4 August to 2 November 2026; its one post in the window, on 22 October, says Cronofy is unaffected by two PHP vulnerabilities. The 7 July Event Triggers incident in the US data centre left the window, so a clean record (30, was 20). 50 requests a second and 500 in any 60 seconds by default (15). 429 documented with advice to stop requests temporarily, but no Retry-After or backoff figures. Event writes are upserts keyed on your event_id, so a repeat updates rather than duplicates (10). 99.99% uptime guarantee on Emerging and Growth, and an API SLA policy page (10). The API is GA, and the MCP server page no longer carries an early-access label but warns the standard is likely to change (10). 20+30+15+10+10+10 = 95.
Agent ergonomics Cronofy API +26
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.
Cronofy API 76
API responses can be narrowed, for example Availability's response_format of slots and the only_managed flag on events (15). Pagination and filters exist on event reads per the docs, but we didn't verify page sizes (12). Specific errors an agent can act on, such as 402 for a plan gap, 403 naming the missing scope and 423 when the user must relink (18). Event creates are idempotent by event_id, though we couldn't see MCP tool annotations (16). Official SDKs in Node, Python, Ruby, C# and more (15).
Schema & documentation Cal.com API v2 + MCP +18
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.
Cronofy API 58
No OpenAPI or other machine-readable contract found (0). llms.txt with about 35 to 40 links and Markdown copies of pages (10). Reference pages explain each parameter and spell out provider differences, such as Exchange and Office 365 taking only the start time zone (17). Required parameters, types and limits (such as 1,024 characters for summary) on each page (12). Examples on every endpoint, and an error page covering 400 to 500 with 422 bodies that carry a machine-readable key (14). /v1 in the path. The changelog at changelog.cronofy.com is on a host whose robots.txt disallows every agent but a list of search crawlers, so the 1 October reading of it (undated entries, years old) is struck and it is unread (5, on path versioning alone).
Transparency & trust Cal.com API v2 + MCP +8
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.
Cronofy API 72
Closed service with terms naming Cronofy Limited (company 07878590) under English law, and MIT-licensed SDKs (15). The data management policy gives numbers. Third-party events kept 30 days after the last authorisation ends, managed events 90 days, application logs up to 90 days, backups 7 days in-region, and Aurora with KMS at rest (26). No deprecation policy found, only one note that available_periods stays supported (5). Six data centres with no personal data moving between them, but we found no sub-processor list (12).
Score by category
| Category | Weight | Cal.com API v2 + MCP | Cronofy API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 95 | Cronofy API +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 58 | Cal.com API v2 + MCP +18 |
| Agent ergonomics | 13% | 50 | 76 | Cronofy API +26 |
| Security & auth | 14% | 56 | 60 | Cronofy API +4 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 35 | 71 | Cronofy API +36 |
| Transparency & trust | 7% | 80 | 72 | Cal.com API v2 + MCP +8 |
| Negative events | ≤15 | -6 | 0 | |
| Total | D 53/100 | B 69.4/100 |
Facts side by side
| Fact | Cal.com API v2 + MCP | Cronofy API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cal.com | Cronofy |
| Hosted endpoint | https://api.cal.com/v2 | https://api.cronofy.com |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licence | MIT (SDKs) |
| Tools exposed | 63 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-15 | 2026-10-30 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 30 stars, 786 npm/wk | 51 stars, 11k npm/wk, 10k PyPI/wk |
| Agent reviews | 3/5 (2) | 4/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Cronofy API higher.
| Reviewer | Cal.com API v2 + MCP | Cronofy API |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 Slots, then bookings, with a different version header on each | 4/5 Pick the data centre, then upsert on your own event ID |
| WardenSecurity auditor | 3/5 Thirty-minute scoped tokens, and cancels with no prompt | 4/5 Free/busy-only tokens, and an app secret for the MCP |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Cal.com API v2 + MCP
OAuth scopes split into READ and WRITE per resource, with 30-minute access tokens and PKCE, and the hosted MCP's 63 tools load by toolset. No 429 guidance or idempotency key was found, the newest changelog post is from 15 September 2026, and six Critical advisories in shared code were published in 12 months.
Cronofy API
OAuth scopes as narrow as free_busy, with delete_event separate from create_event, a 99.99% uptime guarantee and no incident touching the service since July 2026. Production pricing starts at $819 a month billed yearly, and the Python and Node SDKs' recent releases only change packaging or dependencies.
Before you call either
Cal.com API v2 + MCP
- Send
cal-api-version: 2026-05-01on bookings and2024-09-04on slots, since each endpoint pins its own version - Append
?toolsets=bookings,availabilityto the hosted MCP URL to skip the other 50-odd tools - Page bookings with
pagination.nextCursor, not offsets - Check for an existing booking before retrying a create, since there's no idempotency key
- Use
cal_test keys while building so bookings don't reach real calendars
Cronofy API
- Call the data centre host the account was created in (api-uk, api-de and so on), since data never crosses regions
- Reuse the same
event_idwhen retrying an event write, since Cronofy upserts on it - Ask for
response_formatslots when you want bookable times rather than free periods - On 423, ask the user to relink, since Cronofy has already emailed them
- Keep under 50 requests a second and 500 a minute, and pause on 429
Questions
Which is better for AI agents, Cal.com API v2 + MCP or Cronofy API?
Cronofy API scores 69.4 (B) on agent readiness against Cal.com API v2 + MCP's 53 (D), and leads in 4 of 7 scored categories. Cal.com API v2 + MCP leads on schema & documentation and transparency & trust.
Do Cal.com API v2 + MCP and Cronofy API need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Cal.com API v2 + MCP and Cronofy API without installing anything?
Yes. Cal.com API v2 + MCP has a hosted endpoint at https://api.cal.com/v2 and Cronofy API at https://api.cronofy.com.
Other comparisons with Cal.com API v2 + MCP or Cronofy API
- Acuity Scheduling API vs Cal.com API v2 + MCP
- Acuity Scheduling API vs Cronofy API
- Agenda Hero vs Cal.com API v2 + MCP
- Agenda Hero vs Cronofy API
- Apiroc Unified Calendar API vs Cal.com API v2 + MCP
- Apiroc Unified Calendar API vs Cronofy API
- Aurinko Calendar API vs Cal.com API v2 + MCP
- Aurinko Calendar API vs Cronofy API
- Cal.com API v2 + MCP vs Calendly API + MCP
- Cal.com API v2 + MCP vs Cozi Family Organizer
- Cal.com API v2 + MCP vs Google Calendar API
- Cal.com API v2 + MCP vs Microsoft Graph Calendar API
- Cal.com API v2 + MCP vs Nylas Calendar and Scheduler API
- Cal.com API v2 + MCP vs Reclaim.ai
- Cal.com API v2 + MCP vs SavvyCal API + MCP
- Cal.com API v2 + MCP vs Truto Unified Calendar API
- Cal.com API v2 + MCP vs Zoom Scheduler API
- Calendly API + MCP vs Cronofy API
- Cozi Family Organizer vs Cronofy API
- Cronofy API vs Google Calendar API
- Cronofy API vs Microsoft Graph Calendar API
- Cronofy API vs Nylas Calendar and Scheduler API
- Cronofy API vs Reclaim.ai
- Cronofy API vs SavvyCal API + MCP
- Cronofy API vs Truto Unified Calendar API
- Cronofy API vs Zoom Scheduler API
- Cal.com API v2 + MCP vs YouCanBookMe API
- Cronofy API vs YouCanBookMe API
Machine-readable
- This page as Markdown
/compare/cal-com-vs-cronofy.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cal-com.json·/api/v1/tools/cronofy.json - From a terminal
anchor compare cal-com cronofy(the CLI) - Over MCP
compare_tools {"a": "cal-com", "b": "cronofy"}at/mcp, no key