/zoom-mcp

name: zoom-mcp
description: 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`.
user-invocable: false
triggers:
  - "zoom mcp"
  - "zoom mcp server"
  - "zoom mcp tools"
  - "zoom tools/list"
  - "zoom tools/call"
  - "ai companion transcript"
  - "agentic retrieval"
  - "zoom semantic meeting search"
  - "zoom search meetings by content"
  - "zoom meeting assets mcp"
  - "zoom recording resource mcp"
  - "zoom docs via mcp"
  - "zoom transcript via mcp"
  - "meeting transcript via mcp"

Zoom MCP

Guidance for the bundled Zoom MCP connector in this Claude plugin. Prefer `design-mcp-workflow` or [setup-zoom-mcp](../setup-zoom-mcp/SKILL.md) 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](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](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](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](../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:

• [whiteboard/SKILL.md](whiteboard/SKILL.md)

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](examples/transcript-retrieval.md) for the main retrieval workflow.

Tool Catalog

| Tool | Key Parameters | Required Scope | |------|---------------|----------------| | `get_meeting_assets` | `meetingId`* | `meeting:read:assets` | | `search_meetings` | `q`, `from`, `to`, `page_size`, `next_page_token` | `meeting:read:search` | | `get_recording_resource` | `meetingId`*, `types`, `clip_num`, `play_time`, `raw_passcode`, `encode_passcode` | `cloud_recording:read:content` | | `recordings_list` | `userId`*, `from`, `to`, `meeting_id`, `trash`, `trash_type`, `page_size`, `next_pa