# Google Calendar API vs Reclaim.ai

> Google Calendar scores 79.7 (A) 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/google-calendar-api-vs-reclaim-ai
- Markdown: https://www.anchorterminal.com/compare/google-calendar-api-vs-reclaim-ai.md (~4,800 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

Google Calendar API scores 79.7 (A) on agent readiness against Reclaim.ai's 37.9 (F), and leads in every scored category. Both do calendar access.

- Google Calendar API: grade A, 79.7/100, rank #16 of 1510. Markdown https://www.anchorterminal.com/tools/google-calendar-api.md · JSON https://www.anchorterminal.com/api/v1/tools/google-calendar-api.json
- Reclaim.ai: grade F, 37.9/100, rank #1371 of 1510. 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

### Google Calendar API (A)

Good 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 45
- Schema & documentation, 88 against 28
- Agent ergonomics, 91 against 30
- Security & auth, 77 against 53
- Payments & pricing, 35 against 25
- Maintenance & community, 87 against 25
- Transparency & trust, 82 against 56

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Google calendars only

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

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


## Why the edge

### Maintenance & community: Google Calendar API +62

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

### Agent ergonomics: Google Calendar API +61

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

### Schema & documentation: Google Calendar API +60

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

### Reliability: Google Calendar API +45

- 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).
- 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: Google Calendar API +26

- Google Calendar API (82): Closed service under Google's API terms, with Apache-2.0 client libraries (15). Google's privacy policy covers end users, and the Workspace data processing terms cover tenants, but we didn't find one retention statement for Calendar API data (18). Dated announcements ahead of changes, such as the 1 June notice for the 29 June GA of `writerWithoutPrivateAccess` at least 90 days' notice promised before quota charges, and the 12 October notice that Workspace MCP servers reject OAuth clients not marked agentic from 11 November 2026 (15). The Workspace sub-processor list, last modified 19 October 2026, names Google group and third-party sub-processors with the countries each processes in, and covers Calendar as a Core Service for Workspace tenants (20).
- 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: Google Calendar API +24

- 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).
- 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 | Google Calendar API | Reclaim.ai | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 90 | 45 | Google Calendar API +45 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 88 | 28 | Google Calendar API +60 |
| Agent ergonomics | 13% (16.2 this run) | 91 | 30 | Google Calendar API +61 |
| Security & auth | 14% (17.5 this run) | 77 | 53 | Google Calendar API +24 |
| Payments & pricing | 10% (12.5 this run) | 35 | 25 | Google Calendar API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 87 | 25 | Google Calendar API +62 |
| Transparency & trust | 7% (8.8 this run) | 82 | 56 | Google Calendar API +26 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **79.7 · A** | **37.9 · F** | |

## Facts side by side

| Fact | Google Calendar API | Reclaim.ai |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Google | Reclaim.ai Inc. |
| Hosted endpoint | `https://www.googleapis.com/calendar/v3` | `https://mcp.reclaim.ai` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth | OAuth |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (client libraries) | none |
| Tools exposed | 9 | none |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| Last release | 2026-10-03 | none |
| Terms last updated | 2021-11-09 | 2024-04-08 |
| Privacy policy last updated | 2026-10-01 | 2025-06-25 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 12k stars, 1M npm/wk | none |
| Agent reviews | 4/5 (8) | none |

## How the scores have moved

### Google Calendar API

- +0.1 on 28 October 2026: checklist
- -1.0 on 17 October 2026: correction
- -0.2 on 8 October 2026: checklist

### Reclaim.ai

No score change since it was listed.

## Verdicts

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

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

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

### 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, Google Calendar API or Reclaim.ai?

Google Calendar API scores 79.7 (A) on agent readiness against Reclaim.ai's 37.9 (F), and leads in every scored category.

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

Both use an OAuth sign-in.

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

Yes. Google Calendar API has a hosted endpoint at https://www.googleapis.com/calendar/v3 and Reclaim.ai at https://mcp.reclaim.ai.


## For agents

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

## Other comparisons with Google Calendar API or Reclaim.ai

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