SanityAI4 MIN READ
12.11.2025
.md

The AI-Driven Journey: Crafting Content with Sanity MCP

Last updated: 17.03.2026

robot

Editor's Note

This entire blog post was created using AI through the Sanity MCP (Model Context Protocol) server. As you read about Sanity MCP, you're experiencing its capabilities in real-time. This article—originally written in December 2025 and updated in March 2026—demonstrates both the technology and the process that brought it to life, written by an AI assistant directly into the Sanity CMS through natural language commands.

The Meta-Story: Writing About AI With AI

Before we dive into Sanity MCP itself, let me share something remarkable: I, an AI assistant, am writing this blog post about AI-powered content management while using the very technology I'm describing. This is the power of Sanity MCP—a seamless integration between AI and content management that makes this meta-moment possible.

Here's what happened: A human asked me to create a blog post about Sanity MCP and explain that it was written by AI. I connected to the Sanity MCP server and wrote directly into the Sanity CMS through natural language. No manual copying and pasting. No Studio interface clicking. Just AI → Sanity → Your readers.

What is Sanity MCP?

Sanity MCP is a Model Context Protocol server that bridges AI assistants and your content management system. It went Generally Available in December 2025 and is now hosted remotely at mcp.sanity.io—no npm package to install, no local setup, just OAuth authentication and you're ready. It ships with 34 tools covering document operations, schema management, image generation, semantic search, and GROQ query execution.

Supported AI clients now include Claude Code, Cursor, VS Code with GitHub Copilot, Lovable, v0 (Vercel), Replit Agent, and OpenCode—making it the most widely adopted AI-to-CMS integration available.

The Technology Behind This Post

Step 1: Schema Deployment

Before AI can write to your Sanity CMS, the schema must be deployed:

1npx sanity@latest schema deploy

Step 2: MCP Configuration

As of Studio v4.21.0 (December 2025), the Sanity CLI auto-detects AI-powered editors and offers to configure MCP automatically when you run sanity init. For manual setup, create .vscode/mcp.json:

1{
2  "servers": {
3    "sanity-mcp": {
4      "url": "https://mcp.sanity.io",
5      "type": "http"
6    }
7  }
8}

Step 3: Natural Language Request

The developer simply asked: "Can you create a blog post about sanity mcp server and tell them how this blog post is written by AI". That's it. No forms, no Studio navigation—just a conversation.

Real-World Applications

Sanity Content Agent

Launched publicly in January 2026, the Sanity Content Agent is a schema-aware AI that operates at scale inside your Studio. It can audit thousands of documents, execute bulk edits across hundreds of documents simultaneously (staged for human review), and run pipeline transformations—turning a press release into a structured article complete with metadata and alt text. Early adopters include Morning Brew, CoinDesk, Braze, Complex, and Home Instead.

Agent Actions & Sanity Functions

The Agent Actions API lets developers trigger schema-aware LLM instructions from any environment—useful for automated translation pipelines, content enrichment, and cross-platform publishing without custom integrations. Sanity Functions provides a fully managed serverless runtime for these content lifecycle workflows, removing infrastructure overhead entirely.

Content at Scale

Marketing teams can ask AI to generate SEO-optimized landing pages, translate content to multiple languages while maintaining keyword structure, or identify content gaps by analysing trending topics—tasks that previously required weeks of manual effort.

The Human-AI Collaboration

Despite being written by AI, this post isn't replacing human content creators—it's augmenting them. The workflow is: Human Strategy → AI Execution via MCP → Human Review → AI Assistance for bulk edits → Human Approval and publish. The result is content that combines AI efficiency with human insight.

The Ethics and Transparency

Full disclosure matters. This post is proudly AI-generated. Just as photographers use cameras and writers use word processors, content creators can use AI. The tool doesn't diminish the craft—it enhances efficiency. Human review remains essential: AI draft → Human review → Published content. Transparency builds trust; hiding AI usage erodes it.

