Zoom MCP
Guidance for the bundled Zoom MCP connector in this Claude plugin. Prefer
or
setup-zoom-mcp first, then route here for tool-surface details, auth expectations, and MCP-specific constraints.
Zoom MCP Server
This plugin bundles Zoom's hosted MCP server at
for AI-agent access to:
- semantic meeting search
- meeting-linked asset retrieval
- recording resource retrieval
Zoom Docs are exposed through a separate bundled server:
- at
- purpose-built for Zoom Docs creation and retrieval
Current tool names from the main Zoom MCP server:
Some MCP clients namespace server tools in the UI, for example
.
Treat the raw tool names above as authoritative.
Zoom Docs-specific MCP work should use the dedicated
server.
Whiteboard-specific MCP work is covered by the dedicated skill
whiteboard/SKILL.md.
Quick Start
1. Export the token expected by the bundled connector:
bash
export ZOOM_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
2. Enable or restart the plugin so Claude restarts the bundled MCP server definition.
3. Verify discovery:
- Confirm the client can see , , ,
and .
- If the client exposes raw protocol inspection, is the authoritative discovery source.
- The current catalog is documented in references/tools.md.
4. Run the first useful call:
text
recordings_list
userId: "me"
from: "2026-03-01"
to: "2026-03-06"
page_size: 10
Critical Notes
1. User OAuth is the documented execution path
Use a General app with user-level OAuth as the execution path for Zoom MCP
tool use in this plugin. Do not rely on Server-to-Server OAuth as a supported MCP auth model here.
2. Zoom MCP uses MCP-specific granular scopes
The Zoom MCP scope set is not the same as the older broad REST scopes.
The key scopes for the main Zoom MCP server are:
- — Search across Zoom Meeting, Zoom Chat, and Zoom Doc, returning the most relevant results based on the query
- — Search and view meetings
- — View a meeting's assets
cloud_recording:read:list_user_recordings
cloud_recording:read:content
- — Create a new file by import
- — Read file content in Markdown format
For Zoom Docs MCP specifically, the official docs page shows these granular scopes for the documented tools:
- — Create a new file by import
- — Read file content in Markdown format
3. AI Companion features are feature prerequisites, not scope substitutes
Semantic meeting search, meeting assets, and recording-content retrieval depend on account
features such as Smart Recording and Meeting Summary for useful results. These feature
settings do not replace the required OAuth scopes.
4. Whiteboard is a separate MCP surface
The Zoom MCP endpoint and the Whiteboard MCP endpoint are separate. Route Whiteboard-specific
requests to whiteboard/SKILL.md.
5. Use REST for deterministic meeting CRUD
The current Zoom MCP tool surface does not expose deterministic
meeting create, update, or delete tools. If the user needs explicit meeting CRUD operations,
route to ../rest-api/SKILL.md.
Server Endpoints
| Transport | URL |
|---|
| Streamable HTTP (recommended) | https://mcp-us.zoom.us/mcp/zoom/streamable
|
| SSE (fallback) | https://mcp-us.zoom.us/mcp/zoom/sse
|
Dedicated Docs MCP server:
| Transport | URL |
|---|
| Streamable HTTP (recommended) | https://mcp.zoom.us/mcp/docs/streamable
|
| SSE (fallback) | https://mcp.zoom.us/mcp/docs/sse
|
Dedicated Whiteboard MCP skill:
Search and Retrieval Model
uses AI Companion retrieval rather than a plain metadata filter. In this
use the live MCP server as authoritative for response schema and scope behavior.
Two result families matter most:
- Recap-oriented results: AI summary, meeting-linked documents, recordings, and related assets
- Recording-oriented results: cloud recording references and transcript-capable resources
Use examples/transcript-retrieval.md for the main retrieval
workflow.
Tool Catalog
| Tool | Key Parameters | Required Scope |
|---|
| * | |
| , , , , | |
| *, , , , , | cloud_recording:read:content
|
| *, , , , , , , | cloud_recording:read:list_user_recordings
|
* Required parameter
Full parameter and output guidance: references/tools.md
Key Workflows
Search meeting content, then retrieve assets:
text
search_meetings
q: "Q4 planning discussion"
from: "2026-03-01"
to: "2026-03-06"
→ choose a returned meeting
→ get_meeting_assets meetingId: "MEETING_ID_OR_UUID"
List recordings, then retrieve recording resources:
text
recordings_list
userId: "me"
from: "2026-03-01"
to: "2026-03-06"
→ choose a recording target
→ get_recording_resource meetingId: "MEETING_UUID_OR_RECORDING_ID"
Create or fetch a Zoom Doc:
- use the dedicated server rather than the main server
- official documented tools on the Zoom Docs MCP page are:
Error Reference
| Code | Meaning | Fix |
|---|
| Missing or rejected bearer token at the endpoint | Set , then restart Claude or re-enable the plugin |
-32001 Invalid access token
| Token expired, malformed, or missing required scopes | Refresh OAuth token and verify the MCP-specific scopes |
-32602 Can not found tool
| Requested tool name is not exposed by the active MCP server | Re-run and use the current tool names for that endpoint |
| Possible downstream resource-not-found response | Re-discover the target with or |
Full error reference: references/error-codes.md
Documentation
Concepts
- concepts/mcp-architecture.md — MCP protocol, hosted endpoints, discovery, and capability model
- concepts/oauth-setup.md — OAuth app creation, MCP-specific scopes, AI Companion prerequisites, token lifecycle
Examples
- examples/transcript-retrieval.md — Search/assets and recording-resource workflows
- examples/create-zoom-doc.md — Verified Zoom Docs creation flow
- examples/search-and-act.md — Search, inspect assets, and hand off CRUD work to REST when needed
- examples/meeting-lifecycle.md — Why meeting CRUD belongs in REST, plus the MCP-to-REST handoff pattern
References
- references/tools.md — Current Zoom MCP tool reference
- references/error-codes.md — MCP and Zoom API errors with fixes
- whiteboard/SKILL.md — Dedicated Whiteboard MCP skill
Troubleshooting
- troubleshooting/common-errors.md — Scope failures, endpoint mixups, search/recording issues
Operations
- RUNBOOK.md — 5-minute preflight and debugging checklist
Related Skills
- zoom-rest-api — Deterministic REST API access, including meeting CRUD
- zoom-oauth — OAuth implementation patterns
- zoom-webhooks — Event-driven recording and meeting workflows
- zoom-rtms — Live media and transcript streams during active meetings