Skip to main content
Book a demo

Connect Zoom to VS Code

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

Book a demo VS Code setup guide

Set up

Add Zoom to VS Code in four steps

Admins approve the server once. Everyone in VS 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 VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Zoom’s 20 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS 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 VS Code

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

Tools

20 Zoom tools in VS Code

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, VS 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.

  • Stop a call before it runs (available)

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

  • Block output after it runs (available)

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

  • Redact output in place (available)

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

Frequently asked questions

Connect more

Find another combination