Generated banner for Zoom MCP
Generated logo for Zoom MCP

Zoom MCP

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • Medium risk

From the author

Guidance for the bundled Zoom MCP connectors. Use after routing to an MCP workflow when planning or troubleshooting tool-based access to meetings, recordings, meeting assets, or transcripts. Route Zoom Docs requests to the dedicated Docs MCP server and Whiteboard-specific requests to `zoom-mcp/whiteboard`.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides essential guidance for configuring and using the bundled Zoom MCP connectors. It covers the setup of user-level OAuth, required granular scopes, and the specific tool surfaces for meeting discovery, asset retrieval, and Zoom Docs management. It emphasizes the use of the correct MCP server endpoints and distinguishes between the main Zoom MCP server, the dedicated Zoom Docs MCP server, and the separate Whiteboard MCP surface.

What it does

  • Provides configuration steps for Zoom MCP connectors using user-level OAuth.
  • Lists available tools for semantic meeting search and recording retrieval.
  • Details the specific granular OAuth scopes required for each MCP tool.
  • Explains how to route requests to dedicated servers for Zoom Docs and Whiteboards.
  • Offers a troubleshooting guide for common MCP protocol and API-level errors.
  • Defines the recommended workflows for searching meetings and accessing associated assets.

When to use it

  • When setting up AI-agent access to Zoom meetings, recordings, or documents.
  • When troubleshooting connectivity or authorization issues with Zoom MCP tools.
  • When planning agentic workflows that require semantic search or asset retrieval from Zoom.
  • When needing to distinguish between the main Zoom MCP server and the dedicated Docs or Whiteboard servers.

Advantages

  • Centralizes configuration and troubleshooting for multiple Zoom MCP surfaces.
  • Clarifies the distinction between MCP-specific scopes and legacy REST scopes.
  • Provides clear routing logic for specialized Zoom content like Docs and Whiteboards.
  • Includes a comprehensive error reference for rapid debugging of tool-use failures.

Usage examples

“search_meetings q: 'Q4 planning' from: '2026-03-01'”
The agent performs a semantic search for meetings matching the query within the specified date range, returning a list of relevant meeting objects.
“get_meeting_assets meetingId: '123456789'”
The agent retrieves the summary, recordings, and linked documents associated with the specified meeting ID.
“recordings_list userId: 'me' from: '2026-03-01'”
The agent lists all cloud recordings for the authenticated user starting from the provided date.
“get_recording_resource meetingId: '987654321'”
The agent retrieves the specific recording content resources for the given meeting ID, provided the correct scopes are present.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/zoom-mcp/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip zoom-mcp.zip -d .agents/skills

Documentation by Zoom

Zoom MCP

Guidance for the bundled Zoom MCP connector in this Claude plugin. Prefer design-mcp-workflow 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 mcp-us.zoom.us for AI-agent access to:

  • semantic meeting search

  • meeting-linked asset retrieval

  • recording resource retrieval

Zoom Docs are exposed through a separate bundled server:

  • zoom-docs-mcp at mcp.zoom.us

  • purpose-built for Zoom Docs creation and retrieval

Current tool names from the main Zoom MCP server:

  • get_meeting_assets

  • search_meetings

  • get_recording_resource

  • recordings_list

Some MCP clients namespace server tools in the UI, for example zoom-mcp:recordings_list. Treat the raw tool names above as authoritative.

Zoom Docs-specific MCP work should use the dedicated zoom-docs-mcp 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:

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 recordings_list, search_meetings, get_meeting_assets, and get_recording_resource.

  • If the client exposes raw protocol inspection, tools/list is the authoritative discovery source.

  • The current catalog is documented in references/tools.md.

4. Run the first useful call:

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:

  • ai_companion:read:search — Search across Zoom Meeting, Zoom Chat, and Zoom Doc, returning the most relevant results based on the query

  • meeting:read:search — Search and view meetings

  • meeting:read:assets — View a meeting's assets

  • cloud_recording:read:list_user_recordings — Lists all cloud recordings for a user.

  • cloud_recording:read:content — read recording content scope

  • docs:write:import — Create a new file by import

  • docs:read:export — Read file content in Markdown format

For Zoom Docs MCP specifically, the official docs page shows these granular scopes for the documented tools:

  • docs:write:import — Create a new file by import

  • docs:read:export — 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

TransportURL
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:

TransportURL
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

search_meetings 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

ToolKey ParametersRequired Scope
get_meeting_assetsmeetingId*meeting:read:assets
search_meetingsq, from, to, page_size, next_page_tokenmeeting:read:search
get_recording_resourcemeetingId*, types, clip_num, play_time, raw_passcode, encode_passcodecloud_recording:read:content
recordings_listuserId*, from, to, meeting_id, trash, trash_type, page_size, next_page_tokencloud_recording:read:list_user_recordings

