Sanity CMS
The Sanity MCP Server provides AI assistants with direct access to Sanity CMS content management capabilities through a TypeScript implementation. Developed by Sanity.io, it enables creating, querying, and managing content with tools for documents, datasets, schemas, releases, and embeddings. The server enforces an initial context workflow, supports different user roles (developer, editor, agent), and includes specialized tools for GROQ queries and semantic search. Built on the @modelcontextprotocol/sdk, it communicates via stdio and authenticates with the Sanity API using environment variables. This implementation is particularly valuable for content managers and developers who need to maintain their Sanity projects without switching contexts from their AI assistant.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- ai-ml
- Source
- PulseMCP
- Repository
- github.com/sanity-io/sanity-mcp-server
- Author type
- human
- Updated
- 2026-04-25
Use via MCP
Resolve Sanity CMS from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.