Knowledge-work-plugins 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.

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/design-mcp-workflow" ~/.claude/skills/anthropics-knowledge-work-plugins-design-mcp-workflow && rm -rf "$T"

manifest: partner-built/zoom-plugin/skills/design-mcp-workflow/SKILL.md

source content

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

Decide whether the problem is agentic tooling, deterministic automation, or both.
Route MCP-only tasks to zoom-mcp.
Route hybrid tasks to both zoom-mcp and rest-api.
If Whiteboard is central, route to zoom-mcp/whiteboard.
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