Skip to main content

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.

Source facts

Repository
anthropics/knowledge-work-plugins
Last source activity
April 9, 2026 at 23:28
Detected SKILL.md language
English
Stars
32,945
Forks
3,632

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
design-mcp-workflow
description
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.
user-invocable
false
# 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](../zoom-mcp/SKILL.md). 3. Route hybrid tasks to both [zoom-mcp](../zoom-mcp/SKILL.md) and [rest-api](../rest-api/SKILL.md). 4. If Whiteboard is central, route to [zoom-mcp/whiteboard](../zoom-mcp/whiteboard/SKILL.md). 5. 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
View on GitHub