Connect Vimeo to Windsurf
Give Windsurf governed access to Vimeo’s 33 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Vimeo to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Approve Vimeo in Runlayer
Add Vimeo from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Vimeo’s 33 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 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
Use Vimeo from Windsurf
Vimeo’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
33 Vimeo tools in Windsurf
Runlayer policy decides which of these Windsurf 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.
Control
What Runlayer can see and stop in Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Vimeo call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf 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 Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more