Design MCP Workflow

anthropics/design-mcp-workflow

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.

303 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

23273

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill design-mcp-workflow

The instruction itself

4 sections, as written by the author

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

How to use it

Copy the folder

Take anthropics/design-mcp-workflow from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.