mcpField
D
design-mcp-workflow

design-mcp-workflow

github.com/anthropicsAgent workflows33.6k2.2k installsUpdated 1d ago
Repository

About design-mcp-workflow

A skill for deciding when Claude or another MCP-capable client should use Zoom MCP, REST API, or both. It covers routing choices, Whiteboard-specific handling, and assumptions about transport, authentication, and client capabilities.

Key features

  1. 01MCP fit assessment
  2. 02REST and MCP boundary guidance
  3. 03Hybrid workflow routing
  4. 04Whiteboard-specific routing
  5. 05Transport and auth assumptions

Use cases

  1. 01Choosing MCP or REST for a Zoom task
  2. 02Combining MCP tools with REST automation
  3. 03Routing Whiteboard requests to the right surface

MCP support

Guides MCP-capable clients on when to route Zoom tasks to zoom-mcp, use REST API, or combine the two.

Install

Copy the command and run it in a terminal.

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

After installing, type/design-mcp-workflowin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported