Head to head · Calendar access · October 2026 research run

Cal.com API v2 + MCP vs Calendly API + MCP

Calendly API + MCP scores 71 (BB) on agent readiness against Cal.com API v2 + MCP's 53 (D), and leads in 5 of 7 scored categories. Both do calendar access.

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

Which one, for what

Cal.com API v2 + MCP D

Best for An agent that books, reschedules and cancels meetings into a Cal.com user's event types, or routes leads with routing forms.

Also in its favour

  • Runs on your own machine

Watch for

120 requests a minute by default and no documented 429 or retry behaviour

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

  • Reliability, 85 against 65
  • Schema & documentation, 86 against 76
  • Agent ergonomics, 61 against 50
  • Security & auth, 70 against 56
  • Maintenance & community, 60 against 35

Also in its favour

  • Agent-ready, a grade of BB or better
  • 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

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

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 Calendly API + MCP +25

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.

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

Reliability Calendly API + 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.

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

Security & auth Calendly API + MCP +14

Cal.com API v2 + MCP 56

OAuth with per-resource READ and WRITE scopes at user, team and organisation level, 30-minute access tokens, PKCE, and client secret rotation with two active secrets. OAuth clients are reviewed before use. API keys have test and live prefixes but no scopes (28). Read-only OAuth scopes and MCP toolsets narrow access, but nothing asks for confirmation before delete_event_type, cancel_booking or delete_org_membership (10). Bookings carry attendee-written names and notes into the model, with no injection guidance found (0). No operator request log found (0). ISO 27001, SOC 2 Type II and HIPAA claimed, an annual third-party penetration test, a Bugcrowd disclosure programme and a valid security.txt pointing to GitHub security advisories on the repository that now hosts the Cal.diy fork, where advisories are published (18). Per the 1 October check, not re-read on 4 November. Total 56.

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

Agent ergonomics Calendly API + MCP +11

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.

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

Schema & documentation Calendly API + MCP +10

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.

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

Score by category

CategoryWeightCal.com API v2 + MCPCalendly API + MCPEdge
Reliability16%6585Calendly API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7686Calendly API + MCP +10
Agent ergonomics13%5061Calendly API + MCP +11
Security & auth14%5670Calendly API + MCP +14
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3560Calendly API + MCP +25
Transparency & trust7%8080even
Negative events≤15-60
TotalD 53/100BB 71/100

Facts side by side

FactCal.com API v2 + MCPCalendly API + MCP
KindHTTP APIHTTP API
VendorCal.comCalendly
Hosted endpointhttps://api.cal.com/v2https://api.calendly.com
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licencenone
Tools exposed6339
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-152026-10-30
Terms last updatedno date given2026-08-05
Privacy policy last updated2026-10-012026-07-03
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity30 stars, 786 npm/wknone
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Calendly API + MCP higher.

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.

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.

Before you call either

Cal.com API v2 + MCP

  1. Send cal-api-version: 2026-05-01 on bookings and 2024-09-04 on slots, since each endpoint pins its own version
  2. Append ?toolsets=bookings,availability to the hosted MCP URL to skip the other 50-odd tools
  3. Page bookings with pagination.nextCursor, not offsets
  4. Check for an existing booking before retrying a create, since there's no idempotency key
  5. Use cal_ test keys while building so bookings don't reach real calendars

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

Questions

Which is better for AI agents, Cal.com API v2 + MCP or Calendly API + MCP?

Calendly API + MCP scores 71 (BB) on agent readiness against Cal.com API v2 + MCP's 53 (D), and leads in 5 of 7 scored categories.

Do Cal.com API v2 + MCP and Calendly API + MCP need an API key?

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

Can an agent call Cal.com API v2 + MCP and Calendly API + MCP without installing anything?

Yes. Cal.com API v2 + MCP has a hosted endpoint at https://api.cal.com/v2 and Calendly API + MCP at https://api.calendly.com.

Other comparisons with Cal.com API v2 + MCP or Calendly API + MCP

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.