Zoom Plugin

A Claude plugin for planning, building, and debugging Zoom integrations. It helps choose the right Zoom surface, shape implementations, debug failures, and route into the right Zoom references without making the user read the whole doc tree first.

Install this directory as a local Claude plugin. The plugin manifest is at .claude-plugin/plugin.json and the bundled Zoom MCP connectors are defined in .mcp.json.

Authentication path depends on the Claude product:

• Claude Cowork: use the published Zoom connector in Claude's connector directory and complete OAuth there.
• Claude Code: complete Zoom user-level OAuth yourself, export bearer tokens for the Zoom surfaces you want Claude to use, then reconnect the plugin and use /setup-zoom-mcp.

For Claude Code, export the bearer tokens before using the bundled MCP servers:

export ZOOM_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
export ZOOM_MEETINGS_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
export ZOOM_CANVAS_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
export ZOOM_CHAT_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
export ZOOM_TASKS_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
export ZOOM_REVENUE_ACCELERATOR_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
export ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"

The same access token can be assigned to each variable when the General App includes the scopes required by all selected MCP servers. Use separate tokens if you want to keep server permissions isolated.

Explicit slash workflows implemented as skills under skills/:

These remain in the plugin as automatic routing helpers, but they are no longer part of the public slash-command surface:

• start
• plan-zoom-product
• plan-zoom-integration
• choose-zoom-approach
• design-mcp-workflow
• debug-zoom-integration

The plugin also keeps the original Zoom product-specific reference library under skills/. These are supporting references, not the primary entry surface:

• skills/general/
• skills/rest-api/
• skills/meeting-sdk/
• skills/video-sdk/
• skills/webhooks/
• skills/websockets/
• skills/oauth/
• skills/team-chat/
• skills/scribe/
• skills/summarizer/
• skills/translator/
• skills/zoom-mcp/
• skills/zoom-mcp/team-chat/
• skills/zoom-mcp/whiteboard/
• skills/zoom-mcp/references/servers.md

/start Build an internal meeting assistant that joins calls, extracts action items, and stores summaries

/start Build a React app that lets customers schedule and join Zoom meetings from our product

/setup-zoom-marketplace-app Create the minimum user-managed General App manifest for a meeting API workflow with webhooks

For programmatic Marketplace app creation from Claude Code, register the separately hosted helper MCP server first:

claude mcp add --transport http \
  zoom-marketplace-helper \
  https://marketplacehelper.asdc.cc/mcp

Then run /setup-zoom-marketplace-app. When the helper tools are connected, the skill selects zoom-marketplace-helper automatically, previews the intended account change, asks for confirmation, and verifies the resulting app after the write. The helper is external to this plugin and its MCP endpoint must already be reachable by Claude Code. If the helper endpoint changes, re-register the Claude Code MCP server with the new /mcp URL. This helper URL only connects Claude Code to the helper. Never use it, the helper operator's OAuth client ID, or the helper operator's OAuth callback in a Marketplace app created for a user. That app must use the user's own credentials and HTTPS endpoints.

If you do not have an existing HTTPS server for the app yet, expose your local app with a temporary tunnel before creating the Marketplace app. This lets you test the OAuth redirect, Zoom App home URL, and webhook endpoints through the app you are running locally.

Start the app locally, for example on port 3000, then choose one tunnel:

# ngrok
ngrok http 3000

# Or Cloudflare Tunnel
cloudflared tunnel --url http://localhost:3000

Use the HTTPS tunnel URL in the app configuration, with the actual routes implemented by your local server. For example:

Home URL:              https://YOUR_TUNNEL_HOST/
OAuth redirect URL:    https://YOUR_TUNNEL_HOST/oauth/callback
Webhook endpoint URL:  https://YOUR_TUNNEL_HOST/webhooks/zoom

If the user already has a hosted HTTPS service, use its routes instead. Build the OAuth authorization URL with the client ID Zoom issues for the user's app and the exact redirect URL configured for that app. Do not copy a maintainer, helper, sample, or previous user's OAuth URL.

The tunnel only forwards requests; it does not create these routes or handle OAuth and webhook validation for you. Free or ephemeral tunnel URLs can change, so update the Marketplace app configuration and any generated manifest values whenever the tunnel hostname changes. Use a deployed HTTPS service or a reserved tunnel hostname when the URL must remain stable.

Before asking zoom-marketplace-helper to create or update the app, provide the current tunnel host and route paths. After every tunnel restart, update the development OAuth redirect URL and OAuth allow list, development home URL, and development webhook URL before testing. Keep the production URLs unchanged unless you intentionally want to test the tunnel as production.

The app tunnel and the helper MCP endpoint are separate concerns and their URLs are not interchangeable. If both are running locally, each service needs a publicly reachable HTTPS URL, or the helper can be deployed while only the app uses a local tunnel.

/debug-zoom My Zoom webhook signature verification fails in production but not locally

/setup-zoom-mcp I want Claude to search meetings, pull recording resources, and create follow-up docs

See CONNECTORS.md. The plugin works standalone from the bundled skills, and gets supercharged when Claude can use the bundled Zoom MCP servers from .mcp.json.

The current official Zoom MCP catalog contains the main Zoom MCP, Meetings, Canvas, Chat, Tasks, Revenue Accelerator, and Whiteboard servers. All 7 current server definitions are bundled in .mcp.json; the complete inventory and current endpoints are in skills/zoom-mcp/references/servers.md. For new document workflows, prefer Zoom Canvas MCP. For new chat workflows, prefer Zoom Chat MCP.

This repo is packaged first as a Claude plugin, but it also includes AGENTS.md for agent ecosystems that use a repo-level discovery file. The reusable core remains the skills/ tree and its SKILL.md files.

Zoom Plugin/
├── .claude-plugin/plugin.json
├── .mcp.json
├── CONNECTORS.md
├── skills/
│   ├── plan-zoom-product/
│   ├── plan-zoom-integration/
│   ├── debug-zoom/
│   ├── setup-zoom-mcp/
│   ├── scribe/
│   ├── summarizer/
│   ├── translator/
│   ├── start/
│   ├── choose-zoom-approach/
│   ├── setup-zoom-oauth/
│   ├── build-zoom-meeting-app/
│   ├── build-zoom-bot/
│   ├── design-mcp-workflow/
│   ├── debug-zoom-integration/
│   └── ... existing Zoom reference skills
└── README.md

MIT