Knowledge-work-plugins setup-zoom-mcp
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.
install
source · Clone the upstream repo
git clone https://github.com/anthropics/knowledge-work-plugins
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/anthropics/knowledge-work-plugins "$T" && mkdir -p ~/.claude/skills && cp -r "$T/partner-built/zoom-plugin/skills/setup-zoom-mcp" ~/.claude/skills/anthropics-knowledge-work-plugins-setup-zoom-mcp && rm -rf "$T"
manifest:
partner-built/zoom-plugin/skills/setup-zoom-mcp/SKILL.mdsource content
/setup-zoom-mcp
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Plan a Zoom MCP workflow and decide when to use MCP alone versus a hybrid REST API + MCP architecture.
Usage
/setup-zoom-mcp $ARGUMENTS
Workflow
- Determine whether the goal is deterministic automation, AI tool orchestration, or a hybrid.
- If MCP is appropriate, identify the likely Zoom MCP surface and transport assumptions.
- If MCP alone is not enough, define the REST API responsibilities separately.
- Call out auth, scope, and client capability constraints.
- 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