Agent skill · marketing growth · anthropics
zoom-mcp
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`.
Why this skill is useful
Provides specific guidance on using Zoom MCP connectors, including niche commands and authentication details not commonly known.
What it needs
Requires zoom account access. About 5k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
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: getmeetingassets searchmeetings getrecordingresource recordingslist Some MCP clients namespace server tools in the UI, for example zoom-mcp:recordingslist. 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: 2. Enable or restart the plugin so Claude restarts the bundled MCP server definition. 3. Verify discovery: Confirm the client can see recordingslist, searchmeetings, getmeetingassets, and getrecordingresource. 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: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/zoom-mcp