
design-mcp-workflow
โ Officialโ 22,378by anthropic ยท part of anthropics/knowledge-work-plugins
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.
๐ฅ๐ฅ๐ฅโ VerifiedFreeQuick setup
๐งฉ One of 7 skills in the anthropics/knowledge-work-plugins package โ works on its own, and pairs well with its siblings.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
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.
Copy & paste โ that's it
npx skills add anthropics/knowledge-work-plugins --skill "design-mcp-workflow" --full-depthRun this in your project โ your agent picks the skill up automatically.
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
Licensed under Apache-2.0โ you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub โ