A
licenseA
qualityC
maintenanceA self-hosted MCP server offering provider-independent AI routing, deterministic verification, and cryptographically signed, tamper-evident audit trails for every response.
8
973 npm
2
MIT
Sanity MCP Server
Related Servers
Alternatives to Sanity MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.MIT
- AlicenseBqualityBmaintenanceOpen-source MCP server that turns any CMS backend into an AI-agent-ready content management system. It provides tools for content CRUD, idea management, and publication tracking, with safety features requiring human approval for publishing.52MIT
Contentrain MCPofficial
AlicenseAqualityAmaintenanceLocal-first MCP server for AI content governance. 13 tools for model/content management, validation, normalization, and i18n across any framework.224MIT- AlicenseNot gradedqualityCmaintenanceMCP server for uploading local images to Sanity CMS. Enables AI assistants to upload files from your filesystem directly into Sanity as image assets.32 npm1MIT
- AlicenseNot gradedqualityAmaintenanceA self-hosted MCP server that provides Claude with a git-versioned document vault, featuring dataset-based access control with keys, OAuth authentication via GitHub, and automatic commits on every write.MIT
TDQS
A3.7/5.0
Scored across 18 tools
Disambiguation5/5
Every tool has a clearly distinct purpose: create, update, patch, delete, publish, unpublish, query, search, list, get, diff, history, references, etc. No two tools overlap in functionality.
Naming Consistency5/5
All tools follow a consistent 'sanity_verb_noun' pattern using snake_case, e.g., sanity_create, sanity_publish, sanity_list_documents. No mixed conventions.
Tool Count4/5
18 tools is slightly above the ideal 3-15 range, but the scope of a CMS (CRUD, publishing, search, history, diffs) justifies the count. Still reasonable.
Completeness5/5
The toolset covers the full document lifecycle: CRUD, patch, publish/unpublish, query, search, history, diffs, references, bulk operations, and type introspection. No obvious gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues