Head to head · Calendar access · October 2026 research run

Cal.com API v2 + MCP vs Google Calendar API

Google Calendar API scores 82 (A) on agent readiness against Cal.com API v2 + MCP's 53 (D), and leads in every scored category. 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

Google Calendar API A

Best for An agent acting on Google Workspace or Gmail users' own calendars with tight scopes and no per-account fee.

Ahead on

  • Reliability, 90 against 65
  • Schema & documentation, 88 against 76
  • Agent ergonomics, 91 against 50
  • Security & auth, 77 against 56
  • Payments & pricing, 53 against 45
  • Maintenance & community, 87 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

Google calendars only

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 Google Calendar API +52

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.

Google Calendar API 87

@googleapis/calendar 20.1.0 on 3 October 2026 is still the newest on npm on 1 November, 29 days earlier, and the discovery document has moved to revision 20261028 (30). Release notes on 12 October, plus client releases on 10, 14 and 24 September and 3 October, all within the 90 days to 1 November (the July notes have aged out) (20). Dated release notes and public client repositories with active maintainers (12). Current official client libraries (15). Generated clients rebuilt by CI in google-api-nodejs-client, with commits up to 30 October in a clone on 1 November (10).

Agent ergonomics Google Calendar API +41

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.

Google Calendar API 91

Responses size with maxResults and Google's standard fields partial responses (20). pageToken, syncToken, timeMin and timeMax, q and singleEvents for expanding recurrences (20). Error reasons an agent can act on, with the action written next to each one (20). Client-supplied event IDs make creates safe to retry and ETags guard updates. We found no readOnlyHint or destructiveHint on the MCP's write tools (16). Official client libraries in many languages, and most parameters are optional (15).

Reliability Google Calendar API +25

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.

Google Calendar API 90

The Google Workspace Status Dashboard lists Calendar with component history and an incidents feed (20). On 1 November the dashboard's 365-day list shows two Calendar incidents, 31 May 2026 (56 minutes, several Workspace products) and 13 March 2026 (2 hours 30 minutes of intermittent errors), with none in the 90 days to 1 November. Other Workspace products have incidents in August and September (Drive, Gmail, Chat, Classroom and Gemini), none naming Calendar. The dashboard tracks the Calendar product rather than the API alone (30). 10,000 requests a minute per project, 600 a minute per user per project and 1,000,000 a day per project, unchanged on 1 November (15). 403 and 429 usageLimits errors with a truncated exponential backoff formula, client-supplied event IDs that return 409 on a duplicate, and ETags with 412 on a stale write (15). No SLA for the API found (0). The REST API is GA. The MCP server is still a developer preview on 1 November (10).

Security & auth Google Calendar API +21

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.

Google Calendar API 77

OAuth 2.0 with 20 Calendar scopes on the auth page, from calendar.freebusy and calendar.events.owned.readonly up to full calendar, and the discovery document (revision 20261028) carries a 21st, calendar.settings, which the auth page still doesn't list on 1 November (30), less 10 because the discovery document lists oauth_token and key as query parameters, the API also reads access_token from the query string, and Google's OAuth web-server guide shows the query string as an alternative to the header, read as for Gmail, Sheets and Forms (20). The auth page's table gives each scope's meaning only, and the non-sensitive, sensitive and restricted classes are per the 1 October check, not re-read on 4 or 17 October. Read-only and free/busy-only scopes, and the MCP guide (updated 29 October) still configures three read-only scopes. Nothing in the API confirms a delete (17). The MCP guide, updated 29 October, warns about indirect prompt injection and says prompts and responses must be screened, with Model Armor or a documented alternative, and tells operators to review AI-initiated actions (12). The Cloud console API dashboard shows traffic, errors by method and response code, and latency percentiles per project, but not a per-call log (8). Valid security.txt to 2030 with contacts and the Google VRP bug bounty policy, read on 1 November. Google's SOC 2 page sends customers to Compliance Reports Manager for the Google Workspace reports, and that Calendar is in their scope is per the 4 October check (20).

Schema & documentation Google Calendar API +12

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.

Google Calendar API 88

Google publishes a discovery document rather than OpenAPI, which is a machine-readable contract all the same, at revision 20261028 on 1 November (25). No llms.txt, and developers.google.com/llms.txt and /workspace/calendar/llms.txt returned 404 again on 1 November, but doc pages return Markdown when .md.txt is appended to the URL, which we found no index or link advertising, read as for Drive, Sheets and Forms (5 of 10). Reference pages say what each method does and when to use patch over update, but we couldn't read the MCP tool descriptions (15). Typed parameters with enums such as orderBy and eventTypes (13). An error page that gives each reason code a recommended action, from timeRangeEmpty to fullSyncRequired (15). v3 in the path and dated release notes, latest 12 October 2026, with nothing newer on 1 November (15).

Payments & pricing Google Calendar API +8

Cal.com API v2 + MCP 45

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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Google Calendar API 53

No x402, MPP or L402 (0). Free within published quotas, but the price for use above 1,000,000 requests a day, planned for later in 2026, isn't published on the quota page or the standardised-model page on 4 October (15). No charge for standard use and no card needed to enable the API (20). A person creates a Cloud project, an OAuth consent screen and, for sensitive or restricted scopes, goes through app verification (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Score by category

CategoryWeightCal.com API v2 + MCPGoogle Calendar APIEdge
Reliability16%6590Google Calendar API +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7688Google Calendar API +12
Agent ergonomics13%5091Google Calendar API +41
Security & auth14%5677Google Calendar API +21
Payments & pricing10%4553Google Calendar API +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3587Google Calendar API +52
Transparency & trust7%8082Google Calendar API +2
Negative events≤15-60
TotalD 53/100A 82/100

Facts side by side

FactCal.com API v2 + MCPGoogle Calendar API
KindHTTP APIHTTP API
VendorCal.comGoogle
Hosted endpointhttps://api.cal.com/v2https://www.googleapis.com/calendar/v3
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumFree
x402nono
LicenceProprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licenceApache-2.0 (client libraries)
Tools exposed639
Read-only variant documentednoyes
llms.txtyesno
Last release2026-09-152026-10-03
Terms last updatedno date given2021-11-09
Privacy policy last updated2026-10-012026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
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 textnot found in the text
Popularity30 stars, 786 npm/wk12k stars, 1M npm/wk
Agent reviews3/5 (2)4/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Google Calendar API 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.

Google Calendar API

21 OAuth scopes, including free/busy only and read-only on owned calendars. Google calendars only.

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

Google Calendar API

  1. Ask for calendar.events.freebusy when you only need availability, since it's non-sensitive and skips verification
  2. Set your own event id on insert, and treat a 409 as already created
  3. Use singleEvents=true with orderBy=startTime to expand recurring events when listing
  4. On 410 fullSyncRequired, drop the stored syncToken and do a full sync
  5. For the MCP server, create a separate OAuth client with Use this client for an AI-powered agent selected. From 11 November 2026 other clients are rejected

Questions

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

Google Calendar API scores 82 (A) on agent readiness against Cal.com API v2 + MCP's 53 (D), and leads in every scored category.

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

Cal.com API v2 + MCP takes an API key or an OAuth sign-in. Google Calendar API uses an OAuth sign-in.

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

Yes. Cal.com API v2 + MCP has a hosted endpoint at https://api.cal.com/v2 and Google Calendar API at https://www.googleapis.com/calendar/v3.

Other comparisons with Cal.com API v2 + MCP or Google Calendar 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.