01 · Records and state owned
Projects, datasets, schemas, GROQ queries, documents, drafts and versions, releases, generated or transformed images, and Studio or schema deployments.
Sanity
Sanity
Included because its hosted MCP gives agents schema-aware access to structured content, GROQ queries, releases, datasets, schema deployment, and media operations under Sanity roles and revision history.
Content, CMS, creative & DAMSystem of productionBYO-UI-ready platform
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.
02 · Data you can retrieve
Inspect project and schema context, execute GROQ, query documents, list datasets and releases, and search Sanity documentation with the authenticated actor's scope.
03 · Actions and write paths
Create, patch, publish, unpublish, and delete documents; create projects and manage datasets; create, schedule, and publish releases; deploy schemas; and generate or transform images.
04 · Authentication and permissions
The hosted server uses OAuth by default or a bearer API token. Calls inherit the OAuth user's permissions or the token's role and scopes; a personal token also attributes changes in revision history.
05 · Monitoring, approval, and recovery
Use a named user or narrowly scoped token so revisions remain attributable; limit project and dataset access through Sanity roles, and disable credit-consuming image or version-generation tools in the client when they are not needed.
06 · Limits and caveats
OAuth sessions typically expire after seven days, available tools can change as the hosted service updates, and image generation, image transformation, and instructed version creation can consume AI credits.
First-party access
Documented surfaces
GROQ structured query ↗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 permissions.Source: Query API referenceMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP support
Official MCP serverSanity-hosted operational MCP plus separate Sanity Context read-only MCPGeneral availability with active 2026 releases
Support: Official MCP server
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: The operational Sanity MCP can deploy schemas and Studio, create/patch/publish/unpublish content, discard drafts/versions, create projects and datasets, update dataset access, and manage releases subject to OAuth or token role permissions. Sanity Context remains a distinct read-only surface.
Authentication: Hosted OAuth is the default. A client can instead send an Authorization bearer token, in which case OAuth is not used.
Approval boundary: Require a preview and explicit confirmation before publish, unpublish, permanent document deletion, release publication, dataset-access changes, or schema and Studio deployment.
Protocol does not erase product boundaries.
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.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability4
Observability3
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Sanity ships them.
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
MCPRepresentative source
https://www.sanity.io/docs/ai/mcp-server ↗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 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://www.sanity.io/docs/http-reference ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Apr 15, 2026
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Developer docsSource inventory
https://www.sanity.io/docs ↗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.
Developer docsSource inventory
https://www.sanity.io/docs/http-reference/query ↗Reverified the named access facet exactly as bounded by the reviewed first-party record.
- Publisher published
- Apr 15, 2026
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
HomepageSource inventory
https://www.sanity.io/ ↗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.
Webhooks / extensionsSource inventory
https://www.sanity.io/docs/webhooks ↗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.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
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.