Sanity MCP Server
Official# Sanity MCP Server
> **This local MCP server (`@sanity/mcp-server`) has been deprecated** in favor of the new, improved remote MCP server at [mcp.sanity.io](https://mcp.sanity.io). This repository is archived and no longer maintained.
## Use [mcp.sanity.io](https://mcp.sanity.io)
The Sanity MCP Server is now available as a hosted remote server at **[mcp.sanity.io](https://mcp.sanity.io)**. It offers:
- Streamable HTTP transport
- OAuth authentication (no API tokens to manage)
- Continuously updated tools and features
- Zero local setup — no Node.js required
### Quick setup
Add this to your MCP client configuration:
```json
{
"mcpServers": {
"sanity": {
"url": "https://mcp.sanity.io",
"type": "http"
}
}
}
```
Visit **[mcp.sanity.io](https://mcp.sanity.io)** for full installation instructions for Claude Code, Cursor, VS Code, and other MCP clients.
TDQS
Scored across 20 tools
Most tools have distinct purposes (e.g., create_document vs update_document, list_releases vs release_action). Slight overlap arises with document_action and mark_for_unpublish both involving unpublishing, but descriptions clarify the release-specific context.
The majority follow a verb_noun pattern (create_document, list_releases, query_documents). Minor deviations include get_initial_context (more imperative than descriptive) and action-based names (document_action, release_action) that break the pattern.
20 tools is slightly above the typical 3-15 range but still reasonable for a full-featured CMS server. Each tool covers a distinct operation, and no obvious bloat is present.
Core document and release lifecycles are covered (create, query, update, delete, schedule, publish). A notable gap is the absence of a direct get_document by ID tool, though query_documents can substitute with GROQ. Auxiliary features like semantic search and schema retrieval add value.