Skip to main content
Book a demo

Connect Sanity to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add Sanity to Windsurf in four steps

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

  1. 1

    Add Sanity to Runlayer

    Sanity isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Windsurf to Runlayer

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

    Windsurf setup guide
  3. 3

    Sign in to Sanity

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

  4. 4

    Use Sanity from Windsurf

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

Tools

55 Sanity tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • Get UI context

    Returns UI enrichment data for widgets.

  • Add cors origin

    Adds CORS origin(s) to allow client-side requests to a Sanity project

  • Assets upload status

    Retrieve the status and result of your asset upload by operationId.

  • Delete cors origins

    Deletes a CORS origin from a Sanity project

  • List cors origins

    Lists all CORS origins configured for a Sanity project

  • Create dataset

    Creates a new dataset with specified name and access settings

  • Create documents

    Create one or more draft documents by directly providing structured content.

  • Create project

    Creates a new Sanity project and initializes it with a dataset and API tokens

See all 55 Sanity 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 Sanity 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