Design MCP Workflow

From the author

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.

— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach for determining how to integrate Zoom capabilities into AI agent workflows. It helps developers decide when to leverage the Model Context Protocol (MCP) for agentic interactions versus using traditional REST APIs for deterministic automation. The workflow guides the user through assessing task requirements, defining architectural boundaries, and selecting the appropriate Zoom-related tools for specific use cases like whiteboard management or general API operations.

What it does

Assesses whether a task is better suited for agentic MCP tools or deterministic REST API calls.
Defines clear boundaries between MCP and REST API responsibilities.
Supports the design of hybrid architectures that combine both MCP and REST approaches.
Provides routing logic for specialized tasks like Zoom Whiteboard interactions.
Ensures transport, authentication, and client capability requirements are addressed during planning.

When to use it

When planning how an AI agent should interact with Zoom services.
When deciding if a specific Zoom task requires the flexibility of an MCP tool.
When designing a system that needs to balance agentic tool use with stable backend automation.
When determining the correct tool routing for Zoom Whiteboard operations.

Advantages

Prevents the misuse of MCP for tasks better handled by deterministic backend code.
Promotes a clear separation of concerns in integration architecture.
Helps avoid common pitfalls in API design and agentic tool implementation.
Ensures critical infrastructure requirements like authentication are considered early.

Usage examples

“How should I structure an agent workflow that needs to both list meetings and update whiteboard content?”: The skill will guide you to route the meeting listing to the appropriate Zoom MCP tool while directing the whiteboard update to the specific whiteboard-focused MCP component, ensuring a clean separation of concerns.
“Is it better to use an MCP tool or a REST API for a recurring daily report generation task?”: The workflow will help you identify this as a deterministic automation task, recommending the REST API approach over an MCP tool to ensure stability and reliability.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/design-mcp-workflow/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip design-mcp-workflow.zip -d .agents/skills

Documentation by Zoom

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

Files

ATTRIBUTION.mdAdded by AutoGineer994 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md1.2 KiB

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Wizard
Matt Pocock· Community
Generate interactive bash wizards to guide humans through complex manual setup, migration, or configuration tasks.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository317.5k
Emails
Corey Haines· Community
Design and optimize automated email sequences for onboarding, nurturing, and lifecycle management.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Conversion Tracking
Corey Haines· Community
A systematic approach to setting up, auditing, and verifying website conversion tracking across major ad platforms and analytics tools.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository59k
Directory Submissions
Corey Haines· Community
A strategic framework for submitting software products to directories to build backlinks, improve domain rating, and drive discovery.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITMedium riskGitHub stars of the source repository59k
Sms
Corey Haines· Community
Plan, build, and optimize compliant SMS, MMS, and WhatsApp marketing programs for high-engagement customer communication.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Marketing Loops
Corey Haines· Community
Orchestrate and schedule repeatable, self-running marketing workflows that operate on a defined cadence.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k