Skip to main content
Book a demo

Connect Sanity to Zed

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

Book a demo Zed setup guide

Set up

Add Sanity to Zed in four steps

Admins approve the server once. Everyone in Zed 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 Zed to Runlayer

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

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

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

Tools

55 Sanity tools in Zed

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

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

  • Gateway policy (available)

    Every Sanity call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination