Consumer MCP gives AI tools read access to a context — so they can read and search your design system data and knowledge. It also allows users to submit feedback via MCP.
Who is it for
Consumer MCP is for people who should use the design system, not maintain it in Supernova.
- Viewers — this is the only MCP connection they can make. During sign-in they only see contexts.
- Engineers, designers and anyone else from your organisation working from a scoped set of tokens, docs, skills, and files.
Share a context only with the team it is for. If engineering and marketing have separate contexts, each team should connect to its own.
How to connect
You need a Supernova account. Add Supernova as a custom MCP server, then pick a context when you sign in.
https://mcp.supernova.io/mcp
- Open Settings / Customize
- Navigate to MCPs
- Select New MCP Server
- Paste:
{
"mcpServers": {
"supernova": {
"url": "https://mcp.supernova.io/mcp"
}
}
}
Sign in to Supernova when prompted, and pick a context.
Claude Code
Add the server with the Claude Code CLI:
claude mcp add --transport http supernova https://mcp.supernova.io/mcp
On first use, Claude Code opens a browser window so you can sign in. Pick a context. After authenticating, Claude Code reuses the session for later calls.
Claude for Desktop / Claude.ai
- Navigate to Settings / Customize / Connectors
- Click on Add → Add custom connector
- Integration name: Supernova
- Integration URL: https://mcp.supernova.io/mcp
- Sign in to Supernova when prompted, and pick a context
- Use shortcut CTRL/CMD + SHIFT + P and select MCP: Add Server
- Select HTTP (HTTP or Server-Sent Events)
- Enter https://mcp.supernova.io/mcp
- Name it Supernova and start the server
- Sign in to Supernova when prompted, and pick a context
codex mcp add supernova --url 'https://mcp.supernova.io/mcp'
Sign in to Supernova when prompted, and pick a context
- To add custom connector, you need to enable Developer mode first
- Go to Settings / Security and login / Developer mode
- Go to Plugins, and click on + in top right corner
- Integration name: Supernova
- Integration URL: https://mcp.supernova.io/mcp
- Sign in to Supernova when prompted, and pick a context
To lock the connection to one context, copy a context-dedicated URL from the context’s Distribution → MCP card:
https://mcp.supernova.io/mcp/c/{context-id}-{context-name}
What Consumer MCP can do
The assistant only sees what’s in the connected context. The context can include documentation, tokens, components, assets, skills and files.
When you ask for something, the assistant picks a tool from this set. You don’t need to name the tools.
Search and read documentation
The assistant can search pages, skills, and files, list pages, and read up to five pages at a time. A typical turn is search first, then read the pages that match.
Look up tokens, components, and assets
When the context includes design system data, the assistant can list and fetch tokens, token groups and themes, design system and Figma components, code components, Storybook stories, assets, and connected Figma sources.
Follow skills and files
The assistant can read workspace skills and knowledge files in the context, plus bundled MCP instruction files for this connection.
Send feedback
If feedback collection is enabled, sn_collect_agent_feedback reports a gap — a missing token, outdated page, or conflicting guidance. Feedback is tied to that context and reviewed in Supernova.
What it cannot do
A context connection cannot:
- Edit documentation, tokens, components, contexts, skills, or files
- Publish documentation or run export pipelines
- Invite teammates or change workspace settings
- See data outside the connected context
- Access Editor MCP — pick a design system when you sign in (Contributor and above) for write access
Sample prompts
|
Prompt |
What it does |
|---|---|
|
"How do I use the Button component?" |
Searches documentation and reads the matching pages. |
|
"How do we handle form validation errors? Show me the pattern and the error state tokens." |
Finds the validation pattern and the tokens used for error states. |
|
"Do we already have something like a segmented control?" |
Searches components and docs for a close match. |
|
"Summarise our design system for a new engineer joining the team." |
Reads docs, tokens, and components in the context and writes a short onboarding brief. |
|
"The Button docs still mention a size we removed — submit feedback." |
Sends feedback on the connected context. |
Available tools
The assistant only sees data in the connected context. It picks a tool from this set — you don't need to name it.
Search and documentation
|
Tool |
Description |
|---|---|
|
sn_search |
Search documentation pages, skills, and files in the context. |
|
sn_get_documentation_page_list |
List documentation pages in the context. |
|
sn_get_documentation_page_content |
Read documentation page content. |
Tokens
|
Tool |
Description |
|---|---|
|
sn_get_token_list |
List design tokens in the context. |
|
sn_get_token_group_list |
List token groups in the context. |
|
sn_get_token_detail |
Get token, including theme values. |
|
sn_get_token_theme_list |
List token themes. |
|
sn_get_token_property_list |
List token properties and options. |
|
sn_get_token_usage |
Where a token is used in code, when adoption data exists. |
Components
|
Tool |
Description |
|---|---|
|
sn_get_component_list |
List design system components in the context. |
|
sn_get_component_detail |
Get a design system component. |
|
sn_get_component_property_list |
List component properties and options. |
|
sn_get_figma_component_list |
List imported Figma components in the context. |
|
sn_get_figma_component_detail |
Get a imported Figma component. |
|
sn_get_code_component_list |
List imported code components in the context. |
|
sn_get_code_component_detail |
Get a imported code component. |
|
sn_get_storybook_story_list |
List imported Storybook stories in the context. |
|
sn_get_storybook_story_detail |
Get a imported Storybook story. |
Assets and Figma sources
|
Tool |
Description |
|---|---|
|
sn_get_asset_list |
List assets in the context. |
|
sn_get_asset_group_list |
List asset groups in the context. |
|
sn_get_asset_detail |
Get a asset. |
|
sn_get_design_source_list |
List connected Figma design sources. |
Skills, files, and contexts
|
Tool |
Description |
|---|---|
|
sn_get_knowledge_skill_list |
List skills in the context. |
|
sn_get_knowledge_skill_detail |
Read a skill's content. |
|
sn_get_knowledge_file_list |
List knowledge files in the context. |
|
sn_get_knowledge_file_detail |
Read a knowledge file. |
|
sn_get_context_list |
List contexts in the workspace. |
|
sn_list_skill_resources |
List bundled MCP instruction files for this connection. |
|
sn_read_skill_resource |
Read a bundled MCP instruction file. |
People and feedback
|
Tool |
Description |
|---|---|
|
sn_get_me |
The signed-in user for this session. |
|
sn_get_users_list |
Workspace members and roles. |
|
sn_get_team_list |
Team members, invitations, and seat limits. |
|
sn_get_feedback |
List feedback items. |
|
sn_collect_agent_feedback |
Submit feedback for this context. The only write on Consumer MCP. |