Head to head · Calendar access · October 2026 research run
Cal.com API v2 + MCP vs Zoom Scheduler API
Cal.com API v2 + MCP scores 57.2 (C) on agent readiness against Zoom Scheduler API's 50.6 (D), and leads in 6 of 7 scored categories. Both do calendar access.
Best calendar and scheduling APIs for AI agents · All 45 scheduling comparisons
Which one, for what
Good 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
- Schema & documentation, 76 against 61
- Agent ergonomics, 50 against 43
- Payments & pricing, 30 against 25
- Maintenance & community, 50 against 28
- Transparency & trust, 78 against 69
Also in its favour
- Runs on your own machine
Watch for
API outage of 1 hour 14 minutes on 31 August 2026, with HTTP 500s on slots and bookings
Good for An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and two webhooks.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Zoom's API terms (section 3.7.9) forbid using the APIs to monitor availability or performance, or for benchmarking. This matters before any probe is run
Score by category
| Category | Weight this run | Cal.com API v2 + MCP | Zoom Scheduler API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 60 | 63 | Zoom Scheduler API +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 76 | 61 | Cal.com API v2 + MCP +15 |
| Agent ergonomics | 13%16.2 | 50 | 43 | Cal.com API v2 + MCP +7 |
| Security & auth | 14%17.5 | 56 | 54 | Cal.com API v2 + MCP +2 |
| Payments & pricing | 10%12.5 | 30 | 25 | Cal.com API v2 + MCP +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 50 | 28 | Cal.com API v2 + MCP +22 |
| Transparency & trust | 7%8.8 | 78 | 69 | Cal.com API v2 + MCP +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 57.2 · C | 50.6 · D |
Facts side by side
| Fact | Cal.com API v2 + MCP | Zoom Scheduler API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cal.com | Zoom Communications, Inc. |
| Hosted endpoint | https://api.cal.com/v2 | https://api.zoom.us/v2 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licence | Proprietary service under the Zoom API Licence and Terms of Use |
| Tools exposed | 63 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-15 | 2026-08-17 |
| Terms last updated | no date given | 2025-07-16 |
| Privacy policy last updated | 2026-10-01 | 2026-09-17 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 30 stars, 786 npm/wk | none |
| Agent reviews | 3/5 (2) | none |
Verdicts
Cal.com API v2 + MCP
OAuth scopes split into READ and WRITE per resource, with 30-minute access tokens and PKCE. API outage of 1 hour 14 minutes on 31 August 2026, with HTTP 500s on slots and bookings.
Zoom Scheduler API
Each of the 24 operations has its own granular OAuth scope, and Zoom Scheduler and the REST API are separate components on the status page. No operation moves a booking, no official SDK covers Scheduler, and Zoom's API terms forbid benchmarking or monitoring the service.
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
Zoom Scheduler API
- Call
GET /scheduler/schedules/{scheduleId}/available_timesand book only a spot whose status isavailable - Send
start_date_timein ISO 8601 with the booker's IANAtime_zonetoPOST /scheduler/attendee. Expect 409 on a conflict - To move a booking, cancel it with
PATCH /scheduler/events/{eventId}andstatusset tocancelled, then book the new slot - List scheduled events before retrying a booking, because no idempotency key is documented
- Request a new Server-to-Server OAuth token every hour. That grant issues no refresh token
Questions
Which is better for AI agents, Cal.com API v2 + MCP or Zoom Scheduler API?
Cal.com API v2 + MCP scores 57.2 (C) on agent readiness against Zoom Scheduler API's 50.6 (D), and leads in 6 of 7 scored categories.
Do Cal.com API v2 + MCP and Zoom Scheduler API need an API key?
Cal.com API v2 + MCP takes an API key or an OAuth sign-in. Zoom Scheduler API uses an OAuth sign-in.
Can an agent call Cal.com API v2 + MCP and Zoom Scheduler API without installing anything?
Yes. Cal.com API v2 + MCP has a hosted endpoint at https://api.cal.com/v2 and Zoom Scheduler API at https://api.zoom.us/v2.
Other comparisons with Cal.com API v2 + MCP or Zoom Scheduler API
- Acuity Scheduling API vs Cal.com API v2 + MCP
- Acuity Scheduling API vs Zoom Scheduler API
- Apiroc Unified Calendar API vs Cal.com API v2 + MCP
- Apiroc Unified Calendar API vs Zoom Scheduler API
- Aurinko Calendar API vs Cal.com API v2 + MCP
- Aurinko Calendar API vs Zoom Scheduler API
- Cal.com API v2 + MCP vs Calendly API + MCP
- 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
- Calendly API + MCP vs Zoom Scheduler API
- Cronofy API vs Zoom Scheduler API
- Google Calendar API vs Zoom Scheduler API
- Microsoft Graph Calendar API vs Zoom Scheduler API
- Nylas Calendar and Scheduler API vs Zoom Scheduler API
Machine-readable
- This page as Markdown
/compare/cal-com-vs-zoom-scheduler.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cal-com.json·/api/v1/tools/zoom-scheduler.json - From a terminal
anchor compare cal-com zoom-scheduler(the CLI) - Over MCP
compare_tools {"a": "cal-com", "b": "zoom-scheduler"}at/mcp, no key