How to Use Claude AI to Manage Your Sanity CMS

If you have been building with Next.js and Sanity for a while, you know the drill. You write your schema, set up your Studio, and then spend more time than you would like clicking through the Sanity Studio UI just to create a document, update a field, or check what content exists. It works fine, but it is not exactly fast.

A few days ago I came across something that actually changed how I interact with my Sanity projects. Claude now has a native Sanity connector through MCP (Model Context Protocol), which means you can manage your Sanity content directly through a conversation with Claude. No Studio, no GROQ queries you have to remember from scratch, no context switching.

In this post I am going to walk you through exactly how to set it up and what you can actually do with it.

Setting Up Claude MCP with Sanity

There are two ways to set this up depending on how you use Claude.

Option 1: Claude Web, Desktop, or Mobile

This is the simplest route if you use Claude through the browser or the desktop app.

1. Open Claude and go to Customize in the top right
2. Click on Connectors
3. Search for Sanity
4. Click Connect and follow the authorization flow
5. Select the Sanity project you want to work with

That is it. Once connected, Claude has access to your selected Sanity project and you can start working with it right away.

Option 2: Claude Code

If you prefer working in the terminal or are already using Claude Code in your development workflow, run this command inside your project:

npx sanity@latest mcp configure

This will walk you through connecting your Sanity project to Claude Code. It sets everything up in your local config so Claude Code knows which project to talk to.

What You Can Actually Do

Once the connector is set up, here is where it gets interesting. You are not limited to basic content creation. Here are the kinds of things you can do just by typing a message to Claude.

Create Content

Create a new blog post titled "Building a Blog with Next.js 15 and Sanity"
with a short excerpt and set the status to draft

Claude knows your schema. It will create the document with the right fields, in the right format, ready to publish from Studio or through your API.

Query Your Dataset

Show me all blog posts published in March 2025

How many products do I have in my catalogue right now?

Instead of writing GROQ queries from memory, you just ask. Claude handles the query and returns the results.

Edit Existing Documents

Find the homepage document and update the hero heading to
"Build faster with structured content"

Claude finds the document, makes the edit, and confirms what changed. No hunting through Studio.

Inspect Your Schema

What does my current blog post schema look like?

This is genuinely useful when you are jumping back into a project you have not touched in a while. Instead of digging through your schema files, Claude gives you a clean summary of the fields and types.

Schema Design and Migrations

The connector also ships with guided prompts for more complex workflows like designing a new schema or running a migration. These are not just suggestions. Claude can help you think through the structure and then help you implement it.

I want to add a related posts field to my blog post schema.
It should reference other blog post documents. Help me set that up.

A Real Example from My Workflow

I manage a project that has a blog, a product catalogue, and a team page all running through Sanity. Before this, switching between content types meant navigating Studio, finding the right document type, filling in fields, and publishing.

Now I just open Claude and type what I need. Last week I had to create eight blog post drafts with titles, excerpts, and author references. Before MCP I would have done that one by one in Studio. With Claude I described what I needed and it created all of them in one go, correctly structured and ready to review.

It is not about replacing Studio entirely. Studio is still great for reviewing content, working with Portable Text, and making visual edits. But for bulk operations, queries, and repetitive tasks, talking to Claude is significantly faster.

Tips for Getting the Most Out of It

Be specific about field names when you know them. If your blog post schema has a field called publishedAt and you mention it by name, Claude will map it correctly without guessing.

Use it for GROQ help. Even if you are not doing everything through Claude, you can ask it to write GROQ queries for you and then use those queries in your Next.js app. It knows your schema so the queries will actually work.

Combine it with Claude Code. If you are building a new Sanity project and also writing your Next.js frontend, having Claude connected to Sanity while also helping you write code is a solid setup. You can ask Claude to create test content in Sanity and generate the corresponding Next.js components in the same conversation.

Start with read-only tasks first. Before you start editing and creating, spend a few minutes just asking Claude to describe your schema and show you some existing documents. This helps you get a feel for how it interprets your content model before you start making changes.

Final Thoughts

I have been using Sanity with Next.js for a while now and the content management side of things has always been the less exciting part. The schema design is fun, the frontend work is fun, but the actual day-to-day content operations are a lot of manual work.

Having Claude connected to Sanity through MCP makes that part of the job noticeably easier. It is not magic, it still needs clear instructions and it works best when you know your own content model, but for a developer who is already comfortable with Sanity and wants a faster way to interact with it, this setup is genuinely worth adding to your workflow.

Give it a try and see how it fits into the way you work. If you have questions or run into anything while setting it up, drop a comment below.