# Cal.com API v2 + MCP vs Zoom Scheduler API

> Cal.com API v2 scores 57.2 (C) to Zoom Scheduler's 50.6 (D) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler
- Markdown: https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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.

- Cal.com API v2 + MCP: grade C, 57.2/100, rank #618 of 950. Markdown https://www.anchorterminal.com/tools/cal-com.md · JSON https://www.anchorterminal.com/api/v1/tools/cal-com.json
- Zoom Scheduler API: grade D, 50.6/100, rank #767 of 950. Markdown https://www.anchorterminal.com/tools/zoom-scheduler.md · JSON https://www.anchorterminal.com/api/v1/tools/zoom-scheduler.json
- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md
- All 45 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md

## Which one, for what

### Cal.com API v2 + MCP (C)

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

### Zoom Scheduler API (D)

Good for: An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and two webhooks.

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 | Cal.com API v2 + MCP | Zoom Scheduler API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 63 | Zoom Scheduler API +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 76 | 61 | Cal.com API v2 + MCP +15 |
| Agent ergonomics | 13% (16.2 this run) | 50 | 43 | Cal.com API v2 + MCP +7 |
| Security & auth | 14% (17.5 this run) | 56 | 54 | Cal.com API v2 + MCP +2 |
| Payments & pricing | 10% (12.5 this run) | 30 | 25 | Cal.com API v2 + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 50 | 28 | Cal.com API v2 + MCP +22 |
| Transparency & trust | 7% (8.8 this run) | 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

1. Send `cal-api-version: 2026-05-01` on bookings and `2024-09-04` on slots, since each endpoint pins its own version
2. Append `?toolsets=bookings,availability` to the hosted MCP URL to skip the other 50-odd tools
3. Page bookings with `pagination.nextCursor`, not offsets
4. Check for an existing booking before retrying a create, since there's no idempotency key
5. Use `cal_` test keys while building so bookings don't reach real calendars

### Zoom Scheduler API

1. Call `GET /scheduler/schedules/{scheduleId}/available_times` and book only a spot whose status is `available`
2. Send `start_date_time` in ISO 8601 with the booker's IANA `time_zone` to `POST /scheduler/attendee`. Expect 409 on a conflict
3. To move a booking, cancel it with `PATCH /scheduler/events/{eventId}` and `status` set to `cancelled`, then book the new slot
4. List scheduled events before retrying a booking, because no idempotency key is documented
5. 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.


## For agents

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

## Other comparisons with Cal.com API v2 + MCP or Zoom Scheduler API

- [Acuity Scheduling API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cal-com.md)
- [Acuity Scheduling API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler.md)
- [Apiroc Unified Calendar API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/apiroc-vs-cal-com.md)
- [Apiroc Unified Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-zoom-scheduler.md)
- [Aurinko Calendar API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-cal-com.md)
- [Aurinko Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-zoom-scheduler.md)
- [Cal.com API v2 + MCP vs Calendly API + MCP](https://www.anchorterminal.com/compare/cal-com-vs-calendly.md)
- [Cal.com API v2 + MCP vs Cronofy API](https://www.anchorterminal.com/compare/cal-com-vs-cronofy.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 Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cal-com-vs-microsoft-graph-calendar.md)
- [Cal.com API v2 + MCP vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cal-com-vs-nylas-calendar.md)
- [Calendly API + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/calendly-vs-zoom-scheduler.md)
- [Cronofy API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-zoom-scheduler.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 Zoom Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.md)
- [Nylas Calendar and Scheduler API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler.md)