Skip to content
Business
Skill

/setup-zoom-mcp

Decide when Zoom MCP is the right fit and produce a safe setup plan for Claude. Use when planning AI workflows over Zoom data, deciding between MCP and REST, or defining a hybrid MCP architecture.

From plugin
knowledge-work-plugins
24k192 skills5 agents15 commands40 MCP
Install
$ npx -y skills add anthropics/knowledge-work-plugins --skill setup-zoom-mcp --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/setup-zoom-mcp

Context preview

The summary Claude sees to decide when to auto-load this skill.

Decide when Zoom MCP is the right fit and produce a safe setup plan for Claude. Use when planning AI workflows over Zoom data, deciding between MCP and REST, or defining a hybrid MCP architecture.

SKILL.md

setup-zoom-mcp.SKILL.md
name: setup-zoom-mcp
description: Decide when Zoom MCP is the right fit and produce a safe setup plan for Claude. Use when planning AI workflows over Zoom data, deciding between MCP and REST, or defining a hybrid MCP architecture.
argument-hint: "<AI workflow or MCP use case>"

/setup-zoom-mcp

> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).

Plan a Zoom MCP workflow and decide when to use MCP alone versus a hybrid REST API + MCP architecture.

Usage

/setup-zoom-mcp $ARGUMENTS

Workflow

1. Determine whether the goal is deterministic automation, AI tool orchestration, or a hybrid. 2. If MCP is appropriate, identify the likely Zoom MCP surface and transport assumptions. 3. If MCP alone is not enough, define the REST API responsibilities separately. 4. Call out auth, scope, and client capability constraints. 5. End with a minimal proof-of-concept sequence.

Output

  • Recommended MCP strategy
  • Connector expectations
  • Hybrid boundaries if REST is also required
  • Risks and setup notes
  • Relevant skill links

Related Skills

  • [design-mcp-workflow](../design-mcp-workflow/SKILL.md)
  • [choose-zoom-approach](../choose-zoom-approach/SKILL.md)
Ships withknowledge-work-plugins

Plugins that turn Claude into a specialist for your role, team, and company. Built for Claude Cowork, also compatible with Claude Code.

Get the whole plugin

Other skills on knowledge-work-plugins.