Skip to main content
Book a demo

Connect Vimeo to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Vimeo 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 Vimeo in Runlayer

    Add Vimeo 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, Vimeo’s 33 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Vimeo

    Sign in the way Vimeo requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Vimeo from Claude Code

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

Tools

33 Vimeo tools in Claude Code

Runlayer policy decides which of these Claude Code users can call. 16 read data only and 4 can change or delete data.

  • Create editing session

    Create a new editing session, returning the session ID and storyboard ID.

  • Set single text

    Set text on the visual layer with specified timing.

  • Set all texts

    Set multiple texts on the visual layer with specified timings.

  • Set media

    Add media (image, video, or sound) to the appropriate layer based on file extension.

  • Save

    Save the current editing session.

  • Render

    Render the storyboard to a video file.

  • Check render progress

    Check the progress of the current storyboard render.

  • Search

    Search your organizational content library for any recorded material including all-hands meetings, presentations, tech talks, demos, tutorials, team communications, or company content.

See all 33 Vimeo 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 Vimeo 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