Connect Sanity to Claude
Give Claude governed access to Sanity’s 55 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Sanity to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 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
Connect Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Sanity’s 55 tools show up in Claude’s own tool list.
Claude setup guide - 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
Use Sanity from Claude
Sanity’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
55 Sanity tools in Claude
Runlayer policy decides which of these Claude 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
Control
What Runlayer can see and stop in Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Sanity call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more