Claude Sanity connectorWhat Claude can do in your Sanity account.
The Claude Sanity connector exposes 31 tools: 14 read, 10 write, 7 undocumented. They cover queries, schemas, datasets, publishing and projects. Below: what Claude reads, what it publishes or deletes, and where the sheet and the docs disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a content team
Sanity stores your content in structured form, defined by a schema. With the connector, you ask Claude to search, audit or publish right in the conversation, without writing the query yourself. Per Sanity, the server acts on your behalf and with your permissions, and it also offers project setup tools.
Audit content. To find content, query_documents runs the query in GROQ, Sanity's query language, and semantic_search finds texts that are close in meaning when an index exists.
Coordinate a campaign. For a release, create_version attaches each document to a release, and version_discard pulls the ones that are no longer part of it.
Publish or take down. When drafts are ready, publish_documents puts it live, unpublish_documents sends it back to draft, and discard_drafts throws away drafts without touching published pages.
What Claude doesn't do here: nothing fires on its own, and no publication goes out on a timer from Claude. Per the docs, scheduling, publishing or deleting a release happens in Sanity Studio. And seven tools on the sheet aren't described by Sanity's documentation. For automated jobs, you want an automation tool; the Integrations page covers that side, and Claude connectors gathers the rest.
The vocabulary in one minute
Five words worth knowing before you connect Sanity.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the chat right when it matters.
- MCP
- The common standard behind connectors: it's what lets an assistant like Claude hold a conversation with an outside service.
Connect Sanity to Claude in three steps
- 01
Find Sanity
In Claude's settings, open Customize, then Connectors, and spot Sanity in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in through the window the service opens itself. If the link breaks one day, hit Disconnect and connect again: that's the intended fix.
- 03
Read the authorization screen
Read the authorization screen before you approve. It belongs to the service, not to Claude, and it decides what the access covers. Per Sanity, the server then acts on your behalf through OAuth by default.
The 31 tools of the Claude Sanity connector
Sanity gives Claude 31 tools: 14 that read your account, 10 that change something in it, and 7 no official source describes.
Three groups: what Claude reads, what it changes, and what Sanity's documentation doesn't describe. Names stay as Claude shows them.
- 14 read
- 10 write
- 7 not documented
What Claude reads (14)
14 toolsFourteen tools that look at projects, schemas, datasets, documents and documentation.
get_document
Fetches a single document from its exact ID, with its full content. It's a direct lookup: the tool doesn't search, filter or query anything else.
get_project_studios
Retrieves every Studio application linked to a given Sanity project.
list_workspace_schemas groups separately.get_sanity_rules
Loads specific best-practice development rules published by Sanity, picked from the list the companion tool returns.
get_schema
Fetches a deployed schema, meaning the definition of a workspace's content types. With no name given, it picks the active schema or the default workspace.
list_datasets
Lists every dataset in your Sanity project. A dataset is a separate pool of content inside the project.
list_embeddings_indices
Lists the embeddings indexes available for a dataset. An embedding is a numeric representation of a text's meaning, used to search by meaning rather than exact words.
list_organizations
Lists every Sanity organization your account has access to. It's the level above projects.
list_projects
Lists the Sanity projects associated with your account, the usual entry point before looking at datasets or schemas.
list_sanity_rules
Lists the development best-practice rules Sanity makes available, so you know which ones to load next with the dedicated tool. Think of it as the table of contents before loading.
list_workspace_schemas
Lists every deployed schema for a project and dataset, grouped by source: server-managed, Studio-deployed or legacy. Each entry carries an ID for an exact read.
query_documents
Queries documents with GROQ, Sanity's query language, and brings back the matching documents. Only the GROQ string goes in the query, with variables passed separately as a JSON object.
read_docs
Fetches one specific article from Sanity's documentation.
search_docs runs a search across Sanity's documentation first, and this tool then reads the one you pick.search_docs
Runs a search across Sanity's documentation. It's often the step before reading one specific article. Handy for finding the right article without knowing its title, before reading it with the companion tool.
semantic_search
Runs a semantic search on an embeddings index: it finds content that's close in meaning, even without the exact word. It only works where an index exists.
list_embeddings_indices tells you first whether a dataset has an index.What Claude changes (10)
10 toolsTen tools that create, publish, unpublish, modify or delete. No source spells out their confirmation: the general rule below applies.
add_cors_origin
Approval: see the ruleAdds one or more CORS origins to a project, meaning site addresses allowed to query Sanity from the browser.
create_dataset
Approval: see the ruleCreates a new dataset with the name and access settings you specify.
create_project
Approval: see the ruleSets up a brand-new Sanity project and equips it with a dataset and API tokens. It's the starting point for a brand-new project, built from the conversation.
create_version
Approval: see the ruleCreates a version of a document for a specific release, separate from the draft and the published document. Versions serve scheduled releases.
deploy_schema
Approval: see the ruleDeploys schema types straight to Sanity's cloud. The content structure shifts for everyone.
discard_drafts
Approval: see the ruleDeletes one or more drafts while leaving already-published documents intact. The live versions don't move.
publish_documents
Approval: see the rulePublishes one or more drafts, from the documents' exact IDs. The content goes live.
unpublish_documents
Approval: see the ruleUnpublishes one or more published documents, which go back to being drafts.
update_dataset
Approval: see the ruleModifies a dataset's name or access control settings. Those settings decide who can read it.
version_discard
Approval: see the ruleRemoves one or more document versions from a release. The documents themselves aren't targeted, only their version planned for that release.
Undocumented (7)
7 toolsThe sheet publishes these seven names, which Sanity's documentation doesn't describe. We won't guess what they do from a name.
create_documents_from_json
This name appears on the directory sheet, and no official source describes it: Sanity's documentation says nothing about it. Its name alone doesn't say what it does.
create_documents_from_markdown
A name published by the directory and missing from Sanity's documentation. No other public source explains it.
migration_guide
The directory lists this name with no description, and Sanity's page about its server doesn't mention it.
patch_document_from_json
No official sentence describes this tool: it shows up on the sheet, not in the publisher's documentation. No public page picks it up either.
patch_document_from_markdown
Present in the directory's list, this name has no description from Sanity or from Anthropic. The docs list other tools instead.
version_replace_document
Neither the sheet nor Sanity's documentation describes this name; only its label is published. No public page fills that gap.
version_unpublish_document
This name has no official description: the sheet lists it, and Sanity's page about its server doesn't cover it. Its label is all there is.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the chat, right when it matters.
No source says whether Claude asks before publishing, unpublishing or deploying a schema: that default rule covers all ten write tools. On a Team or Enterprise workspace, owners decide whether a member can let certain actions through without being asked again, and they can shut off a connector's writes for the whole organization. On the Sanity side, the server acts with your role and your permissions.
Which plans include it
Out of 819 sheets in the official directory, none shows availability by plan. Connector by connector, the answer isn't published anywhere: it's a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, the Sanity sheet in the official directory is where to look.
Where Sanity stops inside Claude
A connector isn't an automation. Claude calls these tools while it answers you: nothing goes out when a draft is ready or a date arrives.
Only the publisher documents this connector, on the page of its docs devoted to the server: neither Claude's help center nor Anthropic's developer docs mention it at all. Everything on this page comes from that page and the directory sheet. And the directory sheet and Sanity's docs don't list the same tools, as the comparison below lays out. The partner badge isn't a security audit, and Anthropic doesn't guarantee a publisher's tools behave as described.
Which tools does the Sanity connector actually expose?
- Claude directory sheet ↗October 202631 tools, seven of which Sanity's documentation doesn't mention, such as the ones whose names mention JSON or Markdown.
- Sanity's documentation for its MCP server ↗September 2026A list that doesn't match the sheet's, with other document creation and editing tools, plus a note that available tools may vary as the server gets updated.
What this page followsNeither side is stale: the two lists simply don't match. This page follows the directory sheet and leaves the seven tools the docs don't describe as undocumented; what your account actually sees shows up in the connector sheet once connected.
Need help connecting Sanity to Claude?
A person reads every message.