"Sanity" matching MCP servers:

Gives AI agents direct access to content projects for running GROQ queries, creating, patching, publishing, and unpublishing documents, inspecting and deploying schemas and hosted Studios, and fetching always-current agent rules. Authentication is handled through OAuth or bearer tokens, so no local files or manual token setup are needed.

Deterministic JSON validation and repair for AI agents. Validates, repairs, schema-checks, and diffs JSON so long-running agents don't corrupt their session state with malformed writes.

A self-hosted Sanity MCP server with full CRUD, atomic transactions, reference tracking, and advanced tools for content management and operations.

Enables AI agents to directly interact with Sanity CMS projects, including querying, creating, and managing documents, schemas, releases, and image generation.

An MCP server that enables Claude Desktop to interact with Sanity.io content, providing tools to create, edit, list documents and get schema templates.

Fans out queries to multiple independent free LLMs from different providers and returns their answers side by side, enabling sanity-checking of decisions or getting multiple perspectives during coding sessions.

An MCP server that lets Claude Code or any MCP client hand bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local GPU model, an OpenAI-compatible endpoint, a router, or a cheap cloud API, so those files never enter the orchestrator's context window. This cuts token spend and quota use while providing a second model to sanity-check results.

Lets an MCP client hand bounded work such as code review, boilerplate, commit messages, format conversion or embeddings to a local or cloud OpenAI-compatible LLM, so file contents never enter the orchestrating model's context and token costs drop. It also provides a second model to sanity-check code and drafts while the main assistant keeps planning and tool use.