setup-zoom-mcp — Claude Code skill: what it does, how to install
Helps decide whether Zoom MCP or a hybrid REST API fits your workflow, evaluates auth constraints, and drafts a PoC plan.
npx skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp -a claude-codeWhat setup-zoom-mcp does
The skill analyzes your Zoom workflow to classify it as deterministic automation, AI tool orchestration, or a hybrid setup. It details connector expectations, surface assumptions, and the exact boundaries where a standard REST API is required alongside MCP.
It flags constraints around authentication, scopes, and client capabilities before proposing a minimal proof-of-concept sequence. Without proper client support or required scopes, connector setups fail immediately, so identifying those risks early prevents architectural dead ends.
What it helps with
- decide between Zoom MCP, REST API, or a hybrid architecture
- outline auth, scope, and client capability constraints
- define separate responsibilities for REST endpoints and MCP tools
- generate a minimal proof-of-concept sequence for Zoom integration
Example prompts for the agent
- /setup-zoom-mcp meeting transcript search and AI summarization workflow
- /setup-zoom-mcp hybrid architecture for meeting scheduling and participant analysis
How to install setup-zoom-mcp
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp -a claude-code2Manually: put the files in place
~/.claude/skills/setup-zoom-mcp/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/setup-zoom-mcp/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp -a codex2Manually: put the files in place
.agents/skills/setup-zoom-mcp/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp -a cursor2Manually: put the files in place
.cursor/skills/setup-zoom-mcp/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins setup-zoom-mcp2Manually: put the files in place
.github/skills/setup-zoom-mcp/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path partner-built/zoom-plugin/skills/setup-zoom-mcpManually: put the files in place
.devin/skills/setup-zoom-mcp/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set89
The whole set →Similar
Questions about setup-zoom-mcp
How do I install setup-zoom-mcp in Claude Code?
Run npx skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp -a claude-code.
What does setup-zoom-mcp do?
It determines whether Zoom MCP suits your AI workflow, isolates REST API needs, and produces a safe setup plan with risks and next steps.
What constraints does the skill evaluate?
It inspects authentication models, permission scopes, transport assumptions, and client capabilities to prevent broken connector configurations.
Source text
SKILL.md · Apache-2.0
--- name: setup-zoom-mcp description: Decide when Zoom MCP is the right fit and produce a safe setup plan for Claude. Use when planning AI workflows over Zoom data, deciding between MCP and REST, or defining a hybrid MCP architecture. argument-hint: "<AI workflow or MCP use case>" --- # /setup-zoom-mcp > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Plan a Zoom MCP workflow and decide when to use MCP alone versus a hybrid REST API + MCP architecture. ## Usage ```text /setup-zoom-mcp $ARGUMENTS ``` ## Workflow 1. Determine whether the goal is deterministic automation, AI tool orchestration, or a hybrid. 2. If MCP is appropriate, identify the likely Zoom MCP surface and transport assumptions. 3. If MCP alone is not enough, define the REST API responsibilities separately. 4. Call out auth, scope, and client capability constraints. 5. End with a minimal proof-of-concept sequence. ## Output - Recommended MCP strategy - Connector expectations - Hybrid boundaries if REST is also required - Risks and setup notes - Relevant skill links ## Related Skills - [design-mcp-workflow](../design-mcp-workflow/SKILL.md) - [choose-zoom-approach](../choose-zoom-approach/SKILL.md)
© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins