Head to head · Calendar access · October 2026 research run

Apiroc Unified Calendar API vs Cal.com API v2 + MCP

Cal.com API v2 + MCP scores 53 (D) on agent readiness against Apiroc Unified Calendar API's 41.9 (E), and leads in 4 of 7 scored categories. Apiroc Unified Calendar API leads on payments & pricing and maintenance & community. Both do calendar access.

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

Which one, for what

Apiroc Unified Calendar API E

Best for A small product or an agent builder that needs read and write across Google, Microsoft and iCloud for tens to hundreds of accounts on a tight budget.

Ahead on

  • Payments & pricing, 60 against 45
  • Maintenance & community, 42 against 35

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Cal.com API v2 + MCP loses 6 points for them

Watch for

No status page history, changelog, OpenAPI spec, llms.txt or security.txt

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.

Ahead on

  • Reliability, 65 against 35
  • Schema & documentation, 76 against 44
  • Security & auth, 56 against 21
  • Transparency & trust, 80 against 51

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

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

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.

Security & auth Cal.com API v2 + MCP +35

Apiroc Unified Calendar API 21

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. Your application calls with one x-api-key that reaches every connected end-user account, and we found no key scopes or rotation docs (10). Per-provider scope selection in the dashboard lets an operator request read-only Google or Microsoft scopes, and production requires your own OAuth app. iCloud connects with an app-specific password, which can't be scoped, and nothing asks for confirmation on deletes (8). Event titles and descriptions from third parties reach the caller with no injection guidance (0). Every response carries a requestId and the privacy policy keeps application logs 30 days, but we found no operator-facing request log (3). No security.txt (per the 30 September check), no disclosure policy, bounty, SOC 2 or ISO 27001 found (0).

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.

Schema & documentation Cal.com API v2 + MCP +32

Apiroc Unified Calendar API 44

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No OpenAPI spec. A Postman collection is the only machine-readable contract (10). No llms.txt, per the 30 September check (0). Reference pages for five resources with parameters and cURL, TypeScript and Python examples, but little on when to use one endpoint over another (10). Typed inputs in the Node SDK and required fields marked in the docs (10). Examples throughout, and an errors page that gives only the shape (error, message, requestId) and the 2xx, 4xx and 5xx ranges, with no list of error names (9). /v1 in the path but no changelog (5).

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.

Reliability Cal.com API v2 + MCP +30

Apiroc Unified Calendar API 35

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No public status page with history. status.apiroc.com doesn't resolve and the homepage shows only an "All systems operational" badge with a claim of 34B+ API calls (0). No readable incident history (5). Rate limits published with numbers, 20 requests a second in Sandbox and 300 in Production per application, plus 600 a minute per Google account and 1,000 a minute per Microsoft account (15). The docs don't mention 429 or Retry-After, though the official Node SDK reads a retry-after header on 429, and webhook docs say to dedupe on svix-id (5). The terms say availability can't be guaranteed, and no SLA was found on any plan (0). GA, with production use licensed on Pro (10). The 429 line's 5 is an in-between value kept from 1 October (the SDK reads retry-after, the docs say nothing). 0 + 5 + 15 + 5 + 0 + 10 = 35.

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.

Transparency & trust Cal.com API v2 + MCP +29

Apiroc Unified Calendar API 51

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. Closed service with terms under Albanian law and an MIT Node SDK (15). Privacy policy (24 August 2026) says event content isn't stored persistently, application logs and analytics are kept 30 days, data isn't used to train models, and Google's Limited Use rules apply. A DPA is published. Webhooks are delivered through Svix, which isn't on the sub-processor list, and webhook message retention has no period (18). 30 days' notice for price rises and sub-processor changes, but no API deprecation policy (3). Five sub-processors listed with locations, and servers stated as US. Svix missing (15).

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.

Payments & pricing Apiroc Unified Calendar API +15

Apiroc Unified Calendar API 60

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No x402, MPP or L402 (0). Plan prices and $0.50 per extra end-user account a month published without login (20). Free plan for 10 end-user accounts with no card (20). Browser signup and a dashboard key, no autonomous route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Maintenance & community Apiroc Unified Calendar API +7

Apiroc Unified Calendar API 42

Node SDK v2.1.0, tagged on 8 October 2026 ("feat: add caldav support", connecting any CalDAV server), 33 days before this check (20). From 12 August only that one release; v1.2.2 (14 July) and v1.3.0, v2.0.0 and v2.0.1 (5 August) are now outside the 90 days, and no changelog or other dated source of Apiroc's could be read (0; was 20). No public changelog. Support by email, with priority support on Pro and a Slack channel on Enterprise, per the 1 October check (4). One current official SDK, in Node (10). CI typechecks, lints, builds and tests on pull requests, a tag-triggered workflow publishes to npm, and dependencies were last bumped in May 2026 (8). 20 + 0 + 4 + 10 + 8 = 42.

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.

Score by category

CategoryWeightApiroc Unified Calendar APICal.com API v2 + MCPEdge
Reliability16%3565Cal.com API v2 + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4476Cal.com API v2 + MCP +32
Agent ergonomics13%5250Apiroc Unified Calendar API +2
Security & auth14%2156Cal.com API v2 + MCP +35
Payments & pricing10%6045Apiroc Unified Calendar API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4235Apiroc Unified Calendar API +7
Transparency & trust7%5180Cal.com API v2 + MCP +29
Negative events≤150-6
TotalE 41.9/100D 53/100

Facts side by side

FactApiroc Unified Calendar APICal.com API v2 + MCP
KindHTTP APIHTTP API
VendorApirocCal.com
Hosted endpointhttps://api.apiroc.com/api/v1https://api.cal.com/v2
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (Node SDK)Proprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licence
Tools exposednone63
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-10-082026-09-15
Terms last updated2026-08-24no date given
Privacy policy last updated2026-08-242026-10-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone30 stars, 786 npm/wk
Agent reviews2/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Cal.com API v2 + 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

Apiroc Unified Calendar API

$0.50 per connected account a month after 50 on Pro, with unlimited requests, and Google, Outlook, iCloud and other CalDAV servers behind one schema. No status page history, changelog, OpenAPI spec, llms.txt or security.txt was found, and one application key reaches every connected account.

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.

Before you call either

Apiroc Unified Calendar API

  1. Send the key in the x-api-key header from a server, never a browser
  2. Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com
  3. On 429, wait for the retry-after header, since the docs don't describe backoff
  4. Pass back pageToken until it's absent, then keep the syncToken for the next incremental read
  5. Dedupe webhooks on svix-id, since Svix retries deliveries

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

Questions

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

Cal.com API v2 + MCP scores 53 (D) on agent readiness against Apiroc Unified Calendar API's 41.9 (E), and leads in 4 of 7 scored categories. Apiroc Unified Calendar API leads on payments & pricing and maintenance & community.

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

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

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

Yes. Apiroc Unified Calendar API has a hosted endpoint at https://api.apiroc.com/api/v1 and Cal.com API v2 + MCP at https://api.cal.com/v2.

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