$ ~/registry/skill/anthropics-partner-built-zoom-plugin-skills-zoom-mcp

SKILL

zoom-mcp

Name: zoom-mcp
Author: anthropics

Plan and troubleshoot MCP access to Zoom meetings, recordings, assets, and transcripts.

Stars

★ 22,528

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

This material is primarily documentation/guidance for a Zoom MCP connector rather than executable code. However, the README explicitly requires a Zoom user OAuth access token and connects to official Zoom MCP endpoints to access meetings, recordings, and related assets, so the overall risk is low-to-moderate with primary concerns around credentials and business data access.

CredentialsCaution

The README explicitly requires ZOOM_MCP_ACCESS_TOKEN, a Zoom user-level OAuth access token with scopes for meeting search, meeting assets, cloud recordings, and some Docs-related access. This is a sensitive credential that could enable misuse of business data if exposed via logs, environment variables, or processes, but the material does not show clear red flags of requesting unrelated credentials.

Network egressCaution

The material states that it connects to Zoom-hosted MCP servers at mcp-us.zoom.us and, for Docs, mcp.zoom.us. By design, meeting queries, recording listings, asset retrieval requests, and related user data would be sent to official Zoom endpoints; this is normal for such connectors, and there is no evidence of exfiltration to unknown third-party domains.

Code executionLow risk

The system flags this as prompt-only, and the provided content is documentation and usage guidance rather than an implementation showing arbitrary local code execution, binary installation, or elevated system permissions. While it mentions restarting the plugin/server definition, that alone is insufficient to indicate unusual local execution risk.

Data accessCaution

According to the README, the tool surface can access meeting search results, meeting assets, recording resources, recording lists, and some Zoom Docs read/write scopes. This means it can touch meeting content, recordings, and document data, which is consistent with the stated function; there is no indication of access to the local filesystem or unrelated system resources.

Supply chainCaution

Positive signals include a GitHub source and open-source status, which provide some auditability. However, the repo has 0 stars, no declared license, unknown maintenance status, and this skill references a bundled Zoom-hosted MCP server, meaning the actual server-side implementation is not fully covered by the local repository; supply-chain transparency is therefore moderate and should be validated further before adoption.

Recommendations

Request only the minimum necessary Zoom OAuth scopes for this connector, and prefer short-lived or easily rotated tokens.
Do not expose ZOOM_MCP_ACCESS_TOKEN in shell history, logs, or process monitoring; use a dedicated secret injection mechanism where possible.
Before deployment, verify that mcp-us.zoom.us and mcp.zoom.us are approved official Zoom endpoints and assess their data compliance implications.
Review the open-source repository contents, recent commits, and dependency list to ensure they align with the described hosted MCP service actually being used.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "zoom-mcp" skill from askskill:
1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/partner-built/zoom-plugin/skills/zoom-mcp/SKILL.md
2. Save it as ~/.claude/skills/zoom-mcp/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Plan meeting data access

Prompt

I want to access Zoom meetings, recordings, and transcripts in an MCP workflow. Help me plan which Zoom MCP connectors to use, the typical call order, and key permissions or limitations.

Expected

A clear integration plan covering suitable connectors, call sequence, permission requirements, and common limitations.

Troubleshoot recording access failure

Prompt

My MCP workflow can read Zoom meeting information, but fetching cloud recordings always fails. Analyze possible causes and provide prioritized troubleshooting steps.

Expected

A troubleshooting checklist covering authentication, permissions, resource scope, connector choice, and error-isolation guidance.

Route Docs and Whiteboard requests correctly

Prompt

Determine whether these requests should use zoom-mcp: read meeting transcripts, fetch Zoom Docs content, and manipulate Whiteboard boards. Specify which MCP service each should route to.

Expected

Routing guidance that clarifies which requests use zoom-mcp and which should go to the dedicated Docs or whiteboard service.

// docs

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.