zoom-mcp

zoom-mcp is a skill for Claude Code from zoom/zoom-plugin. It costs 66 tokens per session (3,353 once invoked), scanned A, original, MIT.

A reference guide for connecting coding agents to Zoom's MCP servers. Zoom is a meeting and collaboration service, and MCP lets an agent use connected tools.

In plain words
What is it for?
Use it to search meetings, retrieve recordings and meeting files, search Zoom content, and work with Zoom Docs, Chat, Canvas, Tasks, Revenue Accelerator, or Whiteboard.
Why use it?
It explains which Zoom tools and access permissions are available when planning or troubleshooting an integration.

Skill for Claude Code ✓ vendor

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is [Marketplace app management](../rest-api/references/marketplace-apps.md) to create or.

Part of the zoom-plugin plugin — 47 skills, 7 MCP servers shipped together

Good fit Use it to search meetings, retrieve recordings and meeting files, search Zoom content, and work with Zoom Docs, Chat, Canvas, Tasks, Revenue Accelerator, or Whiteboard.

Compare 6 skills from other repositories ↓
About the project

Zoom Plugin is a Claude plugin that helps plan, build, and debug Zoom integrations across APIs, SDKs, webhooks, bots, and MCP connections. It is for developers creating Zoom applications, with catalogue entries providing guidance, workflows, and MCP connectors for selecting and implementing the relevant Zoom products.

zoom/zoom-plugin · 7 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/zoom/zoom-plugin
agentmods
npx agentmods add skills/zoom/zoom-plugin/zoom-mcp

Made for: Claude Code.

Or install zoom-plugin, the plugin that ships this one along with the rest of its 47 skills, 7 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for zoom-mcp

README.md
[![agentmods](https://agentmods.dev/badge/skills/zoom/zoom-plugin/zoom-mcp/github.svg)](https://agentmods.dev/skills/zoom/zoom-plugin/zoom-mcp)
Your own site
<a href="https://agentmods.dev/skills/zoom/zoom-plugin/zoom-mcp"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/zoom-mcp/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for zoom-mcp

Your own site · 80×15
<a href="https://agentmods.dev/skills/zoom/zoom-plugin/zoom-mcp"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/zoom-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,353 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 270
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.03353
Opus 5.5 $0.00026 $0.01341
Sonnet 5.5 $0.00013 $0.00671
Haiku 4.5 $0.00007 $0.00335

Measured 1mo ago against content hash fb34ee56bddd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zoom-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/zoom-mcp/SKILL.md · 308 lines

How it starts

The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Zoom MCP

Guidance for the bundled Zoom MCP connector in this Claude plugin. Prefer design-mcp-workflow or setup-zoom-mcp first, then route here for tool-surface details, auth expectations, and MCP-specific constraints.

Zoom MCP Server

Zoom's current hosted MCP catalog uses mcp.zoom.us for AI-agent access to:

  • semantic meeting search
  • cross-Zoom search over Team Chat messages, Zoom Docs, and My Notes
  • meeting-linked asset retrieval
  • recording resource retrieval
  • Zoom Docs and Hub content creation and retrieval
  • Canvas, Chat, Tasks, Revenue Accelerator, and Whiteboard product workflows

The complete current server and scope inventory is in references/servers.md. The dedicated /mcp/docs path and the former /mcp/team_chat path are retained only as legacy compatibility references; use Canvas and Chat for new integrations.

Current tool names from the main Zoom MCP server, verified by tools/list:

  • create_new_file_with_markdown
  • get_file_content
  • get_meeting_assets
  • get_recording_resource
  • hub_create_file_from_content
  • hub_get_file_content
  • recordings_list
  • search_meetings
  • search_zoom

Some MCP clients namespace server tools in the UI, for example zoom-mcp:recordings_list. Treat the raw tool names above as authoritative.

Docs-specific MCP work can use the main zoom-mcp server or the current Zoom Canvas MCP server; use the exact tool names exposed by the active server.

Whiteboard-specific MCP work is covered by the dedicated skill whiteboard/SKILL.md.

Product-specific Chat MCP work is covered by the child skill team-chat/SKILL.md. The folder name is retained for compatibility with existing links; the current official server is Zoom Chat at /mcp/chat/streamable.

Need the OAuth app/scopes first? Use Marketplace app management to create or validate the General App, select user/admin scopes for MCP tools, and understand credential response shapes before minting the bearer token passed to the MCP server. Start from the default Zoom MCP template, or select the matching Meetings, Canvas, Chat, Tasks, Revenue Accelerator, or Whiteboard template from the Marketplace template selector. Automated selection must inspect the template index and require app_type: general, usage: USER_OPERATION, and supports_manifest_update: true.

Read the full file on GitHub · 308 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 308 lines · 66 tokens per session scan A fb34ee56bddd

Subscribe to this mod's changes

zoom-mcp is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 21d ago), licensed MIT. It adds 66 tokens to every session and 3,353 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens