Back to Details

design-mcp-workflow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Design MCP Workflow

设计MCP工作流

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.
当用户希望Claude或其他支持MCP的客户端通过工具调用而非仅通过确定性API代码与Zoom交互时，可使用本技能。

Covers

覆盖场景

  • MCP fit assessment
  • REST API vs MCP boundaries
  • Hybrid architectures
  • Connector expectations
  • Whiteboard-specific MCP routing
  • MCP适配评估
  • REST API与MCP边界划分
  • 混合架构
  • 连接器预期
  • 白板专属MCP路由

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.
  1. 判断问题属于智能体工具类、确定性自动化类，还是两者兼有。
  2. 将仅需MCP的任务路由至zoom-mcp。
  3. 将混合任务同时路由至zoom-mcp和rest-api。
  4. 如果白板是核心功能，路由至zoom-mcp/whiteboard。
  5. 明确说明传输、身份验证及客户端能力的相关假设。

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
  • 针对应使用REST的确定性后端任务使用MCP
  • 将MCP视为所有API设计的替代方案
  • 忽略客户端传输支持及身份验证要求