design-mcp-workflow — Claude Code skill: plan MCP integration
This skill helps you decide whether a task needs MCP or REST API is enough, and plan a hybrid architecture. Use it when designing tool-based workflows for Claude.
npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -a claude-codeWhat design-mcp-workflow does
The skill walks you through the decision: determines if a task is agentic (needs tools), deterministic (automation), or both. Then routes work — sends MCP-only tasks to zoom-mcp, hybrid tasks to both services, and if Whiteboard is central, directs there via zoom-mcp/whiteboard.
As you design, the skill explicitly surfaces assumptions: transport, auth, client capabilities. This separates MCP from REST API at the architecture level, so you do not use MCP for deterministic backend jobs that belong in REST, and do not confuse MCP with replacing your entire API design.
Available on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
What it helps with
- assess whether MCP fits a specific task
- draw boundaries between MCP and REST API
- design a hybrid architecture with tools
- document assumptions about transport and auth
- route Whiteboard tasks to the right service
Example prompts for the agent
- I have a Zoom workflow in Claude, should I use MCP or REST API?
- Design an MCP workflow: agentic parts as tools, deterministic parts as API
- Help me separate MCP responsibility from REST in my architecture
How to install design-mcp-workflow
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -a claude-code2Manually: put the files in place
~/.claude/skills/design-mcp-workflow/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-mcp-workflow/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -a codex2Manually: put the files in place
.agents/skills/design-mcp-workflow/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -a cursor2Manually: put the files in place
.cursor/skills/design-mcp-workflow/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins design-mcp-workflow2Manually: put the files in place
.github/skills/design-mcp-workflow/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path partner-built/zoom-plugin/skills/design-mcp-workflowManually: put the files in place
.devin/skills/design-mcp-workflow/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set89
The whole set →Similar
Questions about design-mcp-workflow
How do I install design-mcp-workflow in Claude Code?
Run npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -a claude-code, then find the skill at ~/.claude/skills/design-mcp-workflow/SKILL.md.
When should I use design-mcp-workflow?
When you need to decide if MCP suits a task, plan a tool-based workflow for Claude, or separate responsibilities between MCP and REST API.
How is MCP different from REST API?
MCP is a tool interface for agentic tasks where Claude calls functions. REST API is deterministic code that follows a script. This skill helps you choose the right approach for each part of your workflow.
Source text
SKILL.md · Apache-2.0
--- 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 1. Decide whether the problem is agentic tooling, deterministic automation, or both. 2. Route MCP-only tasks to [zoom-mcp](../zoom-mcp/SKILL.md). 3. Route hybrid tasks to both [zoom-mcp](../zoom-mcp/SKILL.md) and [rest-api](../rest-api/SKILL.md). 4. If Whiteboard is central, route to [zoom-mcp/whiteboard](../zoom-mcp/whiteboard/SKILL.md). 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
© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins