LoginSign Up
← Back to all sparks
S

Sanity

DEVOPS
Velocity8.8

Programmable headless content management system with structured content and the GROQ query language

www.sanity.io ↗

Sanity's MCP server ships nearly daily, building toward AI agents as first-class content operators

headless-cmsmcpai-agentscontent-managementdeveloper-tools
◆Current state
Sanity is a headless CMS that has been building its MCP server at an unusually fast cadence — five MCP releases in a single week in September. The MCP server now covers document creation, querying, patching, publishing, asset uploads from URLs, schema deployment, and most recently workflow authoring and deployment. Studio continues to ship stable bi-weekly updates, but the MCP investment is clearly the primary engineering priority.
◆Where it's heading
The MCP server is tracking toward full agentic content management. v2.35.0 workflow authoring — where agents can generate content workflows from descriptions and deploy new versions while live instances retain their original definition — is the clearest directional signal. The parallel work on access guidance, revision guards, and per-document error reporting is hardening the MCP surface for production environments where mistakes are costly. Sanity is building toward a CMS where AI agents are first-class operators, not just read-only query tools.
◆Prediction
The MCP server will expand into richer agentic orchestration — autonomous workflow execution, multi-document content operations with rollback safety, and deeper schema introspection to guide agent decisions. The permission hardening pattern in recent releases suggests enterprise customers are already running agents in production and surfacing edge cases.

◆Recent moves

  1. 15h ago

    Sanity MCP server v2.35.3: tool input compatibility fixes

    MCP server compatibility fixes — accepting JSON-stringified legacy input shapes and rejecting misplaced fields. Maintenance work that removes edge-case failures in tool call parsing rather than adding capability.

    View source ↗
  2. 23h ago

    Media Library v2026.09.23.draft: Media Library 2026-09-23

    Media Library gains folder descriptions and several reliability fixes — asset deletion safeguards when usage checks fail, filter menu rendering on small screens, and automatic reconnection after network interruptions. Incremental but directly usable improvements for teams managing large asset libraries.

    View source ↗
  3. 1d ago

    MCP server v2.35.2: Improved guidance for access/permissions issues and documents publishing lifecycle

    MCP server v2.35.2 adds detailed guidance for permission and access failures — explaining cross-org project access, draft vs. published document permissions, and linking agents to recovery paths when writes are denied. This hardening is consistent with agents running in production environments where clear error recovery matters.

    View source ↗
  4. 1d ago

    Sanity Studio v6.16.0: Unknown Portable Text values no longer crash the editor, plus auth, release, and presence fixes

    Studio v6.16.0 stops the Portable Text Editor from crashing on content whose schema has drifted — unknown values are now preserved and marked with a visible affordance rather than causing crashes. A meaningful reliability fix for content teams evolving their schemas in production.

    View source ↗
  5. 2d ago

    MCP server v2.35.1: Clearer errors and more reliable authorization

    MCP server v2.35.1 sharpens error messages for auth, project access, and GROQ syntax failures — GROQ errors now include the query with a position marker. Improved error quality is table stakes as agents encounter more edge cases in production.

    View source ↗
  6. 6d ago

    MCP server v2.35.0: Workflow authoring and asset upload improvements

    ⚡ SPARK

    MCP server v2.35.0 adds workflow authoring: agents can generate Sanity Workflows from descriptions, validate and deploy new versions, and run multiple versions concurrently while live instances retain their original definition. This is the sharpest shift in the MCP server's trajectory — from document CRUD to autonomous workflow creation and deployment.

    View source ↗