Head to head · Calendar access · October 2026 research run
Cal.com API v2 + MCP vs Truto Unified Calendar API
Truto Unified Calendar API scores 60.4 (C) on agent readiness against Cal.com API v2 + MCP's 51.1 (D), and leads in 3 of 7 scored categories. Cal.com API v2 + MCP leads on payments & pricing and transparency & trust. Both do calendar access.
Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons
Which one, for what
Best for An agent that books, reschedules and cancels meetings into a Cal.com user's event types, or routes leads with routing forms.
Ahead on
- Payments & pricing, 30 against 20
- Transparency & trust, 80 against 61
Also in its favour
- A hosted endpoint, with nothing to install
- Runs on your own machine
Watch for
120 requests a minute by default and no documented 429 or retry behaviour
Best for Software companies that need their product's agent to read and book across customers' Google, Outlook, Cal.com and Calendly accounts.
Ahead on
- Reliability, 77 against 65
- Agent ergonomics, 71 against 50
- Maintenance & community, 50 against 35
Also in its favour
- No incidents deducted, where Cal.com API v2 + MCP loses 6 points for them
Watch for
Priced from $999 per connector a year with a demo-led sandbox
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 Truto Unified Calendar API +21
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.
Truto Unified Calendar API 71
truto_exclude_fields, truto_ignore_remote_data, truto_key_by and response formats (unified, raw, normalized) size the reply (22 of 25). Query operators such as [gt] and [in], sort_by, limit and cursors, with a meta endpoint that says which filters each vendor supports (18 of 20). Errors name the HTTP status and say whether Truto or the provider failed, with the provider's message extracted (18 of 20). No idempotency key found for creates (5 of 20). Every call needs only the token and integrated_account_id; a CLI and the Link SDK exist, with no general API SDK found (8 of 15). 22 + 18 + 18 + 5 + 8 = 71.
Transparency & trust Cal.com API v2 + MCP +19
Cal.com API v2 + MCP 80
Closed source since 14 April 2026. The Terms of Service were rewritten as version 2.0, effective 1 November 2026, naming Cal.com, Inc., a Delaware corporation, under Delaware law, and they say Cal.diy and Cal.com's other open-source releases are governed by their own licences (MIT for Cal.diy). Closed with clear terms (15, from 12). Privacy policy (20 August 2026) says nothing is used to train models, account data is kept while active with a 30-day export window after closure, and logs exclude personal data. DPA in the compliance portal (22). Platform deprecation dated 15 December 2025 and date-pinned API versions. The new terms promise prior notice by email or in product for updates that materially reduce a customer's rights, and name a periodic changelog for deprecations (14). Subprocessors are listed in the trust centre per the privacy policy, which we didn't open, and data sits in the US with EU residency on request (13). Privacy, DPA and trust readings are per the 1 October check, not re-read on 4 November. Total 64.
Truto Unified Calendar API 61
Closed service under terms naming Yin Yang Inc. (15 of 30). Truto says it stores no customer data and calls vendors live, logs are kept 30 or 90 days by plan, data is kept 15 days after termination, and a DPA is public (25 of 30). Deprecated admin endpoints are marked with no policy or dates (6 of 20). Enterprise customers can choose a data region and tokens can be stored regionally; no subprocessor list was found (8 of 20). 15 + 25 + 6 + 8 = 54.
Maintenance & community Truto Unified Calendar API +15
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.
Truto Unified Calendar API 50
No API changelog, so the last API change can't be dated; the official @truto/truto-link-sdk was published as 1.3.5 on 26 October 2026, which we take as the latest dated release (20 of 30, since it is the connection widget, not the calendar API). Six Link SDK versions since 8 August (10 of 20, for the same reason). Support through Slack on paid plans, with no public tracker (5 of 15). A CLI and the Link SDK are official, with no API client (10 of 15). Package health not checked (5 of 10). 20 + 10 + 5 + 10 + 5 = 50.
Reliability Truto Unified Calendar API +12
Cal.com API v2 + MCP 65
OpenStatus page at status.cal.com with App, Website and API components and an events log back to February 2024, per the 1 October reading (20). cal.com hosts are paused for this run under the terms of 1 November 2026, so the page wasn't re-read. In the readable part of the window, the 31 August outage (1 hour 14 minutes of HTTP 500s on /v2/slots and /v2/bookings, US East only) hit one region and two endpoints, and the 15 September event was a 1 hour 19 minute degradation of App and API. This run reads one region or a group of calls as partial, so both count as minor. 1 October to 4 November is unread and not credited (20, from 10). 120 requests a minute per key or OAuth token, raisable to 200 and then to 800 on request (15). No 429 behaviour, rate-limit headers or retry guidance in the docs or the OpenAPI spec (0). Enterprise lists "SLA guarantees" with no published figure or document, and a listed SLA nobody could read gives 0 in this run (0, from 5). API v2 is GA (10). Total 65.
Truto Unified Calendar API 77
Graded as a hosted service on the Unified Calendar API. Better Stack status page with components for api.truto.one health, ping and link-token endpoints and the static IP proxy, with incident history (20). The feed lists "APIs and Dashboard are down" on 29 October 2026 and delayed sync jobs and webhooks on 1 November, which counts as one major outage (10). Truto's own limit is 50 requests every 10 seconds per integrated account, in front of each vendor's (15). A vendor 429 comes back with Retry-After and normalised ratelimit-limit, -remaining and -reset headers, with no idempotency guidance for creates (12 of 15). The Enterprise plan lists an SLA guarantee (10). Generally available (10). 20 + 10 + 15 + 12 + 10 + 10 = 77.
Payments & pricing Cal.com API v2 + MCP +10
Cal.com API v2 + MCP 30
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).
Truto Unified Calendar API 20
No x402, MPP or L402 (0). Plan prices per connector a year are public, with unlimited calls (10). A free 30-day sandbox is given after a work-email request reviewed within a business day (10 of 20). A person requests access or books a demo (0). 0 + 10 + 10 + 0 = 20.
Score by category
| Category | Weight this run | Cal.com API v2 + MCP | Truto Unified Calendar API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 77 | Truto Unified Calendar API +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 76 | 75 | Cal.com API v2 + MCP +1 |
| Agent ergonomics | 13%16.2 | 50 | 71 | Truto Unified Calendar API +21 |
| Security & auth | 14%17.5 | 56 | 52 | Cal.com API v2 + MCP +4 |
| Payments & pricing | 10%12.5 | 30 | 20 | Cal.com API v2 + MCP +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 35 | 50 | Truto Unified Calendar API +15 |
| Transparency & trust | 7%8.8 | 80 | 61 | Cal.com API v2 + MCP +19 |
| Negative events | ≤15 | -6 | 0 | |
| Total | D 51.1/100 | C 60.4/100 |
Facts side by side
| Fact | Cal.com API v2 + MCP | Truto Unified Calendar API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cal.com | Yin Yang Inc. |
| Hosted endpoint | https://api.cal.com/v2 | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licence | none |
| Tools exposed | 63 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-15 | 2026-10-26 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | 2026-10-01 | 2024-10-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 30 stars, 786 npm/wk | none |
| Agent reviews | 3/5 (2) | none |
How the scores have moved
Truto Unified Calendar API
No score change since it was listed.
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.
Truto Unified Calendar API
Truto's calendar API is well documented for agents, with Markdown docs, field exclusion, normalised rate-limit headers and errors that name the failing side, across Google, Outlook, Cal.com and Calendly. It is sold from $999 a connector a year through a demo, had an API outage on 29 October 2026 and has no public changelog.
Before you call either
Cal.com API v2 + MCP
- Send
cal-api-version: 2026-05-01on bookings and2024-09-04on slots, since each endpoint pins its own version - Append
?toolsets=bookings,availabilityto the hosted MCP URL to skip the other 50-odd tools - Page bookings with
pagination.nextCursor, not offsets - Check for an existing booking before retrying a create, since there's no idempotency key
- Use
cal_test keys while building so bookings don't reach real calendars
Truto Unified Calendar API
- Pass
integrated_account_idon every call; the token alone reaches nothing - Call the meta endpoint for the method first to see which filters the vendor supports
- Set
truto_ignore_remote_data=trueand list fields intruto_exclude_fieldsto keep responses small - On 429 wait for Retry-After; stay under 50 requests every 10 seconds per integrated account
- Set
expand_recurring=truewhen the task needs each instance of a repeating event
Questions
Which is better for AI agents, Cal.com API v2 + MCP or Truto Unified Calendar API?
Truto Unified Calendar API scores 60.4 (C) on agent readiness against Cal.com API v2 + MCP's 51.1 (D), and leads in 3 of 7 scored categories. Cal.com API v2 + MCP leads on payments & pricing and transparency & trust.
Do Cal.com API v2 + MCP and Truto Unified Calendar API need an API key?
Cal.com API v2 + MCP takes an API key or an OAuth sign-in. Truto Unified Calendar API needs an API key.
Can an agent call Cal.com API v2 + MCP and Truto Unified Calendar API without installing anything?
Cal.com API v2 + MCP has a hosted endpoint at https://api.cal.com/v2. No hosted endpoint is listed for Truto Unified Calendar API.
Other comparisons with Cal.com API v2 + MCP or Truto Unified Calendar API
- Acuity Scheduling API vs Cal.com API v2 + MCP
- Acuity Scheduling API vs Truto Unified Calendar API
- Agenda Hero vs Cal.com API v2 + MCP
- Agenda Hero vs Truto Unified Calendar API
- Apiroc Unified Calendar API vs Cal.com API v2 + MCP
- Apiroc Unified Calendar API vs Truto Unified Calendar API
- Aurinko Calendar API vs Cal.com API v2 + MCP
- Aurinko Calendar API vs Truto Unified Calendar API
- Cal.com API v2 + MCP vs Calendly API + MCP
- Cal.com API v2 + MCP vs Cozi Family Organizer
- Cal.com API v2 + MCP vs Cronofy API
- Cal.com API v2 + MCP vs Google Calendar API
- Cal.com API v2 + MCP vs Microsoft Graph Calendar API
- Cal.com API v2 + MCP vs Nylas Calendar and Scheduler API
- Cal.com API v2 + MCP vs Reclaim.ai
- Cal.com API v2 + MCP vs SavvyCal API + MCP
- Cal.com API v2 + MCP vs Zoom Scheduler API
- Calendly API + MCP vs Truto Unified Calendar API
- Cozi Family Organizer vs Truto Unified Calendar API
- Cronofy API vs Truto Unified Calendar API
- Google Calendar API vs Truto Unified Calendar API
- Microsoft Graph Calendar API vs Truto Unified Calendar API
- Nylas Calendar and Scheduler API vs Truto Unified Calendar API
- Reclaim.ai vs Truto Unified Calendar API
- Truto Unified Calendar API vs Zoom Scheduler API
- Cal.com API v2 + MCP vs YouCanBookMe API
- SavvyCal API + MCP vs Truto Unified Calendar API
- Truto Unified Calendar API vs YouCanBookMe API
Machine-readable
- This page as Markdown
/compare/cal-com-vs-truto-calendar.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cal-com.json·/api/v1/tools/truto-calendar.json - From a terminal
anchor compare cal-com truto-calendar(the CLI) - Over MCP
compare_tools {"a": "cal-com", "b": "truto-calendar"}at/mcp, no key