# Nylas Calendar and Scheduler API vs Reclaim.ai (slim)

> Nylas Calendar and Scheduler scores 75.5 (BB) to Reclaim.ai's 37.9 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/nylas-calendar-vs-reclaim-ai.md (~5,100 tokens) · this version ~2,980 tokens · JSON https://www.anchorterminal.com/compare/nylas-calendar-vs-reclaim-ai.json · canonical https://www.anchorterminal.com/compare/nylas-calendar-vs-reclaim-ai
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against Reclaim.ai's 37.9 (F), and leads in every scored category. Both do calendar access.

- Nylas Calendar and Scheduler API: BB 75.5, rank #60 of 1486 · https://www.anchorterminal.com/tools/nylas-calendar.min.md
- Reclaim.ai: F 37.9, rank #1349 of 1486 · https://www.anchorterminal.com/tools/reclaim-ai.min.md
- Nylas Calendar and Scheduler API, good for Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards. Ahead on Reliability, 72 against 45; Schema & documentation, 91 against 28; Agent ergonomics, 71 against 30; Security & auth, 85 against 53; Payments & pricing, 40 against 25; Maintenance & community, 88 against 25; Transparency & trust, 82 against 56. Also Agent-ready, a grade of BB or better; Free to start without a card.
- Reclaim.ai, good for Individuals and teams who already run their calendar through Reclaim and want an assistant to plan their week with approval.

| Category | Nylas Calendar and Scheduler API | Reclaim.ai |
| --- | --- | --- |
| Reliability (16%) | 72 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 91 | 28 |
| Agent ergonomics (13%) | 71 | 30 |
| Security & auth (14%) | 85 | 53 |
| Payments & pricing (10%) | 40 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 88 | 25 |
| Transparency & trust (7%) | 82 | 56 |

