Setting the file. One moment.
Subchapter 158.9
RUNBOOK.mdMarkdown4 KBView on GitHub
Quick diagnostic checklist before using the Zoom MCP server.
1. Token exported for the bundled connector?
echo "${ZOOM_MCP_ACCESS_TOKEN:+set}"
echo "${ZOOM_DOCS_MCP_ACCESS_TOKEN:+set}"If empty, export the relevant token using concepts/oauth-setup.md.
2. Tool discovery working?
recordings_list, search_meetings, get_meeting_assets,
and get_recording_resource.create_file_with_content
and get_file_content.tools/list succeeds.3. Correct OAuth scopes on the token?
Minimum Zoom MCP scopes for this guide:
ai_companion:read:search — Search across Zoom Meeting, Zoom Chat, and Zoom Docmeeting:read:search — Search and view meetingsmeeting:read:assets — View a meeting’s assetscloud_recording:read:list_user_recordings — Lists all cloud recordings for a user.cloud_recording:read:content — read recording content scopeMinimum Zoom Docs MCP scopes:
docs:write:import — Create new file by importdocs:read:export — Read file content in Markdown formatWhiteboard uses a separate scope set. See whiteboard/SKILL.md.
4. AI Companion features enabled?
Go to Zoom web portal → Admin → Account Management → Account Settings → AI Companion. Confirm Smart Recording and Meeting Summary are enabled if you expect semantic search, meeting assets, or transcript-rich recording content to be useful.
| Symptom | Likely cause | Fix |
|---|---|---|
-32001 Access token is required | Token env var missing or empty | Export ZOOM_MCP_ACCESS_TOKEN, then restart Claude Code |
-32001 Invalid access token, does not contain scopes:[meeting:read:search] | Missing semantic-search scope | Add meeting:read:search and mint a new user token |
-32001 Invalid access token, does not contain scopes:[meeting:read:assets,...] | Missing meeting-assets scope | Add meeting:read:assets and mint a new user token |
-32001 Invalid access token, does not contain scopes:[cloud_recording:read:list_user_recordings,...] | Missing recordings-list scope | Add cloud_recording:read:list_user_recordings |
-32001 Invalid access token, does not contain scopes:[cloud_recording:read:content] | Missing recording-content scope | Add cloud_recording:read:content |
-32602 Can not found tool: ... in this MCP Server | Wrong endpoint surface or wrong tool name | Re-run tools/list and use the current tool names for the active MCP server |
-32603 Call handle error | Missing required parameters or server-side call handling failure | Re-check required arguments against the live schema and retry |
Upstream API returned error status code: 400 ... invalid param | Invalid parameter value passed through to the underlying Zoom API | Fix the specific argument value, such as parent_id for Docs creation on the dedicated Docs server |
| Search returns no useful meeting content | AI Companion features missing or data not indexed | Enable Smart Recording + Meeting Summary, widen the search window, or fall back to recordings_list |
Use user OAuth as the documented execution path for Zoom MCP content tools in this plugin. Do not rely on Server-to-Server OAuth as a supported MCP auth model here.