A few months ago, we gave agents a way to check your content system before they wrote a word. Today, agents can write from the system, and also refine the system itself — edit, update, delete, and improve the system as you work.

A quick recap

Back in March, we introduced Ditto's MCP — a way to connect your Ditto content system directly to Claude Code, Cursor, or any MCP-compatible agentic environment. It was a genuinely useful first step: an agent working in your codebase could generate copy using your approved terminology and voice, apply your style guide rules automatically, surface existing strings to reuse instead of writing new ones, and flag anything that didn't align before it shipped.

Why we're expanding these capabilities now

Product teams have been moving closer to the code for a while now — designers building in the product, PMs iterating in real interfaces, engineers shipping in an afternoon what used to take a sprint.

The original version of Ditto MCP was built for an agent to consult your system: check a rule, search for a string, draft copy with context it could reference. It wasn't built for an agent to build inside that system — make changes to the actual copy and context within the system itself. But you need to be able to use and work within your content system wherever you happen to be working in that moment.

The expanded Ditto MCP allows teams to stay in their workflow, referencing their Ditto system to generate better copy and refining the system itself based on decisions they’re making in the moment.

What this means for product teams who have a Ditto content system

Here's what's actually true now: agents aren't limited to referencing your Ditto style guides and library components. Agents can create and edit the real content — text items, library components, variants — directly in your workspace.

Your Ditto workspace stays up to date with changes as they happen, with a running activity log tracking any changes or edits (by human or agent). One integrated, traceable content system working alongside you, continuously improving as you use it.

What you can do now

In practice: an agent connected to Ditto MCP can now act inside your workspace, not just consult it.

• Create and edit projects, text items, library components, variants, and folders.
• Run reviews and iterate on copy, alongside your style guide rules.
• Bulk update text item metadata, or assign work to another teammate.
• Search across everything — by text value, dev ID, status, or any other property.
• And so, so much more.

That's a lot to take in as a list, so we wrote the full one — with walkthroughs and examples for each capability — in a companion post: Everything you can do with the Ditto MCP.

How to get started

If you're already using Ditto MCP, there's nothing to reinstall — the same connection you set up in March just does more as of today. Full setup details, specific to your use case and tool stack, can be found in our developer documentation.

Want to see the full range of what's possible, live? Book time with our team and we'll walk you through it.