zoom-plugin

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.

Installation

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_DOCS_MCP_ACCESS_TOKEN="your_zoom_docs_mcp_access_token"
export ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN="your_zoom_user_oauth_access_token"

Slash Workflows

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

Internal Routing 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

Deep References

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/

Example Workflows

Starting from a Zoom app idea

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

Planning a new app

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

Debugging a broken webhook

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

Designing an MCP flow

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

Connectors