UI Design MCP Server
Prism is a stdio MCP server that lets an agent generate design tokens and build, animate, review, and export stateful multi-page UI designs — though the shipped schema exposes only 28 tools, not the 42 the README advertises.
Generate design tokens/assets (stateless, read-only, markdown or JSON): color palettes (monochromatic, analogous, complementary, split_complementary, triadic, tetradic), font pairings, modular type scales, spacing scales (linear/geometric/fibonacci), shadow systems, border-radius scales, CSS gradients, responsive breakpoints, complete token sets, and WCAG 2.1 contrast checks.
Build a design in session state:
design_init(style preset + optional base color, clears prior state), then add/update/remove/reorder components and set individual tokens.Component types (27 in schema): hero, navbar, card, card_grid, button, form, text_section, image, cta, footer, stats, timeline, pricing, testimonial, faq, feature_list, banner, tabs, accordion, carousel, modal, sidebar, breadcrumb, pagination, progress, badge, avatar — with variants (e.g. hero centered/split/fullbleed, card_grid 2col/3col/4col).
Add motion:
design_set_animationfor entry animations (fadeUp, scaleIn, slideRight, spring, …), hover effects (scaleUp, lift, glow), duration, delay, and easing curve.Apply templates: ecommerce_home, saas_landing, blog_post, portfolio, dashboard.
Work multi-page: add, switch, and remove pages.
Inspect and correct:
design_get_state,design_get_conflicts, plusdesign_undo/design_redo.Switch light/dark theme via
design_set_theme.Export code: html, react, vue, or figma_tokens.
Poll for dashboard prompts sent by a browser client via
design_check_prompts.Schema vs README drift: the schema omits the README's claimed persistence, accessibility/improvement audits, preview rendering and sync, DTCG/token import-export, HTML/webpage import, semantic styling, capabilities manifest, 4 resources, 3 prompts, and extra export formats (Svelte, Flutter, SwiftUI, presentation, CSS); conversely
design_set_animationanddesign_check_promptsappear in the schema but not the README.
Generates responsive breakpoint systems that align with Bootstrap's breakpoint conventions, for use in Bootstrap-based projects.
Provides curated font pairings and typography scales with direct links to Google Fonts, enabling the use of web fonts in design projects.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@UI Design MCP Server Generate a complementary color palette for #3B82F6"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Prism
中文文档:README.zh-CN.md
An MCP server for design work. Give an AI agent the ability to generate design tokens, assemble a page from 38 component types, review it for accessibility and design quality, and export it as code or tokens.
42 tools, 4 resources, 3 prompts over stdio
38 component types with validated Zod prop schemas
Export to HTML, React, Vue, React-TS, Svelte, CSS, presentation, Flutter, SwiftUI
Tokens in DTCG, CSS custom properties, Style Dictionary, Figma Tokens, Tailwind v4
@theme, DESIGN.mdSessions are stateful and persisted: save/load a project as
.prism.jsonLive preview: one stable artifact any viewer can follow (
design_preview_sync), plus a self-contained DeepSeek Harness plugin (dsh-plugin-prism-design) whose panel opens from the sidebar rail or the right SidebarNo dashboard, no HTTP server, no external APIs. Exported pages are self-contained (pure CSS animation, no CDN runtime)
Quick start
npm install
npm run build
npm start # speak MCP over stdioWire it into an MCP client
{
"mcpServers": {
"prism": {
"command": "node",
"args": ["/absolute/path/to/prism/dist/index.js"]
}
}
}Any MCP-capable client works (Claude Desktop, Cursor, Claude Code, or your own). Once connected, ask the agent for something like:
Build a landing page for a coffee roastery, warm and editorial. Then audit it for accessibility and export the React version.
The agent will call design_init → design_add_component → design_audit_accessibility
→ design_export and can inspect its own work through design_get_state.
Verify the server
npm run smoke # spawns dist/index.js, handshakes, lists tools/resources/promptsRelated MCP server: design-architect-mcp
Tools
Call design_list_capabilities for the machine-readable manifest. It lists
exactly the registered tools — this is enforced by tests/tools.test.ts,
so the manifest cannot drift from the registry.
Generation — stateless token and asset generators (10)
Tool | What it does |
| Harmonious palettes from a base colour (6 harmony schemes) |
| Curated font pairings with Google Fonts links |
| Modular type scales (golden ratio, perfect fourth, …) |
| Spacing systems (linear, geometric, fibonacci) |
| Elevation shadow sets (subtle, medium, sharp) |
| Radius scales (sharp, subtle, rounded, pill) |
| WCAG 2.1 contrast ratios with AA/AAA grading |
| CSS gradients with harmonious stops |
| Responsive breakpoint systems (Tailwind, Bootstrap, Material) |
| A complete token system in one call |
Session — build a design in the server's state (18 + 3 persistence)
Tool | What it does |
| Start a session (neutral default tokens + optional base colour) |
| Add a component by type, with validated props |
| Update props, layout, visibility, lock |
| Rename a layer |
| Remove a component |
| Reorder siblings |
| Align/distribute (single undo step) |
| Stacking: front/back/forward/backward |
| Set one token |
| Light/dark |
| One of 5 page templates |
| Multi-page sessions |
| Read the whole session (tokens, pages, components, activity) |
| Token contrast conflicts |
| History (50 snapshots) |
| Persist and restore a session as |
Review, delivery and meta (11)
Tool | What it does |
| WCAG-oriented audit with a 0–100 score |
| Heuristic review: structure, density, motion, a11y, tokens |
| Standalone HTML preview (PNG when Playwright is installed) |
| Write the live-preview file so a watching viewer shows the latest design |
| html / react / vue / react-ts / svelte / css / presentation / flutter / swiftui |
| DTCG / CSS / Style Dictionary / Figma Tokens / DESIGN.md / Tailwind v4 |
| Import DTCG tokens (replace / merge-overwrite / merge-keep) |
| Import a URL or pasted HTML as components |
| Import tokens from a Google DESIGN.md document |
| Map adjectives ("warm", "温暖") onto measurable token deltas |
| The manifest |
Resources and prompts
Resources:
prism://tokens/active,prism://components/registry,prism://patterns,prism://audit/checklistPrompts:
build_page,design_review,import_project
Live preview
design_preview_sync renders the current page to one stable file
(PRISM_PREVIEW_FILE, default <cwd>/.prism-preview/design.html), stamped with
a revision. Because it is a single path that is overwritten in place, any watcher
can follow it — see DeepSeek Harness integration, whose
bundle also adds a Prism Preview panel (left sidebar rail, or a right-Sidebar tab)
that re-renders whenever the revision changes. That bundle is self-contained — it
packages the MCP server it launches, derives every path from where it is
installed, and declares no machine-specific configuration.
Component types
38 types the exporter can render. Values are validated by
src/component-schemas.ts (unknown keys pass through, missing keys are tolerant);
a test asserts the schema map and the catalog list the same types.
accordion · alert · avatar · badge · bento_grid · breadcrumb · button ·
card · card_grid · carousel · container · cta · faq · feature_grid ·
feature_list · footer · form · glass_card · grid · hero ·
html_fragment · image · input · marquee · navbar · pagination ·
pricing · progress · sidebar · skeleton · stats · table · tabs ·
testimonial · text · text_section · timeline · tooltip
Two of them are produced by the store rather than typed by hand: text comes from
promoteElementToComponent, and container from groupComponents. items is the
canonical list prop for every list-bearing type (links / plans / tabs /
slides are accepted aliases), and design_add_component warns instead of silently
rendering an empty component when the list is missing or is not an array.
html_fragment is how imported HTML is represented: an imported page becomes
faithful regions (header / nav / main / footer / section-N / content) that keep
the original CSS, and edits are written back through
applyHtmlFragmentsToDocument with head and scripts preserved.
Configuration
Variable | Default | Effect |
|
| Where |
| on (set | Rolling autosave of the session |
| on (set | Restore the autosave checkpoint on start |
|
| The live-preview artifact |
|
| Where |
The LLM API key is never involved: Prism has no built-in AI channel — the agent driving the MCP server is the intelligence. Nothing leaves your machine except the exported files you ask for.
Architecture
┌──────────────┐ stdio (MCP) ┌────────────────────────────────────────┐
│ MCP client │ ◄─────────────► │ src/index.ts │
│ (agent) │ │ ├─ McpServer: 42 tools │
└──────────────┘ │ ├─ 4 resources · 3 prompts │
│ └─ DesignStateStore (in-memory + disk)│
└────────────────────────────────────────┘One mutation path: every tool calls design-service, which calls
DesignStateStore. Undo/redo, activity logging, conflict detection and the
export pipeline all hang off that single store, so no two tools can disagree
about state. This is enforced: tests/mutation-path.test.ts fails if a tool
reaches past the service to a store mutator, which is what keeps the component
type allowlist, the prop schemas and the token-category check from being bypassed.
src/
├── index.ts # MCP registration + stdio bootstrap
├── state.ts # DesignStateStore: state, undo/redo, mutators
├── service/design-service.ts # the only mutation path + input validation
├── component-schemas.ts # per-type Zod prop schemas + the list-prop contract
├── tools/ # one module per area (design-tools, design-preview, …)
├── tokens.ts + tokens/dtcgi.ts # token generation and interop
├── layout/snap.ts # grid snapping used by snapComponentsToGrid
├── import-project.ts # HTML → html_fragment regions → back again
├── semantics.ts # adjective → token deltas
├── project-store.ts # .prism.json persistence + autosave
└── resources/, prompts/ # MCP context surfaces
dsh-plugin/ # DeepSeek Harness bundle (MCP connection + preview panel)The geometry layer (a layout engine, a tidy-up pass, and an auto-layout pass) was
removed: exports are CSS flow layout and never read layout coordinates, so
nothing consumed it.
Development
npm run dev # tsx watch src/index.ts
npm run build # tsc
npm test # build + compile tests + node --test (glob over .test-build/tests)
npm run lint # eslint
npm run check # lint + testThe test suite is 166 tests over 18 suites, covering the state store, the service layer, all 42 tool contracts, component schemas, the export formats, token interop, and HTML import fidelity. Three contract tests are worth knowing about:
tests/tools.test.ts— the registered tool set must equal thedesign_list_capabilitiesmanifest, every tool must accept its documented parameters and respond.tests/mutation-path.test.ts— no tool may call aDesignStateStoremutator directly; the service's validation must not be bypassable.tests/component-schemas.test.ts— the prop-schema map and the component catalog must list exactly the same types.
.githooks/pre-push runs npm run lint && npm test && npm run smoke; install it
with npm run hooks:install. CI runs the same plus a dependency audit.
Reproducible audits
These scripts check properties that unit tests cannot, and each regenerates what it needs:
Script | What it proves |
| The server starts over real stdio, handshakes, and registers the expected surface |
| The Harness bundle is well formed: manifest and exported paths, patch rows, JS syntax, and the client-half contracts (guide thunks, the Remote result envelope, the iframe sandbox, the service inject list) |
| The live-preview artifact is written, self-contained (no remote references) and revision-stamped |
| Every variant class an export emits actually has a CSS rule that takes effect in a browser |
| The reworked components behave (tabs switch, tooltip hides until hover, marquee animates, carousel scrolls) |
verify-dsh-bundle.mjs and npm run smoke run anywhere; the CSS and component
audits need playwright (a devDependency) and a cached Chromium.
Examples
examples/ holds exported pages next to their screenshots: saas-landing,
ecommerce-home and dark-dashboard, plus the DSH-era apple-style and
coffee-demo. node showcase.mjs builds the first three through the real MCP
server over stdio and re-shoots them.
History
This repository previously contained a much larger product: an Electron desktop app, a vanilla-JS dashboard, a React 19 client, Yjs real-time collaboration, JSX bidirectional sync, a scraped design-library catalog, and a built-in LLM channel — 82 tools in total. That surface was removed in the route B refactor because it was not reachable from the MCP server, not verifiable, or actively drifted from the code (much of the documentation described features that had been deleted, and the capability manifest advertised tools that were never registered).
Everything that described that removed product was deleted rather than left to
mislead: DESIGN.md, PRD.md, prism-product-definition-v2.md,
docs/archive/*, the dated V2.0 plans, and — for the same reason — the refactor
plan itself, which tracked a target surface (22 tools) the implementation never
had and quoted numbers that every later change invalidated.
Two later cleanups followed the refactor: the component catalog was trimmed from 45 to 38 types (removing entries that could not do anything meaningful in a static export, or duplicated another type), and the dead layout geometry layer was deleted. Then came the DeepSeek Harness integration — an MCP connection plus its preview panel, and the only part of this repository that talks to another application.
What remains is this README, its Chinese translation, and the
integration guide with its
Chinese translation. src/ is the source of
truth.
License
MIT.
Available Tools
28 toolsdesign_add_componentAdd UI ComponentA
Add a UI component to the design canvas. The component will appear in the client dashboard in real-time.
Component types: hero, navbar, card, card_grid, button, form, text_section, image, cta, footer, stats, timeline, pricing, testimonial, faq, feature_list, banner, tabs, accordion, carousel, modal, sidebar, breadcrumb, pagination, progress, badge, avatar
Each type has variants:
hero: 'centered', 'split', 'fullbleed'
navbar: 'simple', 'with_cta', 'mega'
card: 'product', 'feature', 'article', 'profile'
card_grid: '2col', '3col', '4col'
button: 'primary', 'secondary', 'ghost'
cta: 'centered', 'split', 'banner'
Args:
type (string): Component type
variant (string, optional): Component variant
props (object, optional): Component properties (title, subtitle, text, image_url, items, etc.)
parent_id (string, optional): Parent component ID for nesting
Examples:
design_add_component(type="hero", variant="centered", props={"title": "夏季大促", "subtitle": "精选商品5折起", "button_text": "立即抢购"})
design_add_component(type="card_grid", variant="3col", props={"items": [{...}, {...}, {...}]})
Inputs: type (required), props, variant, parent_id.
design_add_pageAdd PageA
Add a new page to the design project. The new page becomes the current active page.
Args:
name (string): Name for the new page
Example:
design_add_page(name="产品详情页")
Inputs: name (required).
design_apply_templateApply Page TemplateA
Apply a pre-built page template. Automatically adds multiple components to the current page.
Available templates:
ecommerce_home: Navbar + Hero (centered) + Card Grid (3col) + CTA (centered) + Footer
saas_landing: Navbar (with_cta) + Hero (split) + Feature List + Stats + Pricing + CTA (banner) + Footer
blog_post: Navbar + Text Section + Image + Text Section + Footer
portfolio: Navbar + Hero (centered) + Card Grid (4col) + Text Section + Footer
dashboard: Navbar + Stats + Card Grid (2col) + Feature List
Args:
template (string): Template name — 'ecommerce_home', 'saas_landing', 'blog_post', 'portfolio', 'dashboard'
Example:
design_apply_template(template="ecommerce_home")
Inputs: template (required).
design_check_promptsCheck User PromptsARead-onlyIdempotent
Check if the user has sent any natural language prompts via the client dashboard.
If a pending prompt exists, it is returned and then cleared. Use this to periodically poll for user instructions sent from the browser client.
No arguments required.
Inputs: no named parameters.
design_exportExport Design as CodeARead-onlyIdempotent
Export the current design as code in the specified format.
Supported formats:
html: Complete standalone HTML file with CSS variables and all component markup
react: React JSX component code
vue: Vue Single File Component (SFC) code
figma_tokens: Design tokens in Figma token JSON format
Args:
format (string): Export format — 'html', 'react', 'vue', 'figma_tokens'
Example:
design_export(format="html")
Inputs: format (required).
design_get_conflictsCheck Token ConflictsARead-onlyIdempotent
Check for token conflicts such as low contrast color combinations or inconsistent spacing.
No arguments required. Returns a list of conflicts found, or an empty list if none.
Inputs: no named parameters.
design_get_stateGet Current Design StateARead-onlyIdempotent
Get the complete current design state including all tokens, components, and animations.
Use this to check what's on the canvas before making changes, or to see if the user has made manual adjustments via the client dashboard.
Returns: Full design state (project name, style, all tokens, component tree, activity log)
Inputs: no named parameters.
design_initInitialize Design ProjectADestructive
Initialize a new design project. Sets the overall style, generates a complete token set, and clears any previous state.
The client dashboard will update in real-time when this is called.
Args:
project_name (string): Name for this design project
style (string): Design style — 'minimal', 'bold', 'playful', 'dark', 'editorial', 'tech'
base_color (string, optional): Override the preset base color (hex like "#6366F1")
Examples:
design_init(project_name="电商促销页", style="bold", base_color="#F97316")
design_init(project_name="极简博客", style="minimal")
Inputs: style (required), project_name (required), base_color.
design_redoRedo Last Undone OperationA
Redo the last undone operation. Re-applies the most recently undone change.
No arguments required. Returns whether the redo was successful and the current state summary.
Inputs: no named parameters.
design_remove_componentRemove ComponentADestructiveIdempotent
Remove a component from the canvas by its ID.
Args:
id (string): Component ID to remove
Example:
design_remove_component(id="comp_12345")
Inputs: id (required).
design_remove_pageRemove PageBDestructiveIdempotent
Remove a page from the design project by its ID.
Args:
page_id (string): ID of the page to remove
Example:
design_remove_page(page_id="page_12345")
Inputs: page_id (required).
design_reorder_componentReorder ComponentAIdempotent
Reorder a component relative to another component in the canvas.
Args:
from_id (string): ID of the component to move
to_id (string): ID of the reference component
position (string): Where to place the moved component relative to the reference — 'before' or 'after'
Example:
design_reorder_component(from_id="comp_123", to_id="comp_456", position="before")
Inputs: to_id (required), from_id (required), position (required).
design_set_animationSet Component AnimationAIdempotent
Set animation for a component. The client dashboard will play the animation in real-time.
Animation entries: fadeUp, fadeIn, scaleIn, slideRight, slideLeft, slideUp, spring Curves: ease, easeOut, easeInOut, spring, linear, bounce
Args:
component_id (string): Component to animate
entry (string, optional): Entry animation type
hover (string, optional): Hover animation type (scaleUp, lift, glow)
duration (number, optional): Duration in seconds (0.1 - 3.0). Default: 0.3
delay (number, optional): Delay in seconds (0 - 3.0). Default: 0
curve (string, optional): Easing curve. Default: 'easeOut'
Example:
design_set_animation(component_id="comp_123", entry="fadeUp", duration=0.5, delay=0.2, curve="spring")
Inputs: component_id (required), curve, delay, entry, +2 more.
design_set_themeSet Theme ModeAIdempotent
Set the theme mode for the design project (light or dark). The client dashboard will update accordingly.
Args:
mode (string): Theme mode — 'light' or 'dark'
Example:
design_set_theme(mode="dark")
Inputs: mode (required).
design_set_tokenSet Design TokenAIdempotent
Set or update a single design token. The client dashboard updates in real-time.
Categories: colors, typography, spacing, shadows, radii, transitions
Args:
category (string): Token category (colors, typography, spacing, shadows, radii, transitions)
key (string): Token key (e.g. "color-primary", "font-display", "space-md")
value (string): Token value (e.g. "#FF5733", "1.5rem", "12px")
Example:
design_set_token(category="colors", key="color-primary", value="#FF5733")
Inputs: key (required), value (required), category (required).
design_switch_pageSwitch PageBIdempotent
Switch to a different page in the design project.
Args:
page_id (string): ID of the page to switch to
Example:
design_switch_page(page_id="page_12345")
Inputs: page_id (required).
design_undoUndo Last OperationA
Undo the last design operation. Reverts the most recent change to the design state.
No arguments required. Returns whether the undo was successful and the current state summary.
Inputs: no named parameters.
design_update_componentUpdate Component PropertiesAIdempotent
Update properties of an existing component on the canvas. Changes appear in real-time on the client dashboard.
Args:
id (string): Component ID (from design_add_component response)
props (object): Properties to update (merges with existing)
Example:
design_update_component(id="comp_12345", props={"title": "新标题", "button_text": "点击这里"})
Inputs: id (required), props (required).
ui_check_color_contrastCheck Color Contrast (WCAG)ARead-onlyIdempotent
Check the WCAG 2.1 color contrast ratio between a foreground and background color.
Evaluates against WCAG AA (4.5:1 for normal text, 3:1 for large text) and AAA (7:1 for normal text, 4.5:1 for large text) standards.
Args:
foreground (string): Foreground/text hex color (e.g. "#333333")
background (string): Background hex color (e.g. "#FFFFFF")
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Contrast ratio, pass/fail for each WCAG level, overall grade, and actionable recommendations.
Examples:
Check dark text on white: foreground="#1A1A2E", background="#FFFFFF"
Check white text on blue: foreground="#FFFFFF", background="#3B82F6"
Check if a muted gray passes: foreground="#888888", background="#FFFFFF"
Inputs: background (required), foreground (required), response_format.
ui_generate_border_radius_scaleGenerate Border Radius ScaleARead-onlyIdempotent
Generate a border-radius scale with named levels from sharp to fully rounded.
Supports four visual styles: sharp (minimal radius), subtle (small radius), rounded (medium radius), and pill (large/pill radius).
Args:
style (string, optional): Radius visual style — 'sharp', 'subtle', 'rounded', 'pill'. Default: 'subtle'
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Border radius scale with 6 levels (none to full), px/rem values, usage guidance, and CSS custom properties.
Examples:
Subtle radius for minimal design: style="subtle"
Pill radius for playful design: style="pill"
Inputs: style, response_format.
ui_generate_color_paletteGenerate Color PaletteARead-onlyIdempotent
Generate a cohesive, harmonious color palette from a base color using color theory principles.
Supports multiple harmony schemes: monochromatic, analogous, complementary, split_complementary, triadic, and tetradic. Also generates neutral grays and semantic color roles (primary, secondary, accent, background, etc.).
Args:
base_color (string, optional): Hex color code (e.g. "#3B82F6" or "3B82F6"). If omitted, a color is derived from the style preset.
scheme (string, optional): Harmony scheme — 'monochromatic', 'analogous', 'complementary', 'split_complementary', 'triadic', 'tetradic'. Default: 'monochromatic'
style (string, optional): Style preset — 'minimal', 'bold', 'playful', 'dark', 'editorial', 'tech'. Used when base_color is omitted. Default: 'minimal'
include_neutrals (boolean, optional): Include a 11-step neutral gray scale. Default: true
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: A color palette with hex/rgb/hsl values, semantic role assignments, usage guidance, and CSS custom properties.
Examples:
Generate a triadic palette from blue: base_color="#3B82F6", scheme="triadic"
Generate a minimal palette without neutrals: style="minimal", include_neutrals=false
Generate a complementary palette for a dark theme: base_color="#10B981", scheme="complementary"
Inputs: style, scheme, base_color, response_format, +1 more.
ui_generate_design_tokensGenerate Complete Design TokensARead-onlyIdempotent
Generate a complete, cohesive design token system in a single call.
Combines colors, typography, spacing, shadows, border-radius, and transitions into one unified token set with CSS custom properties. Tokens are harmonized based on the chosen style preset.
Args:
style (string, optional): Design style preset — 'minimal', 'bold', 'playful', 'dark', 'editorial', 'tech'. Default: 'minimal'
base_color (string, optional): Override the preset's base color with a hex code (e.g. "#6366F1")
dark_mode (boolean, optional): Generate dark mode color tokens alongside light mode. Default: true
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Complete design token set with all categories (colors, typography, spacing, shadows, radii, transitions) as CSS custom properties, ready to paste into a project.
Examples:
Minimal design system: style="minimal"
Dark-first system with custom brand color: style="dark", base_color="#6366F1"
Playful system without dark mode: style="playful", dark_mode=false
Inputs: style, dark_mode, base_color, response_format.
ui_generate_gradientGenerate GradientARead-onlyIdempotent
Generate a CSS gradient from a base color with automatic color stop generation.
Supports linear and radial gradients with configurable angle and number of stops. Color stops are generated using color theory for harmonious transitions.
Args:
base_color (string): Hex color code for the gradient base (e.g. "#6366F1")
type (string, optional): Gradient type — 'linear' or 'radial'. Default: 'linear'
angle (number, optional): Gradient angle in degrees for linear gradients (0-360). Default: 135
stops (number, optional): Number of color stops (2-5). Default: 3
direction (string, optional): Color shift direction — 'analogous' (nearby hues), 'complementary' (opposite hue), 'triadic' (spread hues). Default: 'analogous'
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: CSS gradient string, color stops, and raw values.
Examples:
Purple linear gradient: base_color="#6366F1", angle=135
Blue to orange complementary gradient: base_color="#3B82F6", direction="complementary"
Radial triadic gradient: base_color="#10B981", type="radial", direction="triadic"
Inputs: base_color (required), type, angle, stops, +2 more.
ui_generate_shadow_systemGenerate Shadow SystemARead-onlyIdempotent
Generate a cohesive elevation shadow system with multiple depth levels.
Supports three visual styles: subtle (soft, minimal), medium (balanced depth), and sharp (crisp, defined edges).
Args:
style (string, optional): Shadow visual style — 'subtle', 'medium', 'sharp'. Default: 'subtle'
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Shadow system with 5 elevation levels (sm, md, lg, xl, 2xl), CSS box-shadow values, usage guidance, and CSS custom properties.
Examples:
Subtle shadows for minimal design: style="subtle"
Sharp shadows for material/tech design: style="sharp"
Inputs: style, response_format.
ui_generate_spacing_scaleGenerate Spacing ScaleARead-onlyIdempotent
Generate a consistent spacing scale for layout and component spacing.
Supports multiple generation strategies: linear (equal steps), geometric (exponential growth), and fibonacci (golden ratio progression).
Args:
base_unit (number, optional): Base unit in px — 4 or 8. Default: 8
strategy (string, optional): Generation strategy — 'linear', 'geometric', 'fibonacci'. Default: 'geometric'
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Spacing scale with named steps (0 to 3xl), px/rem values, usage guidance, and CSS custom properties.
Examples:
8px geometric scale (most common): base_unit=8, strategy="geometric"
4px fibonacci scale for fine control: base_unit=4, strategy="fibonacci"
8px linear scale: base_unit=8, strategy="linear"
Inputs: strategy, base_unit, response_format.
ui_generate_type_scaleGenerate Type ScaleARead-onlyIdempotent
Generate a modular typography scale using a chosen ratio.
Produces a full set of type sizes from 'xs' to '4xl' with px, rem, line-height, weight, and usage recommendations.
Args:
base_size (number, optional): Base font size in px. Default: 16
ratio (string, optional): Scale ratio — 'minor_second' (1.067), 'major_second' (1.125), 'minor_third' (1.2), 'major_third' (1.25), 'perfect_fourth' (1.333), 'augmented_fourth' (1.414), 'perfect_fifth' (1.5), 'golden_ratio' (1.618). Default: 'perfect_fourth'
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Typography scale with named sizes, px/rem values, line heights, and CSS variables.
Examples:
Golden ratio scale: ratio="golden_ratio"
Large base with perfect fifth: base_size=18, ratio="perfect_fifth"
Inputs: ratio, base_size, response_format.
ui_suggest_breakpointsSuggest Responsive BreakpointsARead-onlyIdempotent
Generate a responsive breakpoint system with named breakpoints, container max-widths, and CSS media queries.
Supports popular frameworks (Tailwind, Bootstrap, Material) and custom breakpoints, with mobile-first or desktop-first strategies.
Args:
framework (string, optional): Breakpoint preset — 'tailwind', 'bootstrap', 'material', 'custom'. Default: 'tailwind'
strategy (string, optional): Media query strategy — 'mobile_first' (min-width) or 'desktop_first' (max-width). Default: 'mobile_first'
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Breakpoint definitions with px values, container max-widths, usage guidance, and ready-to-use CSS media queries.
Examples:
Tailwind mobile-first: framework="tailwind", strategy="mobile_first"
Bootstrap desktop-first: framework="bootstrap", strategy="desktop_first"
Custom simple breakpoints: framework="custom"
Inputs: strategy, framework, response_format.
ui_suggest_typographySuggest Typography PairingARead-onlyIdempotent
Suggest a curated font pairing (display + body font) based on a design style.
Provides Google Fonts import links, CSS font-family declarations, recommended weights, and usage notes.
Args:
style (string, optional): Design style — 'minimal', 'bold', 'editorial', 'playful', 'tech'. Default: 'minimal'
category (string, optional): Font category preference — 'any', 'sans-serif', 'serif', 'mixed'. Default: 'any'
response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'
Returns: Font pairing with display font, body font, Google Fonts link, CSS snippet, and usage notes.
Examples:
Get a minimal font pairing: style="minimal"
Get a tech-focused serif+sans mix: style="tech", category="mixed"
Get editorial pairings: style="editorial"
Inputs: style, category, response_format.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Each tool has a clearly distinct purpose, with 'ui_' tools handling design token generation (colors, typography, spacing, etc.) and 'design_' tools managing project state, components, pages, and exports. The only potential overlap is between ui_generate_design_tokens and individual generators, but the combined nature of the former is explicitly documented, eliminating ambiguity.
Tool names follow a predictable prefix_verb_noun pattern, using 'ui_' for utility generation and 'design_' for project operations. All names are in snake_case, and verbs such as generate, suggest, check, add, remove, set, and get consistently communicate the action.
At 28 tools, the server is on the high side, but the broad scope—spanning token generation, component management, page management, animations, and exports—justifies the count. Some consolidation could be possible, but the tool set does not feel excessively padded for a comprehensive design tool.
The server covers the full design lifecycle: generating all design tokens, checking contrast, creating and managing pages and components, applying templates, setting animations and themes, exporting code, and detecting conflicts. There are no obvious gaps that would hinder an agent from completing a typical design workflow.
Related MCP Connectors
UI design from prompts, screenshots, and URLs for AI coding agents and theme tokens.
Give your agent a real design system: tokens, measured WCAG contrast, and rules to follow.
Design canvas for agents: create, edit, render and export Figma-shaped designs over MCP.
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server that gives LLMs deep knowledge of design systems and tokens, enabling intelligent design evolution, token analysis, and designer-to-developer handoffs.3713 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.MIT

Figma MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceProvides Figma design context to AI agents, enabling code generation, design system integration, and canvas manipulation through MCP.2,214-- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manage consistent multi-screen UI designs through a token-efficient MCP interface, with design system tokens, components, flows, and visual review.305 npm3AGPL 3.0