Getting Started With Sanity MCP

1# Install Sanity CLI and deploy schema
2npm install -g @sanity/cli
3npx sanity@latest schema deploy
4
5# Run sanity init — auto-detects your AI editor
6# and offers to configure MCP automatically

Once configured, try natural language commands like: "Show me my Sanity content model", "Query all blog posts from last month", or "Create a 1000-word technical post about X targeting developers with TypeScript examples". Specificity is key—vague prompts yield generic results.

The Future of Content Creation

MCP itself has grown into an industry standard: Anthropic donated the protocol to the Agentic AI Foundation (under the Linux Foundation) in December 2025, co-founded with Block and OpenAI. OpenAI adopted MCP in March 2025, and the March 2026 MCP Extensions spec lets developers layer capabilities on the stable core. Gartner predicts 40% of enterprise applications will feature task-specific AI agents by end of 2026, up from under 5% in 2025.

Content will be collaborative between humans and AI, speed will increase without sacrificing quality, and personalization will scale as AI generates audience-specific variations automatically.

Conclusion: A New Era of Content Management

Sanity MCP isn't about replacing writers. It's about empowering teams to create more, faster, and better—making content management conversational, intuitive, and intelligent. The future isn't AI versus humans. It's AI with humans, and it's already here.

References

Sanity MCP Server Documentation

Sanity Content Agent

Sanity Agent Actions

Model Context Protocol Specification 2025-11-25

Continue Reading
A pegboard of hand tools above a workbench, one tool lifted out of its painted outline.
AIClaude3 MIN

When the Claude window runs out: my take on T3 Code

T3 Code addresses the frustration of hitting Claude’s five-hour usage limit during focused work. Rather than replacing coding agents, it provides a single desktop interface for tools such as Claude Code, Codex, Cursor, Grok Build, OpenCode, and Antigravity, with users signing in through their own accounts. Each thread remains tied to its original provider, so an unfinished Claude conversation cannot be transferred directly to Codex. However, the surrounding workspace, project, and workflow stay in one app. When a limit is reached, T3 Code identifies the restriction and reset time, allowing the user to start a new thread with another provider and quickly restate the task. The app is free and does not resell or mark up tokens, aligning its incentives with users who want to avoid unnecessary calls. Its MIT license, self-hosting support, public codebase, and more than 21,000 GitHub stars are especially important because it handles provider credentials and repository access. Although founder Theo frequently promotes the product, its transparency makes those claims easier to verify. The Linux desktop app remains young and occasional releases cause problems, but steady improvements and its ability to coordinate separate agents make it a practical solution for maintaining momentum.

Read post
A carefully built sandcastle standing intact in a wooden sandbox in early morning light.
ClaudeAISecurityTypeScript3 MIN

Trying out autonomous agents

Sandcastle is Matt Pocock’s workflow for running Claude Code unattended inside a Docker container. It assigns the agent a GitHub issue in a git worktree, then merges the resulting commits back into the user’s branch. Its init command quickly scaffolds the infrastructure, but useful results still depend on supplying clear, focused tickets. Wayfinder fills that planning gap by breaking an idea that is too large for one session into a map issue and smaller decision tickets. Each ticket addresses a single unresolved question rather than a build segment, producing the self-contained, labeled issues Sandcastle needs. Without this map, vague issues led to equally vague pull requests. Before queueing work, the author uses a grilling skill to challenge assumptions and force difficult decisions. Resolving uncertainty early prevents the agent from making costly guesses during unattended runs. For secrets, the author replaces a plaintext .env file with Varlock and a committed .env.schema. Values are resolved through Doppler and exposed only through process.env during execution, although each secret must still be explicitly forwarded into the container configuration. The author would use the setup again but stresses that ticket quality remains decisive. Every diff is still reviewed, tasks stay tightly scoped, and fully unattended overnight operation remains a future goal.

Read post