* Required parameter

Full parameter and output guidance: references/tools.md

Key Workflows

Search meeting content, then retrieve assets:

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:

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 zoom-docs-mcp server rather than the main zoom-mcp server

  • official documented tools on the Zoom Docs MCP page are:

    • create_file_with_content

    • get_file_content

Error Reference

CodeMeaningFix
401 UnauthorizedMissing or rejected bearer token at the endpointSet ZOOM_MCP_ACCESS_TOKEN, then restart Claude or re-enable the plugin
-32001 Invalid access tokenToken expired, malformed, or missing required scopesRefresh OAuth token and verify the MCP-specific scopes
-32602 Can not found toolRequested tool name is not exposed by the active MCP serverRe-run tools/list and use the current tool names for that endpoint
404Possible downstream resource-not-found responseRe-discover the target with search_meetings or recordings_list

Full error reference: references/error-codes.md

Documentation

Concepts
Examples
References
Troubleshooting
Operations
  • RUNBOOK.md — 5-minute preflight and debugging checklist

  • 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

Files

troubleshooting/common-errors.md

Common Errors — Zoom MCP Server

Diagnostic guide for the most frequent issues when using the Zoom MCP server.

Authentication Issues

Access token is required (-32001)

Cause: The bundled connector does not have a token available, so no Authorization header is sent to the Zoom MCP endpoint.

Fix: Set ZOOM_MCP_ACCESS_TOKEN and restart Claude Code or re-enable the plugin.

export ZOOM_MCP_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
Invalid access token (-32001)

Cause: The access token expired, was revoked, or does not contain the exact MCP scopes needed for the tool you called.

Fix: Refresh the token, update ZOOM_MCP_ACCESS_TOKEN, restart Claude Code, and verify the MCP-specific granular scopes.

Scope Issues

search_meetings fails on scope

Server-required scope: meeting:read:search

get_meeting_assets fails on scope

Server-required scope: meeting:read:assets

recordings_list fails on scope

Server-required scope: cloud_recording:read:list_user_recordings

get_recording_resource fails on scope

Server-required scope: cloud_recording:read:content

create_file_with_content fails on scope

Required scope: docs:write:import

get_file_content fails on scope

Required scope: docs:read:export

Search and Retrieval Issues

Semantic search returns no useful results

Common causes:

  • AI Companion features were not enabled for those meetings

  • the query is too narrow

  • the date window is too narrow

  • the meeting is easier to locate through recordings_list

Fixes:

  • enable Smart Recording and Meeting Summary

  • widen from and to

  • try shorter search terms

  • fall back to recordings_list

Meeting assets retrieval fails even with a valid token

Most often this means one of these:

  • missing meeting:read:assets

  • guessed meetingId instead of the right UUID or numeric ID

  • user does not have access to that meeting's assets

Recording-oriented retrieval fails

If get_recording_resource cannot find the target:

  • use recordings_list first

  • use the identifier returned by the live listing flow

  • avoid assuming a scheduled meeting number is the same identifier used by the recording flow

Direct resource download returns 401

Returned resource URLs still require the bearer token.

Fix: Include Authorization: Bearer YOUR_TOKEN when fetching the URL directly.

Connection Issues

Can not found tool: ... in this MCP Server (-32602)

Cause: The requested tool does not exist on the active MCP server, or the request was sent to the wrong MCP surface.

Fix:

  • Zoom MCP: https://mcp-us.zoom.us/mcp/zoom/streamable

  • Zoom Docs MCP: https://mcp.zoom.us/mcp/docs/streamable

  • Whiteboard MCP: https://mcp-us.zoom.us/mcp/whiteboard/streamable

  • re-run tools/list

  • use the current tool names exposed by that server

  • if the request is Zoom Docs-specific, use the dedicated Docs MCP server

  • if the request is Whiteboard-specific, route to ../whiteboard/SKILL.md

MCP server not appearing in the client

Fix:

  • confirm the plugin is enabled

  • confirm ZOOM_MCP_ACCESS_TOKEN is set

  • restart Claude Code so the bundled MCP server restarts

Parameter and Call-Handling Issues

Call handle error (-32603)

Cause: The tool call was accepted at the protocol layer, but the server failed while handling the call. One observed case was calling recordings_list without the required arguments.

Fix:

  • re-check required parameters against the live schema from tools/list

  • retry with the missing arguments added

Upstream 400 invalid param

Cause: The MCP tool reached the downstream Zoom API, but one of the passed arguments was invalid. One observed case was calling create_file_with_content with a bogus parent_id.

Fix:

  • remove the bad argument or replace it with a valid value

  • retry the tool call

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter, Needs an MCP server

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/zoom-mcp · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download zoom-mcp.zip