Skip to main content
Book a demo

Connect dbt to Windsurf

Give Windsurf governed access to dbt’s 42 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Windsurf setup guide

Set up

Add dbt to Windsurf in four steps

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

  1. 1

    Approve dbt in Runlayer

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

  2. 2

    Connect Windsurf to Runlayer

    Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches dbt’s 42 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf setup guide
  3. 3

    Sign in to dbt

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

  4. 4

    Use dbt from Windsurf

    dbt’s approved tools appear in Windsurf. Every call is checked against policy and recorded.

Tools

42 dbt tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • Cancel job run

    Cancel a currently running or queued dbt run.

  • Get all macros

    Get the name, description, and package name of all dbt macros in the environment.

  • Get all models

    Get the name and description of all dbt models in the environment.

  • Get all sources

    Get the name, description, and metadata of all dbt sources in the environment.

  • Get dimension values

    Get the distinct values for a given dimension, optionally scoped to specific metrics.

  • Get dimensions

    Get the dimensions for specified metrics

  • Get entities

    Get the entities for specified metrics

  • Get exposure details

    DEPRECATED — use get_node_details instead.

See all 42 dbt tools

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 dbt 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

Find another combination