Introducing Supernova Editor MCP

A design system team is often one or two people holding up an entire org. They get pulled into every new problem. The system itself — the docs, the names, the gaps, the drift between Figma and code — waits. It always waits.

Agents already changed the other half of the job. Point an AI tool at your design system and building gets faster. Adoption gets easier. The agent can see the tokens, the components, the rules. That was a big step. It was not the one that mattered for the people maintaining the system.

Because a system that agents can only read is still a system that humans have to keep.

An agentic design system is one that agents can act on. Query, resolve, and contribute — not just consume. Reading got us to the door. Write access is the first step through it.

That's what we shipped.

From conversation to real edits

Editor MCP gives the AI tools you already live in — Cursor, Claude, VS Code, Codex, ChatGPT — write access to Supernova. Documentation, tokens, components, files, skills, contexts, pipelines.

You don't get a suggestion to copy-paste back into the product. You have a conversation, and the edit lands in Supernova the same way it would if you'd made it yourself.

Forget the backlog of "we should document that." The agent can document it. Forget the rename that touches forty pages. The agent can sweep it. The work that used to be a quarter's worth of maintenance can start happening in the background of the tools your team already has open.

We ran this in early access before today. The part that stayed with us wasn't the speed. It was watching teams treat the design system as something an agent could keep — not just look up.

They documented every new component as it landed. They found the pages missing states and usage guidelines, drafted the gaps, and didn't panic, because page history can restore any docs change. They renamed and deprecated in one pass. They drafted documentation after a Figma import. They enforced naming. They caught Figma variants drifting from coded properties. They audited for stale pages and broken links before anyone had to go looking.

That's not a feature list. That's what a design system starts to look like when agents can write.

I see Supernova MCP as a massive time-saver after trying it in action this morning. I'm looking forward to making our design system maintenance completely agentic. Link codebases, Figma, etc. This is going to be huge!

— Felix Pfahlert, Design System Lead, EGYM Wellpass

Felix is pointing at the same horizon we are. Maintenance that runs itself. A system that stays true because agents are in it, not because two people found a free afternoon.

Fully agentic is still ahead of us: agents that operate the system with people setting the boundaries — what they may do unsupervised, what needs review, what stays a human decision. Editor MCP is the first move that makes that future possible. Without write, agents are well-informed spectators. With it, they can take care of the house.

One URL, from the tool you're already in

We wanted this to feel like nothing to install. There is one URL to connect to any design system or context:

https://mcp.supernova.io/mcp

At sign-in, pick a design system for Editor MCP, or a context for read-only access. The documentation skills are bundled into the server. Your agent already speaks Supernova.

Editor MCP is in public beta, and it's free to use. The tools don't consume Workspace credits today. That will change once it graduates from beta, and we'll give you plenty of notice before it does.

Use it while it's free. Point it at the documentation backlog you've been putting off. Run an audit. Try a bulk edit you'd never have attempted by hand. Then tell us what you find — this beta is how we learn what a fully agentic design system actually needs to be.

Reading showed agents the system. Writing lets them take care of it. That's the first step. Let's take it.

👉 Read the Editor MCP docs

👉 See the full release notes