01 · Records and state owned
Meetings, Team Chat, Whiteboard and other licensed Zoom-product resources on provider servers; external-server tools and custom-agent context on the host side.
Zoom
Zoom Platform
Zoom occupies both sides of MCP: external agents can use product-specific Zoom servers, while AI Companion and AI Studio can consume tools from external servers.
Events & live engagementSystem of engagementExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve licensed product context through product-specific Zoom servers; on the host side, discover and invoke selected external-server tools within AI Companion or AI Studio.
03 · Actions and write paths
Schedule meetings and automate supported product workflows under per-server scopes; host-side actions depend on the external tools configured for the Zoom agent.
04 · Authentication and permissions
Zoom provider servers require a manually registered General app, OAuth 2.0 with PKCE and product scopes. External servers connected to Zoom retain their own authentication model.
05 · Monitoring, approval, and recovery
Model each Zoom product server and each external server as a separate trust boundary; preserve the acting user, app, license, scopes, agent and selected tools.
06 · Limits and caveats
Provider access requires the corresponding Zoom product license and server-specific scopes. Zoom's product servers do not support Dynamic Client Registration or Client ID Metadata Documents.
Agent access
MCP support
Official MCP server + 3rd Party MCP servicesZoom product-specific MCP servers plus MCP host capabilitiesCurrent documented service
Support: Official MCP server + 3rd Party MCP services
Read scope: Expose only the licensed Zoom product and scopes selected for each provider connection; keep results distinct from data returned by external servers hosted in Zoom agents.
Write scope: Allow product-scoped Zoom actions through provider servers and separately govern side effects from external tools invoked by AI Companion or AI Studio agents.
Authentication: Provider connections use a manually registered Zoom General app with OAuth 2.0 Authorization Code, PKCE and Bearer tokens; external-server authentication is configured independently.
Approval boundary: Confirm participant-facing meeting, chat or whiteboard actions at the Zoom provider boundary; confirm external-system side effects at the tool boundary presented by the Zoom agent.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Zoom ships them.
Single-platform patterns
- Webinar and customer-meeting operations cockpit
- Event operations cockpit
- Attendee intelligence room
- Webinar follow-up studio
Multi-platform compositions
- Zoom Platform + CRM or lifecycle system: event operations cockpit
- Zoom Platform + media-production platform + work-management or analytics system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
6 recorded sources
MCP / agent-role validationRepresentative source
https://developers.zoom.us/docs/mcp/ ↗Zoom documents product-specific servers for Meetings, Team Chat, Whiteboard, and other products, and separately supports connecting external MCP servers in Zoom AI Studio.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://developers.zoom.us/docs/api/ ↗First-party API overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://developers.zoom.us/docs/mcp/servers/connect-to-zoom-mcp-servers/ ↗Reverified product-specific MCP servers, OAuth scopes, licenses, and action boundaries.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Developer platformSource inventory
https://developers.zoom.us/ ↗First-party developer portal.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://zoom.us/ ↗Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
WebhooksSource inventory
https://developers.zoom.us/docs/api/meetings/events/ ↗First-party event reference.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.