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.
Before using the bundled MCP servers, export bearer tokens for the Zoom surfaces you want Claude to use:
export ZOOM_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"
export ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"Explicit slash workflows implemented as skills under skills/:
| Workflow | Description |
|---|---|
/start |
Start with a Zoom app idea and get routed to the right product and build path |
/setup-zoom-oauth |
Choose the auth model, scopes, and redirect flow for a Zoom app |
/build-zoom-meeting-app |
Build an embedded or managed Zoom meeting flow |
/build-zoom-bot |
Build bots, recorders, and real-time meeting processors |
/debug-zoom |
Triage a broken Zoom integration and isolate the failing layer |
/setup-zoom-mcp |
Decide when Zoom MCP fits and set up a safe Claude workflow |
/build-zoom-rest-api-app |
Route into Zoom REST endpoints, scopes, and resource patterns |
/build-zoom-meeting-sdk-app |
Route into embedded Zoom meeting implementation details |
/build-zoom-video-sdk-app |
Route into custom video-session implementation details |
/setup-zoom-webhooks |
Set up Zoom webhook subscriptions, signature verification, and handlers |
/setup-zoom-websockets |
Set up Zoom WebSocket event delivery when it fits better than webhooks |
/build-zoom-team-chat-app |
Build Team Chat user or chatbot integrations |
/build-zoom-phone-integration |
Build Zoom Phone integrations around Smart Embed, APIs, and events |
/build-zoom-contact-center-app |
Build Contact Center app, web, or native integrations |
/build-zoom-virtual-agent |
Build Virtual Agent web or mobile wrapper integrations |
These remain in the plugin as automatic routing helpers, but they are no longer part of the public slash-command surface:
startplan-zoom-productplan-zoom-integrationchoose-zoom-approachdesign-mcp-workflowdebug-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/zoom-mcp/
/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
/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.
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/
│ ├── 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