setup-zoom-mcp

The setup-zoom-mcp skill helps decide when Zoom's Model Context Protocol (MCP) surface is the right choice and produces a safe setup plan for using it with Claude. It addresses the architectural question that arises when planning AI workflows over Zoom data: should the workflow use MCP alone, the Zoom REST API alone, or a hybrid of both. The skill exists to prevent teams from reaching for MCP where deterministic REST automation would be more appropriate, and vice versa.

The workflow first determines whether the goal is deterministic automation, AI tool orchestration, or a hybrid. If MCP is appropriate, it identifies the likely Zoom MCP surface and transport assumptions. If MCP alone is insufficient, it defines the REST API responsibilities separately, and it calls out auth, scope, and client capability constraints throughout. It closes by outlining a minimal proof-of-concept sequence. The output is a recommended MCP strategy, connector expectations, hybrid boundaries when REST is also required, risks and setup notes, and links to related skills such as design-mcp-workflow and choose-zoom-approach.

This is a decision-and-planning skill within the Zoom partner plugin. It does not run tools or handle credentials directly; it references a CONNECTORS.md file for checking which tools are connected. Its intended users are developers and AI engineers designing agentic or hybrid retrieval workflows over Zoom data who need guidance on the MCP-versus-REST tradeoff and a safe, minimal starting architecture.