Skip to main content
Book a demo

Connect Zoom to Claude Code

Give Claude Code governed access to Zoom’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Code setup guide

Set up

Add Zoom to Claude Code in four steps

Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.

  1. 1

    Approve Zoom in Runlayer

    Add Zoom from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Zoom’s 20 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Zoom

    Each user signs in to Zoom with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Zoom from Claude Code

    Zoom’s approved tools appear in Claude Code. Every call is checked against policy and recorded.

Tools

20 Zoom tools in Claude Code

Runlayer policy decides which of these Claude Code 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

See all 20 Zoom tools

Control

What Runlayer can see and stop in Claude Code

Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.

  • Gateway policy (available)

    Every Zoom call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Claude Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination