Zoom Plugin for Claude Code
The marketplace entry is named zoom-plugin. It is a development toolkit for planning, building, and debugging Zoom integrations across REST APIs, SDKs, webhooks, bots, and MCP workflows. It is not a general promise that Claude Code can search every meeting, recording, or transcript in a Zoom account.
Build and Debug Zoom Integrations with Claude Code
Plugin quick facts
| Item | Detail |
|---|---|
| Marketplace name | zoom-plugin |
| Publisher | Zoom |
| Install target | zoom-plugin@claude-plugins-official |
| Confirmed focus | REST APIs, SDKs, webhooks, bots, and MCP development |
| First check | Plan one sandbox integration before adding credentials |
| Documentation reviewed | September 16, 2026 |
Install and run a bounded first check
/plugin install zoom-plugin@claude-plugins-officialRestart Claude Code if the plugin does not appear in the active session. Begin with an architecture or endpoint-selection question that does not require an account token. Review the bundled tools and skills, then choose a Zoom development account before testing authenticated calls.
The plugin can help map a product requirement to a Zoom API or SDK surface, identify webhook events, inspect integration code, and prepare a test plan. Its usefulness comes from Zoom-specific development guidance, not unrestricted access to meeting content.
Configure Zoom API, SDK, Webhook, and MCP Credentials
Separate sandbox and production applications. Store client secrets, OAuth tokens, webhook secrets, and account identifiers outside prompts and repository files. Grant the smallest scopes required by the selected API or SDK flow.
For webhooks, define the endpoint, selected events, signature validation, retry handling, and secret rotation before enabling production delivery. For SDK work, record the target platform, supported version, authentication method, and test account. MCP development adds another boundary: inspect each exposed tool and its input schema before allowing writes.
From an Integration Requirement to a Tested Event Flow
Turn the feature request into one explicit path. For example, a meeting-created event may lead to a verified webhook payload, an idempotent handler, and a stored internal record. Name the triggering event, expected fields, state change, duplicate behavior, and failure response.
Use a sandbox account and one synthetic event. Capture the request, signature result, response code, downstream write, and retry behavior. A received webhook proves delivery to the endpoint; it does not prove that every downstream operation completed.
Protect OAuth Scopes, Tokens, and Production Accounts
Review code generated around authentication, callback URLs, token storage, logging, and account selection. Remove secrets from traces and fixtures. Require human approval before changing a production app, enabling a broader event subscription, or granting account-level administration.
Do not infer transcript or recording access from the plugin name. Those capabilities depend on a separate Zoom surface, account entitlement, artifact availability, and scopes. Use only tools that the installed plugin actually exposes.
Move a Verified Zoom Integration into a Verdent Plan
Once the sandbox flow works, Verdent can carry the implementation into a plan-build-verify loop. Include the selected Zoom surface, API or SDK version, scopes, event contract, acceptance tests, secret-handling rules, and rollout boundary. This keeps the engineering artifact specific instead of treating a generic meeting summary as a software specification.
Frequently Asked Questions
Is zoom-plugin a meeting-summary plugin?
No. The Claude Code marketplace entry is a development toolkit for planning, building, and debugging Zoom integrations. Meeting-content access is not an automatic capability of this entry.
How do I install the Zoom plugin for Claude Code?
Run /plugin install zoom-plugin@claude-plugins-official, then start a session with the installed plugin available. Inspect its tools before adding Zoom credentials.
Which Zoom development surfaces does it cover?
The marketplace entry covers REST APIs, SDKs, webhooks, bots, and MCP workflows. The exact guidance and tools available depend on the installed plugin version.
What should be reviewed before production use?
Review the Zoom app, scopes, callback URLs, token storage, webhook signatures, event subscriptions, retry behavior, logs, tests, and rollout plan. Keep production credentials out of prompts and source files.
Continue This Workflow With Verdent
Use this next step before moving the verified integration into implementation.