Setup Zoom Mcp
Decide if Zoom MCP fits your AI workflow and output a minimal, auth-aware setup plan—including when to pair REST with MCP.
Overview
Setup Zoom MCP is an agent skill most often used in Validate (also Build integrations) that plans safe Zoom MCP adoption and hybrid REST boundaries for AI workflows.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill setup-zoom-mcpWhat is this skill?
- Five-step workflow: goal classification, MCP surface, hybrid REST split, auth/scope constraints, minimal POC sequence
- Outputs recommended MCP strategy, connector expectations, hybrid boundaries, risks, and related skill links
- Explicitly compares deterministic automation, AI tool orchestration, and hybrid architectures
- Argument hint accepts an AI workflow or MCP use case string via /setup-zoom-mcp
- Hands off to design-mcp-workflow and choose-zoom-approach skills for deeper design
- 5-step planning workflow ending in a minimal proof-of-concept sequence
Adoption & trust: 833 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want Zoom data in Claude but do not know whether MCP alone is enough, what auth scopes you need, or how to bound a risky first integration.
Who is it for?
Operators scoping Zoom-aware agents before committing engineering time to MCP connectors and OAuth.
Skip if: Teams that already finalized Zoom REST-only pipelines with no agent surface, or tasks that only need meeting URLs without API access.
When should I use this skill?
Planning AI workflows over Zoom data, deciding between MCP and REST, or defining a hybrid MCP architecture—with /setup-zoom-mcp and an AI workflow or MCP use case argument.
What do I get? / Deliverables
You leave with a recommended MCP strategy, connector expectations, hybrid REST responsibilities, risk notes, and a minimal proof-of-concept sequence plus links to follow-on design skills.
- Recommended MCP strategy document
- Hybrid REST versus MCP boundary list
- Minimal POC sequence and risk notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Choosing MCP versus REST and scoping Zoom access is pre-build validation—you prove the integration approach before wiring code. The skill produces strategy, connector expectations, hybrid boundaries, and a proof-of-concept sequence—classic scoping work before implementation.
Where it fits
Decide whether summarizing past Zoom recordings needs MCP tools only or a REST backfill job before you estimate build time.
Document which meeting lifecycle events stay on REST webhooks while Claude uses MCP for interactive lookups during support triage.
How it compares
Planning workflow for MCP setup decisions, not a drop-in Zoom REST client or meeting bot implementation.
Common Questions / FAQ
Who is setup-zoom-mcp for?
Solo builders and small teams designing Claude or knowledge-work automations that might read or act on Zoom via MCP connectors.
When should I use setup-zoom-mcp?
During Validate when scoping Zoom AI workflows, and during Build integrations when you need hybrid MCP plus REST boundaries before implementing connectors.
Is setup-zoom-mcp safe to install?
The skill plans auth and scope constraints but does not execute Zoom calls itself—review the Security Audits panel on this Prism page and your org’s Zoom app policies before enabling live connectors.
Workflow Chain
Then invoke: design mcp workflow, choose zoom approach
SKILL.md
READMESKILL.md - Setup Zoom Mcp
# /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)