Operational server reads schemas/project context, runs GROQ, creates and patches documents, generates images, manages datasets and releases, deploys schemas and Studio; Sanity Context supplies schema-aware read-only dataset access
Sanity
Curated anchor platform in composable content platform with material relevance to the Marcom operating stack and a first-party developer surface.
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Operational server reads schemas/project context, runs GROQ, creates and patches documents, generates images, manages datasets and releases, deploys schemas and Studio; Sanity Context supplies schema-aware read-only dataset access
No Sanity MCP write was verified; the documented MCP surface is read-only. Use a separately authorized API or the native UI for mutations and do not attribute those writes to MCP.
Official Sanity documentation confirms hosted OAuth or token authentication, active GA releases and MCP App widgets. Distinguish the broad operational server from Sanity Context, which is intentionally read-only and typically dataset-scoped.
Official Sanity documentation confirms hosted OAuth or token authentication, active GA releases and MCP App widgets. Distinguish the broad operational server from Sanity Context, which is intentionally read-only and typically dataset-scoped. Official Sanity documentation confirms hosted OAuth or token authentication, active GA releases and MCP App widgets. Distinguish the broad operational server from Sanity Context, which is intentionally read-only and typically dataset-scoped.
Official Sanity documentation confirms hosted OAuth or token authentication, active GA releases and MCP App widgets. Distinguish the broad operational server from Sanity Context, which is intentionally read-only and typically dataset-scoped.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
Role: provider
Read scope: Operational server reads schemas/project context, runs GROQ, creates and patches documents, generates images, manages datasets and releases, deploys schemas and Studio; Sanity Context supplies schema-aware read-only dataset access
Write scope: No MCP writes verified; the documented surface is read-only.
Authentication: Official Sanity documentation confirms hosted OAuth or token authentication, active GA releases and MCP App widgets.
Approval boundary: Official Sanity documentation confirms hosted OAuth or token authentication, active GA releases and MCP App widgets. Distinguish the broad operational server from Sanity Context, which is intentionally read-only and typically dataset-scoped.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Sanity ships these experiences.
Single-platform patterns
- Structured content production and governance studio
- Campaign asset assembly room
- Brief-to-experience studio
- Content approval queue
Multi-platform compositions
- Sanity + CRM or campaign platform: campaign asset assembly room
- Sanity + work-management system + analytics or distribution platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
6 recorded sources
Official Sanity documentation confirms hosted OAuth or token authentication, active GA releases and MCP App widgets. Distinguish the broad operational server from Sanity Context, which is intentionally read-only and…
- Publisher updated
- Jun 24, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
- Publisher updated
- Apr 15, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Apr 29, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Sanity's Query API retrieves Content Lake data with GROQ through GET or POST requests. GROQ is a structured query language, not SQL; private datasets, drafts, and versions require appropriate authentication and…
- Publisher updated
- Apr 15, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.