Sanity

Sanity

Official

Query and edit Sanity content over a remote OAuth MCP — no token in a config file.

Score 75(?)Sanity183Verified Top MCPs for Website Builders and CMS →

Quick answer

What it does

Gives agents access to Sanity projects: browse datasets and schema, query and read documents, create and patch drafts, and work with releases. Configuration is one URL plus an OAuth authorization, or `npx sanity@latest mcp configure` to wire it up from an already-logged-in CLI.

Best for

  • GROQ-shaped content queries from an agent
  • Drafting and patching documents
  • Schema-aware content audits
  • OAuth instead of a stored project token

Not for

  • Page layout and design
  • Self-hosted-only requirements

Source: top-mcps.com/mcp/sanity — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "sanity": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://mcp.sanity.io"
          ]
        }
      }
    }

    Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.sanity.io. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI or .mcp.json
    claude mcp add --transport http sanity https://mcp.sanity.io

    Then run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .cursor/mcp.json
    {
      "mcpServers": {
        "sanity": {
          "url": "https://mcp.sanity.io"
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

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

    VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "sanity": {
          "serverUrl": "https://mcp.sanity.io"
        }
      }
    }

    Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "sanity": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://mcp.sanity.io"
          ]
        }
      }
    }

    Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "streamable-http",
              "url": "https://mcp.sanity.io"
            }
          }
        ]
      }
    }

    Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI
    codex mcp add sanity --url https://mcp.sanity.io

    Codex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "sanity": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://mcp.sanity.io"
            ]
          }
        }
      }
    }

    Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ChatGPT → Settings → Connectors (remote URL)
    {
      "name": "Sanity",
      "transport": "http",
      "url": "https://mcp.sanity.io"
    }

    Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Read + write
Sandbox
Datasets are the isolation boundary — point the agent at a development dataset before production.
Gotchas
  • OAuth grants the signed-in user's access, which on a personal account is usually every project you can see. Authorize from an account scoped to the project you mean.
  • The local `@sanity/mcp-server` npm package is published as DEPRECATED and tells you to use the hosted endpoint. Anything still pinned to it is running unmaintained code.
  • Drafts and published documents are different records in Sanity. An agent that patches the published document bypasses the draft review step entirely.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. website builders work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-website-builders
Compare Sanity against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Sanity MCP vs [Contentful MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/sanity
- top-mcps.com listing for Contentful
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Sanity MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/sanity (fetch https://top-mcps.com/mcp/sanity.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 1 update tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

More Website Builders MCPs

Other tools in the same category worth evaluating.

Hostinger
Official

Buy a domain, provision hosting, deploy a site, and set its DNS — one official server covering the whole chain, now through three search-and-execute tools.

hostinger, domains, web-hosting, dns
10 minMedium
Webflow
Official

Edit a live Webflow site from an agent — CMS collections, pages, and the Designer canvas over OAuth.

webflow, website-builders, cms, no-code
10 minMedium
Contentful
Official

Model, write and publish structured content from an agent — 73 tools across entries, assets and content types.

contentful, cms, headless-cms, website-builders
10 minMedium

Compared with Sanity

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Website Builders and CMS? See all Website Builders MCPs →