| Fact (where they differ) | Nylas Calendar and Scheduler API | Reclaim.ai |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Nylas | Reclaim.ai Inc. |
| Hosted endpoint | `https://api.us.nylas.com/v3` | `https://mcp.reclaim.ai` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Licence | MIT (SDKs) | none |
| Tools exposed | 38 | none |
| llms.txt | yes | no |
| Last release | 2026-10-30 | none |
| Terms last updated | 2025-06-23 | 2024-04-08 |
| Privacy policy last updated | 2026-01-06 | 2025-06-25 |
| Popularity | 181 stars, 281k npm/wk, 104k PyPI/wk | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Schema & documentation, Nylas Calendar and Scheduler API +63: Nylas Calendar and Scheduler API 91 (OpenAPI 3.1 file at developer.nylas.com/openapi.json with 140 paths and 244 operations on 1 November, 20 of the paths and 34 operations for calendars, events, availability and scheduling (25). llms.txt and Markdown docs (10). Guides say when to use each API, and the MCP page lists each tool with a one-line purpose and no when-not-to guidance (15). Typed parameters in the reference (12). An errors page with a JSON shape (`type`, `message`, `provider_error`, `request_id`) and a retry yes or no for each status code (14). v3 in the path and a dated changelog with 20 entries between 15 September and 30 October 2026 (15). 25+10+15+12+14+15 = 91.); 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.)
- Maintenance & community, Nylas Calendar and Scheduler API +63: Nylas Calendar and Scheduler API 88 (Changelog entries up to 30 October 2026, the last calendar-specific one on 22 October with event webhook, recurring cancellation and Microsoft availability fixes (30). 20 dated changelog entries between 15 September and 30 October (20). Public dated changelog, open SDK repositories with commits to 30 September (Python) and 13 October (Node), and support (15). Current official SDKs (15). nylas-python v6.18.0 on 30 September 2026. The Node SDK's package.json is still 8.4.0 (24 June 2026) with unreleased commits on main to 13 October (8). 30+20+15+15+8 = 88.); 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, Nylas Calendar and Scheduler API +41: Nylas Calendar and Scheduler API 71 (38 MCP tools with no toolsets found on 1 November (5), plus 5 for `limit` and `select` field selection on the REST API (10). Page tokens and time filters on event lists (18). Typed errors with a request ID and a provider error passed through, and a retry table (18). The MCP needs a confirmation call before sending mail, but event create, update and delete need none, event writes have no idempotency key and we found no tool annotations (10). Official SDKs in Node, Python and more (15). 10+18+18+10+15 = 71.); 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.)
- Security & auth, Nylas Calendar and Scheduler API +32: Nylas Calendar and Scheduler API 85 (Nylas IAM, launched 6 October 2026, issues API keys bound to one grant, workspace, application or organisation with roles and permissions. Every new IAM key expires, keys can be disabled or rotated, and the IAM guide (re-read 1 November) shows principals and credentials created and rotated through a public /v3/iam API once a first management key is made in the Dashboard. End users connect through OAuth with scopes the app picks. Application keys still reach every grant, so 1 is held back as for nylas-email, and 1 more because the IAM pages name no calendar permission, as nylas-notetaker holds back for Notetaker (28). A principal can be bound to one grant with read permissions, the agent security page shows a scheduling agent limited to reading calendars and creating events, and anything outside the binding answers 403. The MCP confirmation step covers email sends only, so creating, updating or deleting an event needs no confirmation. 3 below nylas-email's 17, which has the send confirmation (14). The MCP and agent security docs say event descriptions and locations can carry hidden instructions and tell agents to treat calendar content as untrusted (13). IAM Access Activity records allowed and denied API, authentication and MCP requests for 400 days with links to request logs, and Dashboard logs are kept 14 days. Requests made with an application key appear only in the logs (13). SOC 2 Type II, ISO 27001 and 27701, CSA STAR, an annual penetration test and a private bug bounty with security@nylas.com, per the 1 October check, and an RFC 9116 security.txt on developer.nylas.com valid to 1 August 2027. www.nylas.com still has none. nylas-email scores this 17 (17). 28+14+13+13+17 = 85.); 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.)
- Reliability, Nylas Calendar and Scheduler API +27: Nylas Calendar and Scheduler API 72 (Atlassian Statuspage at status-v3.nylas.com with US and EU components (20). In the 90 days from 3 August the history feed names no calendar incident. Incidents hit IMAP message reads (6 August), US message sync latency (11 August), EWS attachments (14 August), Microsoft send and read through Exchange Online (31 August to 1 September), Notetaker Teams joins (4 September), IMAP retrieval (10 September), IMAP sync (17 September) and Microsoft 365 sign-in for Sandbox applications on shared credentials (from 22 October), each limited to one provider, product or non-production surface, so partial. The exception is 19 August, delayed or missing webhooks for all providers in the US and EU from 09:11 to 14:34 PDT, mitigated by recovering the sync state of affected grants. Calendar event webhooks come from the same provider grant sync, so it counts here as one major, as for nylas-email (10). 200 requests a second per grant for calendar and 50 a second per application for grant, auth and webhook endpoints, plus the provider limits behind them, re-read on 1 November (15). 429s separate Nylas limits from provider limits and pass on the provider's Retry-After, Google's included since 22 October, and the errors page says which codes to retry with exponential backoff. Idempotency keys cover email send only, not event writes (10). The pricing page lists a 99.99 per cent availability SLA for annual Enterprise contracts, with terms in the customer agreement, which nylas-email scores 7 (7). GA (10). 20+10+15+10+7+10 = 72.); 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, Nylas Calendar and Scheduler API +26: Nylas Calendar and Scheduler API 82 (Closed service under Californian law, with MIT SDKs (15). The privacy policy keeps customer data for the life of the account plus two months and lets EEA customers pick UK or US data centres, per the 1 October check and as nylas-email read it on 1 November. A sub-processor page dated 28 August 2026, with changes announced on the status page (24). v2 deprecation documented and a dated changelog, but no deprecation policy found. The 10 October changelog capped availability ranges at 732 days on the day it took effect (10). Sub-processors listed, AWS and GCP named as hosts, US and EU regions (18). 15+24+10+18 = 67.); 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.)