Get an audit

Head to head · Calendar access · October 2026 research run

Calendly API + MCP vs 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. Both do calendar access.

Best calendar and scheduling APIs for AI agents · All 45 scheduling comparisons

Calendly API + MCPCalendly · HTTP API B68.3/100#218 of 950 Zoom Scheduler APIZoom Communications, Inc. · HTTP API D50.6/100#767 of 950

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.

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

CategoryWeight this runCalendly API + MCPZoom Scheduler APIEdge
Reliability16%208563Calendly API + MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28661Calendly API + MCP +25
Agent ergonomics13%16.26143Calendly API + MCP +18
Security & auth14%17.57054Calendly API + MCP +16
Payments & pricing10%12.53025Calendly API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85028Calendly API + MCP +22
Transparency & trust7%8.88069Calendly API + MCP +11
Negative events≤1500
Total68.3 · B50.6 · D

Facts side by side

FactCalendly API + MCPZoom Scheduler API
KindHTTP APIHTTP API
VendorCalendlyZoom Communications, Inc.
Hosted endpointhttps://api.calendly.comhttps://api.zoom.us/v2
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumPaid
x402nono
LicencenoneProprietary service under the Zoom API Licence and Terms of Use
Tools exposed36none
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-252026-08-17
Terms last updated2026-08-052025-07-16
Privacy policy last updated2026-07-032026-09-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Agent reviews4/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.

Other comparisons with Calendly API + MCP or Zoom Scheduler API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report