design-mcp-workflow
anthropics/knowledge-work-plugins
Decide whether Zoom MCP fits your task and plan tool-based AI workflows.
What is design-mcp-workflow?
This skill helps you assess whether to use Zoom MCP (Model Context Protocol) for Claude interactions versus REST APIs, and how to architect hybrid solutions. Use it when planning agentic tooling, deterministic automation, or both.
- Evaluate whether a task is suited for MCP-based tool calls or deterministic API code
- Identify boundaries between MCP-only and REST API responsibilities
- Design hybrid architectures combining both approaches
- Route Whiteboard-specific tasks to appropriate MCP handlers
- Clarify transport, authentication, and client capability assumptions
How to install design-mcp-workflow
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill design-mcp-workflowHow to use design-mcp-workflow
- 1.Determine whether your use case requires agentic tooling, deterministic automation, or both
- 2.Assess client MCP support and authentication capabilities
- 3.Route MCP-only tasks to the zoom-mcp skill
- 4.Route hybrid tasks to both zoom-mcp and rest-api skills
- 5.If Whiteboard is central to your workflow, route to zoom-mcp/whiteboard
- 6.Document transport, auth, and client capability assumptions explicitly
Use cases
- Deciding whether to implement Zoom meeting automation as MCP tools or REST API calls
- Planning a workflow that needs both agentic decision-making and deterministic backend operations
- Designing Whiteboard collaboration features that require real-time tool interactions
- Architecting multi-client systems where some clients support MCP and others only REST
- Separating concerns between interactive Claude tasks and scheduled backend jobs
- AI workflow architects
- Backend engineers building Zoom integrations
- Teams planning MCP-capable Claude deployments
- Developers choosing between tool-based and API-based automation
design-mcp-workflow FAQ
Use MCP when Claude needs to make tool-based decisions interactively. Use REST APIs for deterministic backend automation. Use both for hybrid workflows where Claude makes decisions and triggers deterministic operations.
Avoid using MCP for deterministic backend jobs that should stay in REST, treating MCP as a replacement for all API design, and ignoring client transport support and authentication requirements.
If Whiteboard is central to your workflow, route to the zoom-mcp/whiteboard skill for specialized handling.
Explicitly document transport mechanisms, authentication methods, and client capability assumptions to avoid integration issues.
Full instructions (SKILL.md)
Source of truth, from anthropics/knowledge-work-plugins.
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
- 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
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.
design-system
Audit, document, or extend your design system with consistency checks and component documentation.
digest
Generate daily or weekly digests of activity across all connected sources to catch up on mentions, action items, and decisions.
discover-brand
Autonomously discover brand materials across enterprise platforms and generate structured brand guidelines.
documentation
Write and maintain technical documentation for APIs, READMEs, runbooks, and architecture guides.
draft-content
Draft marketing content tailored to your channel, audience, and brand voice with SEO guidance.
draft-offer
Draft complete offer letters with compensation packages, terms, and negotiation guidance for new hires.