Setting the file. One moment.
Subchapter 114.21
use-cases/apis-vs-mcp-routing.mdMarkdown4 KBView on GitHub
Decide whether to route a request to Zoom APIs, Zoom MCP, or both.
Zoom APIs and Zoom MCP are complementary:
References
App Types| Primary requirement | Route | Notes |
|---|---|---|
| Deterministic automation, configuration, reporting, scheduled jobs, strict retries/error handling | zoom-rest-api | Direct control over requests, retries, and idempotency |
| AI interaction, dynamic tool discovery, AI Companion workflows, external AI interoperability | zoom-mcp | Agent chooses tools contextually through MCP |
| High-volume production automation plus AI assistant workflows | zoom-rest-api + zoom-mcp | Keep core actions in APIs; expose curated tool surfaces via MCP |
| User request | Route |
|---|---|
| “Create meetings nightly and sync metrics to BI” | zoom-rest-api |
| “Let my assistant search meeting content and fetch transcripts” | zoom-mcp |
| “Automate meeting lifecycle, then let agents answer questions from summaries” | zoom-rest-api + zoom-mcp |
zoom-oauth for app auth/token lifecycle.zoom-rest-api for create/read/update/reporting endpoints.zoom-webhooks for async event processing if needed.zoom-oauth for user OAuth token required by MCP server.zoom-mcp for semantic meeting search, summaries, recordings/transcripts, and tool invocation.zoom-rest-api handles provisioning, policy/configuration, and scheduled ingestion jobs.zoom-webhooks or zoom-websockets handles event ingestion.zoom-mcp exposes curated higher-level tools for AI Companion or external agents.Use zoom-mcp when you are: