New to Claude Skills? Learn how to install them →

anthropics on GitHub

Zoom MCP

OfficialFree

Streamline access to Zoom meeting assets and recordings.

Get this skill

Free · Opens the source repo

What Zoom MCP does

Zoom MCP is designed to facilitate seamless interaction with Zoom's hosted MCP server, providing developers and designers with the tools needed to access and manage meeting-related assets. This skill is particularly useful for those who need to perform semantic searches for meetings, retrieve meeting-linked assets, and access cloud recordings. By utilizing the dedicated servers for Zoom Docs and Whiteboard, users can effectively manage different types of Zoom content through a unified interface.

The skill includes several key tools such as get_meeting_assets, search_meetings, get_recording_resource, and recordings_list, which allow for efficient querying and retrieval of meeting data. The guidance provided within the skill ensures that users can set up the necessary OAuth tokens and understand the specific scopes required for accessing the Zoom MCP functionalities. This makes it easier to integrate Zoom capabilities into existing workflows and applications.

For those who are already using the Zoom platform, this skill enhances productivity by automating the retrieval of important meeting information and assets. It is particularly valuable for teams that rely on Zoom for collaboration and need to access recordings or documents quickly. The structured approach to searching and retrieving assets means that users can focus on their tasks without getting bogged down in manual processes.

However, it is important to note that while Zoom MCP excels in accessing meeting-related assets, it does not support deterministic CRUD operations for meetings. For those needs, users are directed to the separate Zoom REST API skill. Additionally, users should be aware of the specific OAuth scopes required for different functionalities to avoid authorization issues.

When to use it

Use this skill when you need to retrieve meeting assets, search for meetings, or access cloud recordings from Zoom in an automated manner.

When not to use it

This skill is not suitable for users needing to create, update, or delete meetings, as those operations are handled by the Zoom REST API.

What you can build with it

Retrieve Meeting Assets

Use the `search_meetings` tool to find relevant meetings based on keywords and then retrieve associated assets.

Access Cloud Recordings

Utilize the `recordings_list` tool to list and access cloud recordings for a specified user within a date range.

Integrate Zoom Docs

Leverage the dedicated Zoom Docs MCP server for creating and retrieving documents related to your meetings.

How to install Zoom MCP

View source

1. Install with the skills CLI

npx skills add anthropics/knowledge-work-plugins/zoom-mcp --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by anthropics

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

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

Frequently asked questions about Zoom MCP

Similar skills