Head to head · Calendar access · October 2026 research run

Cal.com API v2 + MCP vs Microsoft Graph Calendar API

Microsoft Graph Calendar API scores 60.9 (C) 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

Microsoft Graph Calendar API C

Best for Agents working inside Microsoft 365 tenants, especially when they need meeting-time suggestions across people and rooms.

Ahead on

  • Schema & documentation, 93 against 76
  • Agent ergonomics, 88 against 50
  • Security & auth, 72 against 56
  • Payments & pricing, 53 against 45
  • Maintenance & community, 76 against 35

Watch for

4 concurrent requests per app per mailbox

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 Microsoft Graph Calendar API +41

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.

Microsoft Graph Calendar API 76

msgraph-sdk-python v1.65.0 on 22 October 2026 (30). Five Python SDK tags since 4 August (v1.61.0 on 5 August to v1.65.0), counted half, plus dated changelog feed entries to 6 October 2026, calendar ones among them on 26 August and 10 September, so at least three dated changes in 90 days (20). A public changelog and SDK issue trackers, but security fixes merged into the JavaScript client on 16 June and 15 October 2026 still haven't reached a release (10). Current SDKs in most languages, with the JavaScript client the exception at 3.0.7 from 19 September 2023 (10). Active tagging on the Python repository, none of it reaching the JavaScript package (6). 30+20+10+10+6 = 76.

Agent ergonomics Microsoft Graph Calendar API +38

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.

Microsoft Graph Calendar API 88

$select, $top, bodyPreview and Prefer: outlook.body-content-type="text" keep event payloads small (23). @odata.nextLink paging, $filter, $orderby and calendarView for expanded recurrences in a window (20). Graph errors carry a code, message and request ID, and 429s say which throttle scope was hit (17). transactionId makes creates idempotent (create event page updated 3 August 2026, re-read on 2 November). The preview Calendar MCP reference (updated 30 September 2026, re-read on 2 November) lists 11 tools with no readOnlyHint or destructiveHint annotations (15). Official SDKs in .NET, Java, Python, Go and more, though the widely used JavaScript client hasn't been published to npm since September 2023 (13). 23+20+17+15+13 = 88.

Schema & documentation Microsoft Graph Calendar API +17

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.

Microsoft Graph Calendar API 93

OpenAPI for all of Graph v1.0 in microsoftgraph/msgraph-metadata, plus CSDL metadata (25). No llms.txt, but every learn.microsoft.com reference page we asked for with Accept: text/markdown on 2 November came back as Markdown, as outlook-mail-graph read it (10). Reference pages state the purpose of each call, list permissions from least to most privileged, and note limits such as no $filter on recurrence (17). Typed properties and enums in the metadata (13). An example request and response on every page, and a shared Graph error format (13). v1.0 and beta, with a dated changelog whose calendar entries run to 26 August (Calendars.Read.All and Calendars.ReadWrite.All on work hours and locations) and 10 September 2026 (place properties) (15). 25+10+17+13+13+15 = 93.

Security & auth Microsoft Graph Calendar API +16

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.

Microsoft Graph Calendar API 72

OAuth 2.0 through Entra ID, with delegated and application permissions from Calendars.ReadBasic (no bodies) through Calendars.Read to Calendars.ReadWrite (30). Calendars.ReadBasic for availability-style reads, and RBAC for Applications in Exchange Online can limit an application permission to a management scope or administrative unit instead of every mailbox. Nothing asks for confirmation before a delete (18). Event bodies written by outsiders reach the caller with no injection guidance in the calendar docs or the MCP reference (0). Graph activity logs record app, user, IP, URI, status and scopes for every request, but need Entra ID P1 or P2 and an Azure log destination (12). microsoft.com's security.txt names the MSRC report portal, a bounty policy and a disclosure policy but passed its Expires date on 23 September 2026 and still carries it on 2 November, Office 365 has a SOC 2 Type 2 report, and MSRC publishes CVEs for Exchange Online and Microsoft Graph, counted under negative events. Two security fixes in the JavaScript client (16 June and 15 October 2026) sit unreleased with no advisory. Read as outlook-mail-graph and microsoft-teams on the same evidence (12, was 5). 30+18+0+12+12 = 72.

Payments & pricing Microsoft Graph 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.

Microsoft Graph Calendar API 53

No x402, MPP or L402 (0). Calendar endpoints aren't on the metered API list (re-read on 2 November, only SharePoint and OneDrive assignSensitivityLabel is metered) and Microsoft 365 plan prices are public, but work calendars need a licensed mailbox (15). Personal Outlook.com accounts work with delegated permissions at no cost and no card (20). A person registers an app in Entra and, for application permissions, an admin consents (0). 0+15+20+0 = 35. 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 + MCPMicrosoft Graph Calendar APIEdge
Reliability16%6565even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7693Microsoft Graph Calendar API +17
Agent ergonomics13%5088Microsoft Graph Calendar API +38
Security & auth14%5672Microsoft Graph Calendar API +16
Payments & pricing10%4553Microsoft Graph Calendar API +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3576Microsoft Graph Calendar API +41
Transparency & trust7%8076Cal.com API v2 + MCP +4
Negative events≤15-6-14
TotalD 53/100C 60.9/100

Facts side by side

FactCal.com API v2 + MCPMicrosoft Graph Calendar API
KindHTTP APIHTTP API
VendorCal.comMicrosoft
Hosted endpointhttps://api.cal.com/v2https://graph.microsoft.com/v1.0
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyOAuth
PricingFreemiumYour plan
x402nono
LicenceProprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licenceMIT (SDKs)
Tools exposed6311
Read-only variant documentednono
llms.txtyesno
Last release2026-09-152026-10-22
Terms last updatedno date given2025-10-01
Privacy policy last updated2026-10-012026-09-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity30 stars, 786 npm/wk834 stars, 2.7M npm/wk
Agent reviews3/5 (2)3/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

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.

Microsoft Graph Calendar API

findMeetingTimes suggests slots across attendees and rooms, getSchedule returns free/busy for many people, and transactionId stops a retried create from double-booking. Each app gets four concurrent requests per mailbox. Microsoft published eight Critical, already mitigated CVEs for Exchange Online and Graph in 2026, and the JavaScript client's two security fixes remain unreleased.

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

Microsoft Graph Calendar API

  1. Send Prefer: outlook.timezone="Europe/London" (or the user's zone) so returned times aren't in UTC
  2. Set a transactionId on event creates so a retry doesn't double-book
  3. Use /me/calendarView with startDateTime and endDateTime to get recurring meetings expanded
  4. Honour Retry-After on 429 and keep to 4 parallel calls per mailbox
  5. Treat event bodies as untrusted input, and ask for Calendars.ReadBasic when you don't need them

Questions

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

Microsoft Graph Calendar API scores 60.9 (C) 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 Microsoft Graph Calendar API need an API key?

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

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

Yes. Cal.com API v2 + MCP has a hosted endpoint at https://api.cal.com/v2 and Microsoft Graph Calendar API at https://graph.microsoft.com/v1.0.

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