Skip to main content
Book a demo

Connect Cloudflare Workers Builds to VS Code

Give VS Code governed access to Cloudflare Workers Builds through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Cloudflare Workers Builds 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 Cloudflare Workers Builds in Runlayer

    Add Cloudflare Workers Builds 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, Cloudflare Workers Builds’s 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 Cloudflare Workers Builds

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

  4. 4

    Use Cloudflare Workers Builds from VS Code

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

Tools

Cloudflare Workers Builds tools in VS Code

Cloudflare Workers Builds reports its tools when your organization connects it, so the list depends on your deployment.

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 Cloudflare Workers Builds 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