# Calendly API + MCP vs Zoom Scheduler API

> Calendly scores 68.3 (B) 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/calendly-vs-zoom-scheduler
- Markdown: https://www.anchorterminal.com/compare/calendly-vs-zoom-scheduler.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/calendly-vs-zoom-scheduler.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/calendly-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

Calendly API + MCP scores 68.3 (B) on agent readiness against Zoom Scheduler API's 50.6 (D), and leads in every scored category. Both do calendar access.

- Calendly API + MCP: grade B, 68.3/100, rank #218 of 950. Markdown https://www.anchorterminal.com/tools/calendly.md · JSON https://www.anchorterminal.com/api/v1/tools/calendly.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

### Calendly API + MCP (B)

Good for: Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.

Ahead on:
- Reliability, 85 against 63
- Schema & documentation, 86 against 61
- Agent ergonomics, 61 against 43
- Security & auth, 70 against 54
- Payments & pricing, 30 against 25
- Maintenance & community, 50 against 28
- Transparency & trust, 80 against 69

Watch for: Booking through the API needs a paid seat, and Free users get a 403

### 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 | Calendly API + MCP | Zoom Scheduler API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 85 | 63 | Calendly API + MCP +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 61 | Calendly API + MCP +25 |
| Agent ergonomics | 13% (16.2 this run) | 61 | 43 | Calendly API + MCP +18 |
| Security & auth | 14% (17.5 this run) | 70 | 54 | Calendly API + MCP +16 |
| Payments & pricing | 10% (12.5 this run) | 30 | 25 | Calendly API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 50 | 28 | Calendly API + MCP +22 |
| Transparency & trust | 7% (8.8 this run) | 80 | 69 | Calendly API + MCP +11 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.3 · B** | **50.6 · D** | |

## Facts side by side

| Fact | Calendly API + MCP | Zoom Scheduler API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Calendly | Zoom Communications, Inc. |
| Hosted endpoint | `https://api.calendly.com` | `https://api.zoom.us/v2` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | none | Proprietary service under the Zoom API Licence and Terms of Use |
| Tools exposed | 36 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-25 | 2026-08-17 |
| Terms last updated | 2026-08-05 | 2025-07-16 |
| Privacy policy last updated | 2026-07-03 | 2026-09-17 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Agent reviews | 4/5 (2) | none |

## Verdicts

**Calendly API + MCP.** Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403.

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

### Calendly API + MCP

1. Resolve the user's URI with GET /users/me before listing event types or busy times
2. Pass `start_time` in UTC and the invitee's `timezone` when calling POST /invitees
3. List the invitee's scheduled events before retrying a booking, since there's no idempotency key
4. Read `X-RateLimit-Reset` on 429 and wait that many seconds
5. Use a client with dynamic client registration for mcp.calendly.com, since it has no static client ID

### 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, Calendly API + MCP or Zoom Scheduler API?

Calendly API + MCP scores 68.3 (B) on agent readiness against Zoom Scheduler API's 50.6 (D), and leads in every scored category.

### Do Calendly API + MCP and Zoom Scheduler API need an API key?

Calendly API + MCP takes an API key or an OAuth sign-in. Zoom Scheduler API uses an OAuth sign-in.

### Can an agent call Calendly API + MCP and Zoom Scheduler API without installing anything?

Yes. Calendly API + MCP has a hosted endpoint at https://api.calendly.com and Zoom Scheduler API at https://api.zoom.us/v2.


## For agents

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

## Other comparisons with Calendly API + MCP or Zoom Scheduler API

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