/deploy-schema
Deploy Sanity schema to the Content Lake with verification.
$ npx -y skills add sanity-io/agent-toolkit --agent claude-codeShips with sanity. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/deploy-schema
Context preview
What this command does when you run it.
Deploy Sanity schema to the Content Lake with verification.
Command definition
deploy-schema.mdname: deploy-schema
description: Deploy Sanity schema to the Content Lake with verification.
Deploy Sanity Schema
I'll help you deploy your schema to the Sanity Content Lake.
Why Deploy Schema?
Schema deployment is **required** for:
- ⚠️ **MCP Server content operations** (`create_documents`, `patch_documents`) to use the latest schema
- Embedded Studios
- Scheduled Publishing
- Cloud Functions with schema validation
Deployment Command
npx sanity schemas deploy
What I'll Do
1. **Pre-Deploy Check**
- Verify schema syntax (run typegen)
- Check for breaking changes
- Warn about removed fields with data
2. **Deploy**
- Run `npx sanity schemas deploy`
- Confirm success
3. **Post-Deploy Verification**
- Use MCP `get_schema` to verify deployment
- Confirm new types/fields are available
When to Deploy
| Scenario | Deploy? | |----------|---------| | Added new document type | ✅ Yes | | Added/modified fields | ✅ Yes | | Changed validation rules | ✅ Yes | | Using MCP content tools after schema changes | ✅ Yes | | Local dev only (no MCP) | Optional |
Important Notes
- **Schema deployment is fast** (~2 seconds)
- **Does NOT deploy the Studio app** (use `npx sanity deploy` for that)
- **Always deploy before MCP content operations** after schema changes
Usage
> "Deploy my schema" > "Check if my schema is deployed" > "Why can't MCP see my new field?"
Read more
name: deploy-schema description: Deploy Sanity schema to the Content Lake with verification.
Deploy Sanity Schema
I'll help you deploy your schema to the Sanity Content Lake.
Why Deploy Schema?
Schema deployment is **required** for:
- ⚠️ **MCP Server content operations** (`create_documents`, `patch_documents`) to use the latest schema
- Embedded Studios
- Scheduled Publishing
- Cloud Functions with schema validation
Deployment Command
npx sanity schemas deploy
What I'll Do
1. **Pre-Deploy Check**
- Verify schema syntax (run typegen)
- Check for breaking changes
- Warn about removed fields with data
2. **Deploy**
- Run `npx sanity schemas deploy`
- Confirm success
3. **Post-Deploy Verification**
- Use MCP `get_schema` to verify deployment
- Confirm new types/fields are available
When to Deploy
| Scenario | Deploy? | |----------|---------| | Added new document type | ✅ Yes | | Added/modified fields | ✅ Yes | | Changed validation rules | ✅ Yes | | Using MCP content tools after schema changes | ✅ Yes | | Local dev only (no MCP) | Optional |
Important Notes
- **Schema deployment is fast** (~2 seconds)
- **Does NOT deploy the Studio app** (use `npx sanity deploy` for that)
- **Always deploy before MCP content operations** after schema changes
Usage
> "Deploy my schema" > "Check if my schema is deployed" > "Why can't MCP see my new field?"
Collection of resources to help AI agents build better with Sanity.
Repo: sanity-io/agent-toolkit