Skip to main content
Book a demo

Connect Sanity to VS Code

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

Book a demo VS Code setup guide

Set up

Add Sanity 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

    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 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, Sanity’s 55 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 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 VS Code

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

Tools

55 Sanity tools in VS Code

Runlayer policy decides which of these VS Code 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 VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Sanity 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