- Explore MCP Servers
- design-system-mcp
Design System Mcp
What is Design System Mcp
The MCP (Model Context Protocol) server is a tool that provides detailed information about component properties and design tokens, facilitating design consistency and accessibility across components.
Use cases
The MCP server can be used by developers and designers to retrieve component props for UI elements and access design tokens to ensure uniform styling throughout a design system. It is especially useful for integrating design principles into UI component libraries.
How to use
To utilize the MCP server, run the provided in-memory debug script using the command deno task debug-mcp. This allows users to make sample calls and view responses for component properties and tokens, enhancing testing and debugging.
Key features
Key features include the getComponentProps function, which fetches details about component properties, and the getTokens function that retrieves design token information. The server also supports token generation from JSON files using Style Dictionary.
Where to use
The MCP server is suitable for usage in design systems, component libraries, and any application where consistent design tokens and component properties are critical for user interface development.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Overview
What is Design System Mcp
The MCP (Model Context Protocol) server is a tool that provides detailed information about component properties and design tokens, facilitating design consistency and accessibility across components.
Use cases
The MCP server can be used by developers and designers to retrieve component props for UI elements and access design tokens to ensure uniform styling throughout a design system. It is especially useful for integrating design principles into UI component libraries.
How to use
To utilize the MCP server, run the provided in-memory debug script using the command deno task debug-mcp. This allows users to make sample calls and view responses for component properties and tokens, enhancing testing and debugging.
Key features
Key features include the getComponentProps function, which fetches details about component properties, and the getTokens function that retrieves design token information. The server also supports token generation from JSON files using Style Dictionary.
Where to use
The MCP server is suitable for usage in design systems, component libraries, and any application where consistent design tokens and component properties are critical for user interface development.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Content
MCP Server for Design System
This project includes an MCP (Model Context Protocol) server that provides information about component props and design tokens.
MCP Server Features
The MCP server offers two main tools:
getComponentProps: Retrieves information about component propertiesgetTokens: Retrieves design token information from token files
Debugging the MCP Server
To debug the MCP server:
- Run the in-memory debug script:
$ deno task debug-mcp
This script:
- Creates an in-memory client-server connection
- Makes sample calls to retrieve component props and tokens
- Displays the results in the console
You can modify the debug script to test different components or specific token requests.
Design Token Generation
Design tokens are stored as JSON files in the src/design-system/tokens directory:
color.json: Color palette and theme colorstypography.json: Font families, sizes, weightsspacing.json: Spacing scaleradius.json: Border radius values
Token Generation Process
Tokens are processed using Style Dictionary with the following workflow:
- Define token values in JSON files in the
tokensdirectory - Style Dictionary processes these tokens according to the configuration in
src/design-system/style-dictionary/config.json - Output formats include:
- CSS variables (tokens.css)
- JavaScript module (tokens.js)
- TypeScript declarations (tokens.d.ts)
To generate tokens:
$ deno task build-tokens
The generated files are placed in the src/design-system/style-dictionary/dist directory and can be imported into your components.
Dev Tools Supporting MCP
The following are the main code editors that support the Model Context Protocol. Click the link to visit the official website for more information.










