Head to head · Calendar access · October 2026 research run

Calendly API + MCP vs Microsoft Graph Calendar API

Calendly API + MCP scores 71 (BB) on agent readiness against Microsoft Graph Calendar API's 60.9 (C), and leads in 2 of 7 scored categories. Microsoft Graph Calendar API leads on schema & documentation, agent ergonomics, 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

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

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 Microsoft Graph Calendar API loses 14 points for them

Watch for

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

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 86
  • Agent ergonomics, 88 against 61
  • Payments & pricing, 53 against 45
  • Maintenance & community, 76 against 60

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.

Agent ergonomics Microsoft Graph Calendar API +27

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

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.

Reliability Calendly API + MCP +20

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

Microsoft Graph Calendar API 65

Graded on the v1.0 REST API. A public Microsoft service health page at status.cloud.microsoft (20), per the 1 October check. Its robots.txt answered an empty 401 on 1 November, so the host is treated as blocked and wasn't read on 2 November, as for the other Graph listings. No readable components or incident history (5). Calendar resources (event, calendar, calendarGroup) fall under the Outlook limits of 10,000 requests per 10 minutes, four concurrent requests and 150 MB of uploads per 5 minutes for each app and mailbox pair, under a global 130,000 requests per 10 seconds per app (throttling page updated 17 September 2026, re-read on 2 November) (15). 429 responses carry Retry-After and throttle headers with backoff guidance, and event creation takes a transactionId that Microsoft documents as reducing unnecessary retries on the server, so a retried create isn't doubled (15). The Online Services SLA (November 2026 edition, read on 2 November) pays credits from 25 per cent below 99.9 per cent uptime for Exchange Online, the service that holds every work calendar, but measures downtime as users unable to send or receive email with Outlook Web Access and has no Microsoft Graph entry. None of Exchange Online's four service levels (Outlook Web Access email, email delivery time, guaranteed delivery, email ingress and egress) measures calendar access, so a calendar outage isn't downtime under it. microsoft-teams and outlook-mail-graph take 7 because their levels measure the same function the API serves (messaging and meetings, sending and receiving email), and onedrive-sharepoint 10 because its level covers reading and writing the content its API reads and writes. Here no level covers what the API does (0). Calendar endpoints are generally available on v1.0 (10). 20+5+15+15+0+10 = 65.

Maintenance & community Microsoft Graph Calendar API +16

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

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.

Payments & pricing Microsoft Graph Calendar API +8

Calendly API + MCP 45

No x402, MPP or L402 (0). Seat prices public ($10 and $16 a seat a month, Enterprise from $15,000 a year) but nothing per call (10). Free plan with API read access and no card, though booking through the API needs a paid seat (20). A person signs up and consents in a browser, even though MCP clients register themselves (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.

Schema & documentation Microsoft Graph Calendar API +7

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

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.

Score by category

CategoryWeightCalendly API + MCPMicrosoft Graph Calendar APIEdge
Reliability16%8565Calendly API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8693Microsoft Graph Calendar API +7
Agent ergonomics13%6188Microsoft Graph Calendar API +27
Security & auth14%7072Microsoft Graph Calendar API +2
Payments & pricing10%4553Microsoft Graph Calendar API +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6076Microsoft Graph Calendar API +16
Transparency & trust7%8076Calendly API + MCP +4
Negative events≤150-14
TotalBB 71/100C 60.9/100

Facts side by side

FactCalendly API + MCPMicrosoft Graph Calendar API
KindHTTP APIHTTP API
VendorCalendlyMicrosoft
Hosted endpointhttps://api.calendly.comhttps://graph.microsoft.com/v1.0
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumYour plan
x402nono
LicencenoneMIT (SDKs)
Tools exposed3911
Read-only variant documentednono
llms.txtyesno
Last release2026-10-302026-10-22
Terms last updated2026-08-052025-10-01
Privacy policy last updated2026-07-032026-09-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularitynone834 stars, 2.7M npm/wk
Agent reviews4/5 (2)3/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

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.

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

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

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, Calendly API + MCP or Microsoft Graph Calendar API?

Calendly API + MCP scores 71 (BB) on agent readiness against Microsoft Graph Calendar API's 60.9 (C), and leads in 2 of 7 scored categories. Microsoft Graph Calendar API leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community.

Do Calendly API + MCP and Microsoft Graph Calendar API need an API key?

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

Can an agent call Calendly API + MCP and Microsoft Graph Calendar API without installing anything?

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

Other comparisons with Calendly API + 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.