Your design system,in every agent you use

One URL connects Supernova to Claude, Cursor, and any MCP client. Your agent reads your design system, and writes back to it.

Clients

Your whole stack, connected.

One MCP server reaches Claude, Cursor, Copilot, Codex, ChatGPT, Gemini, Figma, and the prototyping tools beside them. If it speaks MCP, it can read the system and write back.

Read and write

Read your design system. Write to it.

An MCP server is how an agent reaches a tool it does not live inside. Nothing to install — Supernova’s skills ship with the server.

Read

Ask what the system says

Tokens, components, assets, and documentation as structured data, not a page to interpret.

Write

Change it from where you work

Create pages, edit tokens, restructure components, publish. Most design system MCPs stop at read.

Use cases

A glimpse of what your team can do with Supernova MCP

Get set up

Import your design system from Figma

Paste a link. The agent creates the connection and runs the import.
Get set up

Build your documentation structure from what you already have

Components and tokens become a page structure, instead of an empty site.
Audit what you have

Audit your design system

Inconsistent, undocumented, deprecated, or drifting — across the whole system.
Audit what you have

Find every gap in your documentation

What each component page is missing, listed in one pass.
Audit what you have

Match your code to your tokens

Every hardcoded value from the repo, matched to a token.
Maintain at scale

Clean up your documentation in one prompt

Remove every mention of a term without opening a page.
Maintain at scale

Change a block property everywhere it appears

One property, on three pages or thirty.
Maintain at scale

Standardise ten component pages to one structure

Align the form pages to the structure of the Input page.
Create and reuse

Build the checkbox page the way you built the button page

Reuse a structure you already trust.
Build with your design system

Give your prototyping agent real components

Tokens, components, and docs as structured data, not a page to interpret.
Who it’s for

One MCP Server. Serves your whole team

01

Design system teams

Standardise documentation that grew on its own, run bulk edits, audit on demand, and import from Figma into a structure built from your components and tokens.

02

Engineers

Query tokens, components, and documentation from the IDE, in the same session as the code. Run a parity audit against the repository.

03

Designers

Ask what the design system says without leaving your tooling. After a Figma change, have the agent update the documentation that is now out of date.

04

Product managers

Ask what already exists before scoping work that rebuilds it. Check what a component supports, and what shipped since you last looked.

FAQ

Questions & answers

Give your agents a system worth following

See how Supernova documents, syncs, and serves your system in one place.