Design Mcp Workflow

anthropics/knowledge-work-pluginsOfficial

Helps you figure out when to use Zoom's MCP server versus their REST API, or both. If you're building agentic workflows where Claude needs to call Zoom tools, this walks through fit assessment and routing decisions. It explicitly separates deterministic automation (stay in REST) from interactive tool use (go MCP), which matters because a lot of people treat MCP as a blanket API replacement when it's really for dynamic, conversational tasks. The workflow is simple: assess the problem, route to the right skill, call out auth and transport assumptions. Honest take: this is meta tooling, so it's most useful if you're already familiar with MCP concepts and just need the decision tree.

skills.sh installs: 2.2K
GitHub stars: 35.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow --agent claude-code

Installs into .claude/skills of the current project.

Files

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.