Connect Zoom to Claude
Give Claude governed access to Zoom’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Zoom to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 1
Approve Zoom in Runlayer
Add Zoom from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Zoom’s 20 tools show up in Claude’s own tool list.
Claude setup guide - 3
Sign in to Zoom
Each user signs in to Zoom with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Zoom from Claude
Zoom’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
20 Zoom tools in Claude
Runlayer policy decides which of these Claude users can call.
Ask
READ-ONLY
Canvas add file collaborators
Adds collaborators (Zoom users, Team Chat channels, or email addresses) to a Zoom Canvas (formerly Zoom Docs) file, granting them a specified access role.
Canvas list file collaborators
Retrieves the list of collaborators for a specified Zoom Canvas (formerly Zoom Docs) file (supports doc and data table file types only).
Canvas modify file collaborator role
Modifies the role of an existing collaborator on a Zoom Canvas (formerly Zoom Docs) file.
Canvas remove file collaborator
Removes a specified collaborator from a file in Zoom Canvas (formerly Zoom Docs).
Create new file with markdown
⚠️ DEPRECATED: This tool has been replaced by hub_create_file_from_content.
Get file content
[DEPRECATED] This tool is deprecated.
Get meeting assets
READ-ONLY
Control
What Runlayer can see and stop in Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Zoom call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more