design-mcp-workflow
This skill helps design Zoom MCP workflows, assess MCP fit, and plan hybrid architectures. It enables developers to clearly separate MCP and REST API responsibilities for efficient AI tool integration.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill design-mcp-workflowBefore / After Comparison
1 组Developers often confuse MCP and REST API responsibilities when designing Zoom tool integration workflows, leading to rework and architectural confusion, taking an average of 4 hours to complete a workflow plan.
This skill provides clear MCP fit assessment and hybrid architecture guidance, helping developers quickly distinguish responsibilities, reducing planning time to 0.5 hours.
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
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill