Design Mcp Workflow
- 1.5k installs
- 23.1k repo stars
- Updated July 28, 2026
- anthropics/knowledge-work-plugins
design-mcp-workflow is an agent skill for design zoom mcp workflows separating mcp tool responsibilities from rest apis.
About
The design-mcp-workflow skill is designed for design Zoom MCP workflows separating MCP tool responsibilities from REST APIs. 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 1. Invoke when the user designs Zoom MCP workflows or separates MCP from REST responsibilities.
- MCP fit assessment.
- REST API vs MCP boundaries.
- Hybrid architectures.
- Connector expectations.
- Whiteboard-specific MCP routing.
Design Mcp Workflow by the numbers
- 1,480 all-time installs (skills.sh)
- +89 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #217 of 2,742 Automation & Workflows skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
design-mcp-workflow capabilities & compatibility
- Capabilities
- mcp fit assessment · rest api vs mcp boundaries · hybrid architectures · connector expectations
What design-mcp-workflow says it does
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
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 responsibil
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill design-mcp-workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.5k |
|---|---|
| repo stars | ★ 23.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
How do I design zoom mcp workflows separating mcp tool responsibilities from rest apis?
Design Zoom MCP workflows separating MCP tool responsibilities from REST APIs.
Who is it for?
Teams planning MCP-based Zoom integrations before implementation.
Skip if: Skip for direct REST-only Zoom integrations without MCP design.
When should I use this skill?
User designs Zoom MCP workflows or separates MCP from REST responsibilities.
What you get
Completed design-mcp-workflow workflow with documented commands, files, and expected deliverables.
- MCP fit assessment
- REST versus MCP boundary map
By the numbers
- Workflow includes 2 decision steps: classify agentic vs deterministic needs, then route MCP-only work
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
1. Decide whether the problem is agentic tooling, deterministic automation, or both. 2. Route MCP-only tasks to zoom-mcp. 3. Route hybrid tasks to both zoom-mcp and rest-api. 4. If Whiteboard is central, route to zoom-mcp/whiteboard. 5. 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
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.577k39.1k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.471kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.471kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.470kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.470kLark Vc AgentGive their coding agent the ability to read, create, and update documents, tasks, and wiki pages inside Feishu (Lark).415kHow it compares
Pick design-mcp-workflow for pre-implementation architecture decisions; use REST SDK docs when endpoints and auth are already chosen.
FAQ
What does design-mcp-workflow do?
Design Zoom MCP workflows separating MCP tool responsibilities from REST APIs.
When should I use design-mcp-workflow?
User designs Zoom MCP workflows or separates MCP from REST responsibilities.
Is design-mcp-workflow safe to install?
Review the Security Audits panel on this page before installing in production.