---
id: gh-design-mcp-workflow
name: "design-mcp-workflow"
url: https://skills.yangsir.net/skill/gh-design-mcp-workflow
author: anthropics
domain: ai-agent-external-interaction
tags: ["mcp", "workflow-design", "ai-agent", "zoom", "tool-integration"]
install_count: 2100
rating: 4.30 (120 reviews)
github: https://github.com/anthropics/knowledge-work-plugins/tree/main/partner-built/zoom-plugin/skills/design-mcp-workflow
---

# design-mcp-workflow

> 此技能用于设计Zoom MCP工作流，评估MCP适用性并规划混合架构，帮助开发者区分MCP与REST API职责，实现高效的AI工具集成。

**Stats**: 2,100 installs · 4.3/5 (120 reviews)

## Before / After 对比

### 工作流规划时间

**Before**:

开发者在设计Zoom工具集成的工作流时，常常混淆MCP和REST API的职责，导致后期返工和架构混乱，平均需要4小时才能完成一个工作流规划。

**After**:

此技能通过清晰的MCP适用性评估和混合架构指导，帮助开发者快速区分职责，将工作流规划时间缩短至0.5小时。

| Metric | Before | After | Change |
|---|---|---|---|
| 规划时间 | 4小时 | 0.5小时 | -88% |

## 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](../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


---
*Source: https://skills.yangsir.net/skill/gh-design-mcp-workflow*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-design-mcp-workflow/markdown*