Sanity MCP server

Enable AI agents to interact with your Sanity workspace through the Model Context Protocol (MCP).

The Sanity Model Context Protocol (MCP) server enables AI assistants like Claude Code and Cursor to interact directly with your Sanity projects.

With the MCP server, agents can go beyond code generation and perform advanced content management operations in your Sanity projects. Agents can execute GROQ queries, manage releases, and patch documents with full awareness of your schema, eliminating the need to manually supply context.

The Sanity MCP server is hosted on Sanity's own infrastructure on https://mcp.sanity.io. It follows Anthropic's official MCP specification and works with any MCP-compatible client. It supports authentication through both OAuth (default) and token-based authentication.

Prerequisites:

• An MCP-compatible client, such as Claude, ChatGPT, Cursor, VS Code, Lovable, Replit or v0
• A Sanity account

Sanity ships official connectors for Claude and ChatGPT. These are the fastest way to connect: install from the directory, authenticate with your Sanity account, and the hosted MCP server and our official agent skills are configured and kept up to date for you.

The Sanity connector in the Claude directory connects Claude to your Sanity content across Claude on the web, desktop, mobile and Claude Code CLI.

The Sanity plugin for ChatGPT connects Sanity to ChatGPT on the web, desktop, mobile and Codex CLI.

You can add the Sanity MCP server to all of your developer tools at once using the Sanity CLI. It detects the most common AI-powered editors (Cursor, VS Code, Claude Code) and automatically configures the MCP server for you.

npx sanity@latest mcp configure

pnpm dlx sanity@latest mcp configure

yarn dlx sanity@latest mcp configure

bunx sanity@latest mcp configure

Unlike the connectors above, this installs only the MCP server. Bundled agent toolkit extras like skills aren't included.

The Sanity MCP server works with any MCP-compatible agent. The following are setup instructions for common MCP clients.

/plugin install sanity@claude-plugins-official

claude mcp add Sanity -t http https://mcp.sanity.io --scope user

[mcp_servers.sanity]
url = "https://mcp.sanity.io"

codex mcp login sanity

{
  "mcpServers": {
    "Sanity": {
      "type": "http",
      "url": "https://mcp.sanity.io"
    }
  }
}

{
  "servers": {
    "Sanity": {
      "type": "http",
      "url": "https://mcp.sanity.io"
    }
  }
}

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sanity": {
      "type": "remote",
      "url": "https://mcp.sanity.io",
      "oauth": {}
    }
  }
}

{
  "mcpServers": {
    "Sanity": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.sanity.io",
        "--transport",
        "http-only"
      ]
    }
  }
}

The Sanity MCP server uses OAuth by default to perform operations on your behalf. You may instead provide an API token by setting the Authorization header in your MCP config. When configured with the header, the server will not use OAuth. Tool calls will use the API token in accordance with its role and scoped to its permissions.

{
  "mcpServers": {
    "Sanity": {
      "url": "https://mcp.sanity.io",
      "headers": {
        "Authorization": "Bearer sk..."
      }
    }
  }
}

You can create API tokens from sanity.io/manage or with the sanity CLI's tokens command. You can also provide a personal token, which will share your role and permissions, as well as link you to any changes in the revision history.

Once configured and started, authenticate with your Sanity credentials if prompted. You can then use natural language to work with Sanity development tasks, such as:

• Help me migrate this project to Sanity.
• Run a GROQ query for all articles written by Mark.
• Add localization to my article document type.
• Help me migrate existing content to a new schema shape.
• List all releases in this dataset.

mcp.sanity.io provides both editorial and development-focused tools for content operations, schema exploration, GROQ query execution, project management tasks such as creating and managing resources like datasets and API keys, and migration assistance. These tools allow your AI assistant to interact with your Sanity data directly.

The following is a list of available tools and their uses:

Most MCP tools are standard API calls and don't consume AI credits. The following tools invoke Sanity's AI inference endpoints and consume AI credits:

• generate_image
• transform_image
• create_version – only when the instruction parameter is provided

You can disable these tools in your MCP client if you want to avoid credit usage.

Learn more about pricing and quotas in How AI credits work.

If you encounter authentication errors (e.g., 401 Unauthorized), the solution depends on how you installed the server:

Installed via CLI (using token auth)

If you installed the MCP via the Sanity CLI, your authentication relies on a generated token that may have expired or been revoked. To fix this, simply run the configuration command again and re-select your code editor with space:

npx sanity@latest mcp configure

pnpm dlx sanity@latest mcp configure

yarn dlx sanity@latest mcp configure

bunx sanity@latest mcp configure

This will generate a fresh auth token and update your editor's configuration file automatically.

Manually configured (using OAuth)

If you configured the server manually, you are likely using OAuth. Sessions typically expire after 7 days. Your client should prompt you to re-authenticate, but if it gets stuck:

• VS Code: Run Authentication: Remove Dynamic Authentication Providers from the Command Palette, select the Sanity provider, and restart the server.
• Cursor: Run Cursor: Clear All MCP Tokens from the Command Palette to reset your session.

If specific tools (like query_documents) are missing or failing, verify that your account has the correct permissions for the project and dataset you are trying to access. The set of available tools may also vary as we release updates to the MCP server.

Join us in the Sanity community to ask questions and discuss our MCP server with other developers in the #mcp-server channel.