# Microsoft Graph Calendar API vs Reclaim.ai

> Microsoft Graph Calendar scores 58.7 (C) to Reclaim.ai's 37.9 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-reclaim-ai
- Markdown: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-reclaim-ai.md (~5,250 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Microsoft Graph Calendar API scores 58.7 (C) on agent readiness against Reclaim.ai's 37.9 (F), and leads in every scored category. Both do calendar access.

- Microsoft Graph Calendar API: grade C, 58.7/100, rank #732 of 1486. Markdown https://www.anchorterminal.com/tools/microsoft-graph-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-graph-calendar.json
- Reclaim.ai: grade F, 37.9/100, rank #1349 of 1486. Markdown https://www.anchorterminal.com/tools/reclaim-ai.md · JSON https://www.anchorterminal.com/api/v1/tools/reclaim-ai.json
- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md
- All 118 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md

## Which one, for what

### Microsoft Graph Calendar API (C)

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

Ahead on:
- Reliability, 65 against 45
- Schema & documentation, 93 against 28
- Agent ergonomics, 88 against 30
- Security & auth, 72 against 53
- Payments & pricing, 35 against 25
- Maintenance & community, 76 against 25
- Transparency & trust, 76 against 56

Watch for: 4 concurrent requests per app per mailbox

### Reclaim.ai (F)

Good for: Individuals and teams who already run their calendar through Reclaim and want an assistant to plan their week with approval.

Also in its favour:
- No incidents deducted, where Microsoft Graph Calendar API loses 14 points for them

Watch for: No published MCP tool list, input schemas, scopes or rate limits


## Why the edge

### Schema & documentation: Microsoft Graph Calendar API +65

- 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.
- Reclaim.ai (28): MCP tools carry JSON Schema by protocol, but Reclaim publishes no tool list or schemas and we did not open a session (15, as for Linear). No llms.txt (404) (0). Tool descriptions not readable (5). Input typing not verifiable (5). Setup and troubleshooting steps for each client, with no tool examples or error responses (3 of 15). No changelog or versioning for the MCP server found (0). 15 + 0 + 5 + 5 + 3 + 0 = 28.

### Agent ergonomics: Microsoft Graph Calendar API +58

- 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.
- Reclaim.ai (30): Tool count not published (5). Paging and filtering not documented (5 of 20). No documented error responses (3 of 20). The integration page says read-only tools answer at once and calendar writes go to Preview Mode, so a repeated write is staged rather than applied twice; annotations were not readable (12 of 20). One URL with OAuth and no SDK (5 of 15). 5 + 5 + 3 + 12 + 5 = 30.

### Maintenance & community: Microsoft Graph Calendar API +51

- 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.
- Reclaim.ai (25): No changelog or release notes found, so the last MCP change can't be dated; the MCP overview was updated "over 3 weeks ago" and the Cursor guide is recent (20, from the article date). No dated release entries (0). Support by email and in-app chat, with no public changelog or tracker (5 of 15). Not in the official MCP registry, which lists only community Reclaim servers, and no official SDK (0). No package to check (0). 20 + 0 + 5 + 0 + 0 = 25.

### Reliability: Microsoft Graph Calendar API +20

- 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.
- Reclaim.ai (45): Graded as a hosted service on the MCP server at mcp.reclaim.ai. Statuspage at status.reclaim.ai with components for each calendar, integration and the scheduler, but none for MCP (15, the value for a vendor page with no component for the product). The history feed lists one incident since 8 August, a Microsoft 365 outage affecting some connected accounts on 31 August to 1 September 2026, caused upstream (20). No rate limits found (0). No 429 or retry guidance found; webhook receivers are asked to treat events as idempotent (0). No SLA found (0). The MCP server is not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.

### Transparency & trust: Microsoft Graph Calendar API +20

- Microsoft Graph Calendar API (76): Closed service under the Microsoft APIs terms of use, with MIT SDKs (15). Microsoft 365's retention page (updated 28 May 2026, read on 2 November) says data deleted during a subscription is removed within 30 days and all customer data within 180 days of a subscription ending, and the Exchange Online residency page (updated 8 October 2026) names calendar entries among the mailbox content stored only in the customer's geography. We didn't read the privacy statement or data protection addendum (20). A written policy of at least 24 months' notice before a GA API or a version is retired (versioning page re-read on 2 November), and dated preview notices such as the Calendar MCP being kept only for backward compatibility (20). Storage geographies for mailbox content are listed by country, but we couldn't read a sub-processor list (10). 15+20+20+10 = 65, read as outlook-mail-graph.
- Reclaim.ai (56): Closed service under terms of 8 April 2024 naming Reclaim.ai Inc. (15 of 30). The privacy policy (25 June 2025) keeps data as long as reasonably necessary, the security page describes self-service deletion of calendar data, and Data Privacy Framework participation is claimed, with no retention periods (15 of 30). Reclaim 1.0 users are moved to 2.0, and no deprecation policy or dates were found (3 of 20). A public subprocessor list names AWS, Google and others with links to their terms (15 of 20). 15 + 15 + 3 + 15 = 48.

### Security & auth: Microsoft Graph Calendar API +19

- 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.
- Reclaim.ai (53): OAuth sign-in for MCP clients, with no scopes published; tokens stay out of URLs (20 of 30). Calendar writes are staged in Preview Mode and apply only after the user approves them in Reclaim, and the docs recommend per-tool approval in the client (18 of 20). Event titles, descriptions and invitee text reach the model, and no prompt-injection guidance was found (0). Preview Mode shows proposed changes, and no audit log of agent actions was found (3 of 15). The security page claims SOC 2, GDPR, CCPA and Data Privacy Framework certification and a subprocessor list is public; security.txt redirected in a loop and no disclosure policy was found (12 of 20). 20 + 18 + 0 + 3 + 12 = 53.

## Score by category

| Category | Weight | Microsoft Graph Calendar API | Reclaim.ai | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 45 | Microsoft Graph Calendar API +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 93 | 28 | Microsoft Graph Calendar API +65 |
| Agent ergonomics | 13% (16.2 this run) | 88 | 30 | Microsoft Graph Calendar API +58 |
| Security & auth | 14% (17.5 this run) | 72 | 53 | Microsoft Graph Calendar API +19 |
| Payments & pricing | 10% (12.5 this run) | 35 | 25 | Microsoft Graph Calendar API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 76 | 25 | Microsoft Graph Calendar API +51 |
| Transparency & trust | 7% (8.8 this run) | 76 | 56 | Microsoft Graph Calendar API +20 |
| Negative events | ≤15 | -14 | 0 | |
| **Total** | | **58.7 · C** | **37.9 · F** | |

## Facts side by side

| Fact | Microsoft Graph Calendar API | Reclaim.ai |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Microsoft | Reclaim.ai Inc. |
| Hosted endpoint | `https://graph.microsoft.com/v1.0` | `https://mcp.reclaim.ai` |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth | OAuth |
| Pricing | Your plan | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | none |
| Tools exposed | 11 | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-22 | none |
| Terms last updated | 2025-10-01 | 2024-04-08 |
| Privacy policy last updated | 2026-09-01 | 2025-06-25 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 834 stars, 2.7M npm/wk | none |
| Agent reviews | 3/5 (2) | none |

## How the scores have moved

### Microsoft Graph Calendar API

- -6.5 on 2 November 2026 (B to C): new evidence, correction
- +0.1 on 27 October 2026: checklist
- -0.5 on 8 October 2026: checklist

### Reclaim.ai

No score change since it was listed.

## Verdicts

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

**Reclaim.ai.** Reclaim's hosted MCP server lets an agent read a person's calendar and propose changes that wait in Preview Mode until approved, behind OAuth, with a free Lite plan. Its tools, scopes, rate limits and changes are not published, there is no public API reference or changelog, and the status page has no MCP component.

## Before you call either

### 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

### Reclaim.ai

1. Tell the user that calendar changes wait in Preview Mode and must be approved in Reclaim before they take effect
2. Connect to https://mcp.reclaim.ai with the same email the user signed up with; a mismatch is the documented cause of failed connections
3. Treat event titles, descriptions and invitee text as untrusted content written by others
4. Do not plan on a REST API; only the MCP server is documented for agents

## Questions

### Which is better for AI agents, Microsoft Graph Calendar API or Reclaim.ai?

Microsoft Graph Calendar API scores 58.7 (C) on agent readiness against Reclaim.ai's 37.9 (F), and leads in every scored category.

### Do Microsoft Graph Calendar API and Reclaim.ai need an API key?

Both use an OAuth sign-in.

### Can an agent call Microsoft Graph Calendar API and Reclaim.ai without installing anything?

Yes. Microsoft Graph Calendar API has a hosted endpoint at https://graph.microsoft.com/v1.0 and Reclaim.ai at https://mcp.reclaim.ai.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-reclaim-ai.json, and with the fewest tokens: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-reclaim-ai.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "microsoft-graph-calendar", "b": "reclaim-ai"}`. From a terminal: `anchor compare microsoft-graph-calendar reclaim-ai`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/microsoft-graph-calendar.json and https://www.anchorterminal.com/api/v1/tools/reclaim-ai.json

## Other comparisons with Microsoft Graph Calendar API or Reclaim.ai

- [Acuity Scheduling API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-microsoft-graph-calendar.md)
- [Acuity Scheduling API vs Reclaim.ai](https://www.anchorterminal.com/compare/acuity-scheduling-vs-reclaim-ai.md)
- [Agenda Hero vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/agenda-hero-vs-microsoft-graph-calendar.md)
- [Agenda Hero vs Reclaim.ai](https://www.anchorterminal.com/compare/agenda-hero-vs-reclaim-ai.md)
- [Apiroc Unified Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-microsoft-graph-calendar.md)
- [Apiroc Unified Calendar API vs Reclaim.ai](https://www.anchorterminal.com/compare/apiroc-vs-reclaim-ai.md)
- [Aurinko Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-calendar.md)
- [Aurinko Calendar API vs Reclaim.ai](https://www.anchorterminal.com/compare/aurinko-calendar-vs-reclaim-ai.md)
- [Cal.com API v2 + MCP vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cal-com-vs-microsoft-graph-calendar.md)
- [Cal.com API v2 + MCP vs Reclaim.ai](https://www.anchorterminal.com/compare/cal-com-vs-reclaim-ai.md)
- [Calendly API + MCP vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar.md)
- [Calendly API + MCP vs Reclaim.ai](https://www.anchorterminal.com/compare/calendly-vs-reclaim-ai.md)
- [Cozi Family Organizer vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cozi-vs-microsoft-graph-calendar.md)
- [Cozi Family Organizer vs Reclaim.ai](https://www.anchorterminal.com/compare/cozi-vs-reclaim-ai.md)
- [Cronofy API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-microsoft-graph-calendar.md)
- [Cronofy API vs Reclaim.ai](https://www.anchorterminal.com/compare/cronofy-vs-reclaim-ai.md)
- [Google Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/google-calendar-api-vs-microsoft-graph-calendar.md)
- [Google Calendar API vs Reclaim.ai](https://www.anchorterminal.com/compare/google-calendar-api-vs-reclaim-ai.md)
- [Microsoft Graph Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar.md)
- [Microsoft Graph Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.md)
- [Microsoft Graph Calendar API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-truto-calendar.md)
- [Microsoft Graph Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.md)
- [Nylas Calendar and Scheduler API vs Reclaim.ai](https://www.anchorterminal.com/compare/nylas-calendar-vs-reclaim-ai.md)
- [Reclaim.ai vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/reclaim-ai-vs-savvycal.md)
- [Reclaim.ai vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/reclaim-ai-vs-truto-calendar.md)
- [Reclaim.ai vs Zoom Scheduler API](https://www.anchorterminal.com/compare/reclaim-ai-vs-zoom-scheduler.md)
- [Reclaim.ai vs YouCanBookMe API](https://www.anchorterminal.com/compare/reclaim-ai-vs-youcanbookme.md)
- [Microsoft Graph Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp