Sanity MCP connector
The Sanity connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent query, create, patch and publish Sanity documents, upload assets and deploy schemas, with each person signed in as themselves and every change recorded in an audit log.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which Sanity documents are still in draft this week?
Working in Sanity with Elaichi
-
Get schema
-
List workspace schemas
-
Query documents
How to connect Sanity to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Sanity MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Sanity MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Sanity MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Sanity MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Sanity MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Sanity to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Sanity through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Sanity is logged.
-
Content
Catch a draft up after an edit meeting
Ask for the documents still in draft, patch the fields that changed in the meeting, and publish the ones that are ready in a single pass.
-
Marketing
Stand up a campaign page from a brief
Create the landing page documents from a campaign brief, pull the hero images in from URLs, and keep them unpublished until launch day.
-
Engineering
Review and deploy a schema change
List the workspace schemas, compare a proposed change against what is live, and deploy the schema and the studio once it is approved.
-
Design
Get images into the media library fast
Upload a batch of assets from a shared folder or URL, check that each upload finished, and transform or generate variants for the pages that need them.
-
Product
Publish release notes on release day
Draft the release notes document from the ticket summary, create a version for review, and publish it the moment the build ships.
-
Localization
Find what still needs a translation
Query the documents published in one language that have no matching version in another, then create the translated drafts for the team to review.
Try asking
- “Which Sanity documents are still in draft this week?”
- “Publish the spring campaign landing page documents.”
- “Upload the new hero images from these URLs to the media library.”
What connecting Sanity gets you
6 screens from Elaichi, each doing one job for your Sanity account.
Ask Elaichi to work across your apps.
Which Sanity documents are still in draft this week?
Publish the spring campaign landing page documents.
Upload the new hero images from these URLs to the media library.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your Sanity documents in plain language.
Find drafts, check published pages and confirm upload status from live Sanity records.
Copy the endpoint
AI apps
One endpoint brings Sanity to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
53 Sanity tools, ready without writing code.
Documents, assets, schemas and studio deploys, covered the moment Sanity is connected.
Toolboxes
Every team gets its own Sanity toolbox.
Editors publish documents, engineers deploy schemas, each from a toolbox scoped to them.
Shared connections
Teammates work in Sanity without seeing a credential.
One person connects Sanity, shares it with teams, and nobody else handles a token.
Audit log
Every Sanity change is logged with a name.
See who published, patched or unpublished which document, and exactly when it happened.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Sanity digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch documents
Sanity
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Sanity
Queued
Workflows
Scheduled runs turn Sanity drafts into reviewed digests.
New documents are fetched, grouped, drafted into a digest, approved, then posted back to Sanity.
Sanity health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Assets
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By team
Share of activity
Editorial 34%
Marketing 27%
Engineering 21%
Design 18%
Collections and dashboards
Sanity content health, computed without asking a model.
Documents created over 14 days, upload counts and team breakdowns, refreshed on a schedule.
Why connect Sanity's MCP server through Elaichi
Sanity builds and runs this MCP server. Elaichi sits in front of it, so Sanity's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Sanity's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Sanity's tools at the same Elaichi address as every other connected app. Nobody adds Sanity's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Sanity sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Sanity's server. By default, a tool Sanity does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Sanity
Sanity builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Sanity team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Sanity
All three can connect Sanity to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Sanity tools | Allow or restrict single Sanity tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Sanity call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Sanity tools for your AI agents
53 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sanity, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Sanity builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Sanity to Claude?
Connect Sanity in Elaichi first, which sends you to Sanity's own sign-in over OAuth; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Once Claude signs in to Elaichi, your Sanity documents, assets and schemas are available in the conversation.
Does Sanity work with ChatGPT and Cursor as well as Claude?
Yes. Sanity is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, Microsoft Copilot or any other MCP client. The Elaichi Agent uses that same Sanity connection too, so there is nothing to set up a second time.
What can an AI agent actually do with my Sanity content?
It can query and read Sanity documents, create new ones, patch fields, publish or unpublish, discard drafts and create versions. It can upload images and files into the media library from a URL or a file, check whether an upload finished, and generate or transform images. On the engineering side it can read, list and deploy schemas and deploy the studio. Short, concrete asks such as 'publish the pricing page draft' work better than long paragraphs.
Does connecting Sanity give the AI everything in my project?
No. Every call into Sanity runs as the person who signed in, so the AI only sees the projects, datasets and documents that person can already reach in Sanity. Elaichi can narrow that further with roles and restrictions, and it never widens what Sanity itself allows.
Can I stop an agent from deleting or changing things in Sanity?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and querying Sanity documents while restricting publish, unpublish, patch or discard. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Sanity connection when someone leaves?
Offboarding that person in Elaichi ends their access to Sanity through every client at once. A Sanity connection shared with the team keeps working for everyone else. If you want the connector gone entirely, disconnecting Sanity once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.
Does the Sanity MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Sanity is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Sanity?
Yes. Both let Claude, ChatGPT or Cursor use Sanity. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Sanity call.
How is Elaichi different from Composio for Sanity?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Sanity: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Sanity in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot