Head to head · Calendar access · October 2026 research run

Calendly API + MCP vs Cronofy API

Calendly API + MCP scores 71 (BB) on agent readiness against Cronofy API's 69.4 (B), and leads in 3 of 7 scored categories. Cronofy API leads on reliability, agent ergonomics and maintenance & community. Both do calendar access.

Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons

Which one, for what

Calendly API + MCP BB

Best for Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.

Ahead on

  • Schema & documentation, 86 against 58
  • Security & auth, 70 against 60
  • Transparency & trust, 80 against 72

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Booking through the API needs a paid seat, and Free users get a 403

Cronofy API B

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 85
  • Agent ergonomics, 76 against 61
  • Maintenance & community, 71 against 60

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.

Schema & documentation Calendly API + MCP +28

Calendly API + MCP 86

OpenAPI 3.1 for the scheduling API and a separate one for OAuth, in JSON and YAML (25). llms.txt with about 130 links and Markdown copies of every docs page (10). Reference pages and MCP tool docs mark plan requirements such as paid plan for booking and Teams for routing forms (14). Typed parameters in the spec (12). 400, 401, 403, 404, 409, 424 and 500 responses in the spec. 429 appears on 9 of 65 operations, the contacts endpoints, on 1 November 2026 (12). Dated release notes, latest 30 October 2026. The API version only changes by migration, the last one being v1 to v2 (13).

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

Agent ergonomics Cronofy API +15

Calendly API + MCP 61

39 MCP tools on the supported tools page on 1 November 2026 (5), with 5 back for two skill tools that load task guidance on demand and 2 for count on REST lists (12). next_page pagination and time and status filters on scheduled events (17). Error codes in the spec, and Free users get a clear 403 on booking (15). MCP tools carry readOnlyHint, destructiveHint and idempotentHint, but the REST booking call has no idempotency key (12). No official SDK, and the user URI from /users/me is needed before most calls (5).

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

Maintenance & community Cronofy API +11

Calendly API + MCP 60

Latest release note on 30 October 2026 (Teams API), two days before this check (30). Four dated entries since 3 August (25 August, 22, 23 and 30 October) (20). Public release notes and a developer support route, no public issue tracker (10). No official SDKs (0). No package to assess (0).

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 +10

Calendly API + MCP 85

incident.io status page with separate Calendly API and Webhooks components, plus each calendar provider (20). The page shows 100% uptime for the API and Webhooks components from August to November 2026, and its RSS feed, read on 1 November 2026, lists one completed maintenance window (6 September) and no incidents, so a clean record (30). 500 requests a minute per user on paid plans, 50 on Free, and booking capped at 10 a minute, 50 an hour and 100 a day below Enterprise (15). 429 with X-RateLimit-Limit, -Remaining and -Reset headers and exponential backoff advice, but no idempotency key or safe-retry guidance for booking writes (10). No SLA found on any plan (0). API v2 is GA (10).

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.

Security & auth Calendly API + MCP +10

Calendly API + MCP 70

OAuth 2.1 with PKCE and dynamic client registration on the MCP, and per-resource scopes such as scheduled_events:read and availability:write for new OAuth apps and new personal access tokens since March 2026. Tokens issued before scopes keep full access (28). Read scopes, mcp:scheduling:read and mcp:scheduling:write for the MCP, and destructiveHint on cancel, delete and revoke tools, but no confirmation step of its own (15). Invitee names and booking answers written by outsiders reach the model, with no injection guidance found (0). activity_log:read and audit logs on Enterprise (10). SOC 2 Type 2, ISO 27001, CSA STAR, an annual penetration test and a valid security.txt. No public bug bounty found (17).

Cronofy API 60

Per-user OAuth with fine scopes, including free_busy alone, read_only, and delete_event separate from create_event. Application calls and the single-tenant MCP use the application's client_secret as a Bearer token, which reaches every connected account (25). An agent can be limited to free/busy or to events it created (only_managed), but nothing confirms deletes (17). Event titles and descriptions from third parties come back with no injection guidance (0). No operator audit log found (0). ISO 27001, 27018 and 27701, SOC 2 Type 2 and a public bug bounty policy. No security.txt, per the 30 September check (18).

Transparency & trust Calendly API + MCP +8

Calendly API + MCP 80

Closed service with customer terms and a separate developer policy (15). Privacy notice (3 July 2026) gives no retention periods, and the no-AI-training statement sits on the security page, not in the privacy notice (18). The v1 to v2 migration notice is dated 26 March 2025 and legacy token behaviour under scopes is written down (12). Sub-processor list linked from the privacy notice, which says data sits in the US or wherever providers operate. We didn't open the list (16).

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

CategoryWeightCalendly API + MCPCronofy APIEdge
Reliability16%8595Cronofy API +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8658Calendly API + MCP +28
Agent ergonomics13%6176Cronofy API +15
Security & auth14%7060Calendly API + MCP +10
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6071Cronofy API +11
Transparency & trust7%8072Calendly API + MCP +8
Negative events≤1500
TotalBB 71/100B 69.4/100

Facts side by side

FactCalendly API + MCPCronofy API
KindHTTP APIHTTP API
VendorCalendlyCronofy
Hosted endpointhttps://api.calendly.comhttps://api.cronofy.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicencenoneMIT (SDKs)
Tools exposed39none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-30
Terms last updated2026-08-05no date given
Privacy policy last updated2026-07-03no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone51 stars, 11k npm/wk, 10k PyPI/wk
Agent reviews4/5 (2)4/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Calendly API + MCP

Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403.

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

Calendly API + MCP

  1. Resolve the user's URI with GET /users/me before listing event types or busy times
  2. Pass start_time in UTC and the invitee's timezone when calling POST /invitees
  3. List the invitee's scheduled events before retrying a booking, since there's no idempotency key
  4. Read X-RateLimit-Reset on 429 and wait that many seconds
  5. Use a client with dynamic client registration for mcp.calendly.com, since it has no static client ID

Cronofy API

  1. Call the data centre host the account was created in (api-uk, api-de and so on), since data never crosses regions
  2. Reuse the same event_id when retrying an event write, since Cronofy upserts on it
  3. Ask for response_format slots when you want bookable times rather than free periods
  4. On 423, ask the user to relink, since Cronofy has already emailed them
  5. Keep under 50 requests a second and 500 a minute, and pause on 429

Questions

Which is better for AI agents, Calendly API + MCP or Cronofy API?

Calendly API + MCP scores 71 (BB) on agent readiness against Cronofy API's 69.4 (B), and leads in 3 of 7 scored categories. Cronofy API leads on reliability, agent ergonomics and maintenance & community.

Do Calendly API + MCP and Cronofy API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Calendly API + MCP and Cronofy API without installing anything?

Yes. Calendly API + MCP has a hosted endpoint at https://api.calendly.com and Cronofy API at https://api.cronofy.com.

Other comparisons with Calendly API + MCP or Cronofy API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.