Design MCP Workflow

Design a Zoom MCP workflow for Claude. Use when deciding whether Zoom MCP fits a task, when planning tool-based AI workflows, or when separating MCP responsibilities from REST API responsibilities.

zoom 746f2e5 1.3 KB Updated

File contents

Design MCP Workflow

Use this skill when the user wants Claude or another MCP-capable client to interact with Zoom via tool calls instead of only deterministic API code.

Covers

  • MCP fit assessment
  • REST API vs MCP boundaries
  • Hybrid architectures
  • Connector expectations
  • Whiteboard-specific MCP routing

Workflow

  1. Decide whether the problem is agentic tooling, deterministic automation, or both.
  2. Route MCP-only tasks to zoom-mcp.
  3. Route hybrid tasks to both zoom-mcp and rest-api.
  4. If Whiteboard is central, route to zoom-mcp/whiteboard.
  5. If the client needs manual app registration, route to setup-zoom-marketplace-app and select the matching MCP template.
  6. Call out transport, auth, and client capability assumptions explicitly.

Common Mistakes

  • Using MCP for deterministic backend jobs that should stay in REST
  • Treating MCP as a replacement for all API design
  • Ignoring client transport support and auth requirements

zoom/zoom-plugin/tree/main/skills/design-mcp-workflow commit 746f2e5d01

Frequently asked questions

npx skillmds@latest add zoom/design-mcp-workflow