Zoom Mcp
Wire an AI agent to Zoom’s hosted MCP for semantic meeting search, recordings, assets, and Markdown-to-Zoom-Docs—without hardcoding tool inventories.
Overview
Zoom Mcp is an agent skill most often used in Build (also Operate, Grow) that connects agents to Zoom’s hosted MCP for meeting search, assets, recordings, and docs via protocol discovery and user OAuth.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill zoom-mcpWhat is this skill?
- Hosted Zoom MCP: Streamable HTTP (recommended) and SSE fallback at `mcp-us.zoom.us`
- Separate Whiteboard MCP surface; meeting CRUD should use REST—not assumed on MCP
- Discovery via MCP `tools/list`—do not hardcode tool counts or names in client logic
- Capability focus: semantic meeting search, meeting assets, recordings, Zoom Docs from Markdown
- User OAuth documented as primary auth path for bundled Zoom MCP servers
Adoption & trust: 893 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want your agent to find Zoom meetings and recordings intelligently but do not know which hosted MCP URL, auth flow, or discovery pattern to use—and you might wrongly assume full meeting CRUD on MCP.
Who is it for?
Solo builders shipping meeting-aware agents who need hosted MCP endpoints, OAuth guidance, and a clear split between MCP semantic tools and REST CRUD.
Skip if: Teams that only need calendar scheduling without Zoom data, air-gapped environments blocked from `mcp-us.zoom.us`, or workflows requiring guaranteed meeting create/update/delete solely through MCP without REST.
When should I use this skill?
Configuring Zoom hosted MCP (meetings or whiteboard surfaces), discovering tools via `tools/list`, or retrieving meetings, assets, recordings, and docs through MCP rather than hardcoded REST assumptions.
What do I get? / Deliverables
You configure Streamable HTTP or SSE against Zoom’s hosted MCP, authenticate with user OAuth, and call tools discovered from `tools/list` for search and assets—using REST when you need deterministic meeting management.
- Correct MCP transport and URL configuration
- Tool inventory sourced from live `tools/list`
- Documented auth and REST-vs-MCP capability split for your agent
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
MCP client configuration and discovery are integration work you do while assembling agent tooling, even though you will invoke meetings data later in operate and grow workflows. Integrations is the canonical shelf because the skill documents transport URLs, auth model, and tools/list discovery—not distribution or analytics dashboards.
Where it fits
Register Zoom MCP Streamable HTTP URL and OAuth in your agent client before shipping a meeting assistant.
Publish meeting-derived Markdown into Zoom Docs for onboarding or changelog collateral.
How it compares
Hosted MCP integration skill for semantic Zoom data—not a replacement for Zoom REST when you need full meeting lifecycle CRUD.
Common Questions / FAQ
Who is zoom-mcp for?
Indie developers and agent builders integrating Zoom meetings, recordings, and docs into Claude Code, Cursor, or other MCP clients with user OAuth.
When should I use zoom-mcp?
During Build while wiring MCP transports and OAuth; during Operate when triaging customer calls via semantic meeting search; during Grow when turning call insights or Markdown notes into Zoom Docs for distribution.
Is zoom-mcp safe to install?
It entails network access to Zoom’s hosted MCP and user OAuth tokens—scope minimally, rotate credentials, and review the Security Audits panel on this Prism page before production use.
SKILL.md
READMESKILL.md - Zoom Mcp
# MCP Architecture — Zoom MCP Server ## What is MCP? Model Context Protocol (MCP) standardizes how AI systems connect to external tools and data sources. Zoom exposes hosted MCP surfaces that clients can discover and call over MCP. ## Hosted Zoom MCP Surfaces ### Zoom MCP | Transport | URL | |-----------|-----| | Streamable HTTP (recommended) | `https://mcp-us.zoom.us/mcp/zoom/streamable` | | SSE (fallback) | `https://mcp-us.zoom.us/mcp/zoom/sse` | ### Whiteboard MCP | Transport | URL | |-----------|-----| | Streamable HTTP (recommended) | `https://mcp-us.zoom.us/mcp/whiteboard/streamable` | | SSE (fallback) | `https://mcp-us.zoom.us/mcp/whiteboard/sse` | Whiteboard MCP is covered by the dedicated skill [../whiteboard/SKILL.md](../whiteboard/SKILL.md). ## Discovery Model Do not hardcode tool counts in client logic. Use the MCP protocol `tools/list` response as the current source of truth for: - tool names - descriptions - parameter schemas - newly added or removed tools ## Current Capability Shape The current Zoom MCP surface is centered on: - semantic meeting search - meeting asset retrieval - recording resource retrieval - Zoom Docs creation from Markdown If the task requires deterministic meeting CRUD, use the REST API skill instead of assuming those operations exist on the current Zoom MCP surface. ## Authentication Model User OAuth is the primary documented path. Use user OAuth as the expected auth model for the bundled Zoom MCP servers in this plugin. ## Protected Resource Metadata The hosted MCP surfaces advertise supported scopes through OAuth protected-resource metadata. Zoom MCP protected-resource metadata currently exposes: - `ai_companion:read:search` - `meeting:read:assets` - `meeting:read:search` - `cloud_recording:read:content` - `cloud_recording:read:list_user_recordings` - `docs:write:import` - `docs:read:export` Whiteboard MCP protected-resource metadata currently exposes: - `whiteboard:write:whiteboard` - `whiteboard:read:list_whiteboards` - `whiteboard:read:whiteboard` ## Retrieval Model `search_meetings` is not just a title filter. It is a semantic retrieval path over meeting content, recap-linked assets, and recording-linked artifacts. Useful result families: - recap-oriented results with AI summaries and linked assets - recording-oriented results for post-meeting content retrieval When writing parsers, validate the live response shape from the server rather than relying on older example field names. ## Feature Prerequisites AI Companion features such as **Smart Recording** and **Meeting Summary** are feature prerequisites for useful semantic retrieval and recap-linked content. They do not replace the required OAuth scopes. ## Error Layering Failures can happen at two layers: - MCP protocol layer (`-32001`, `-32602`, `-32603`) - underlying Zoom API-style permission/resource failures surfaced through the MCP response See [../references/error-codes.md](../references/error-codes.md). # OAuth Setup — Zoom MCP Server ## Overview The documented path for Zoom MCP is a **General app** using **user-level OAuth**. Each user authorizes with their own Zoom account, and the resulting bearer token is passed by the bundled connector in [`.mcp.json`](../../../.mcp.json). ## Step 1: Create a General App with User-Level OAuth 1. Go to [marketplace.zoom.us](https://marketplace.zoom.us) → **Develop** → **Build App**. 2. Create a **General app**. 3. Configure the app for **user-level OAuth** for the per-user MCP path. 4. Set a redirect URL for your client or local test environment. 5. Note the client ID and client secret. ### If You Do Not Already Have a Redirect Endpoint For development, two pragmatic options are: **Option 0: `localhost` and manually copy the code** Example: ```text http://localhost:3000/oauth/zoom/callback ``` If the local app does not actually handle the callback yet, the browser may show a failed page load. You can still copy the `code` and `state` values from the b