BrixUI MCP Server
Allows AI agents to interact with BrixUI Design System components and design tokens via Figma, providing tools for listing, searching, and retrieving component details, as well as accessing design tokens such as colors, spacing, border radius, and typography.
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., "@BrixUI MCP Server List all components in BrixUI"
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.
BrixUI MCP Server
A production-ready Model Context Protocol server for the BrixUI Design System V1.2. Connects AI clients — Claude, ChatGPT, Cursor, Windsurf, Roo Code, Cline, and any MCP-compatible client — directly to your Figma components, design tokens, and variables.
What it does
Capability | Details |
List components | Browse all 274+ components organized by category |
Search components | Fuzzy search by name, category, or description |
Component details | Full node metadata, auto-layout, variants, fills, effects |
Design tokens | Colors, spacing, border radius, typography via Variables API |
MCP Resources |
|
Related MCP server: figmind
Requirements
Node.js 20+
Installation
Global install
npm install -g brixui-mcp-serverOr run without installing
npx brixui-mcp-serverEnvironment Setup
export FIGMA_PERSONAL_ACCESS_TOKEN=your_figma_token_hereTo use a different Figma file (optional):
export BRIXUI_FILE_KEY=your_custom_file_keyThe default BrixUI file key is 6Gvd4zkjc7K7RdRxkRF5wP.
Create a .env file for local development:
cp .env.example .env
# edit .env and add your tokenClient Configuration
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"brixui": {
"command": "npx",
"args": ["brixui-mcp-server"],
"env": {
"FIGMA_PERSONAL_ACCESS_TOKEN": "your_token_here"
}
}
}
}Or if installed globally:
{
"mcpServers": {
"brixui": {
"command": "brixui-mcp-server",
"env": {
"FIGMA_PERSONAL_ACCESS_TOKEN": "your_token_here"
}
}
}
}ChatGPT Desktop
In ChatGPT Desktop → Settings → MCP Servers → Add Server:
{
"name": "BrixUI Design System",
"command": "npx",
"args": ["brixui-mcp-server"],
"env": {
"FIGMA_PERSONAL_ACCESS_TOKEN": "your_token_here"
}
}Cursor
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"brixui": {
"command": "npx",
"args": ["brixui-mcp-server"],
"env": {
"FIGMA_PERSONAL_ACCESS_TOKEN": "your_token_here"
}
}
}
}Roo Code
Edit your Roo Code MCP config (~/.roo/mcp.json or the workspace .roo/mcp.json):
{
"mcpServers": {
"brixui": {
"command": "npx",
"args": ["brixui-mcp-server"],
"env": {
"FIGMA_PERSONAL_ACCESS_TOKEN": "your_token_here"
}
}
}
}Windsurf / Cline / other MCP clients
Any client that supports stdio MCP servers can use:
{
"command": "npx",
"args": ["brixui-mcp-server"],
"env": {
"FIGMA_PERSONAL_ACCESS_TOKEN": "your_token_here"
}
}Available Tools
Tool | Description |
| List all components grouped by category |
| Search by keyword with optional category filter |
| Full details for a component by node ID |
| All color, spacing, radius, and typography tokens |
Available Resources
URI | Description |
| Full component catalog in plain text |
| All design tokens |
| Color variables with hex values |
| Typography scale |
Example Prompts
Show all button components from BrixUISearch for card components in BrixUIGet the full details of BrixUI component with nodeId 1958:62429What are all the color tokens in BrixUI? Generate a Tailwind config from them.Show me the spacing scale from BrixUI and generate CSS custom properties for itExplain the auto-layout structure of this BrixUI navigation component: <nodeId>Generate a React component using BrixUI design tokens for a pricing cardWhat typography styles does BrixUI use? Create a matching Tailwind typography config.Development
git clone https://github.com/multicomak/BrixUI-MCP.git
cd BrixUI-MCP
npm install
cp .env.example .env
# add your FIGMA_PERSONAL_ACCESS_TOKEN to .env
npm run dev # watch mode
npm run build # production build
npm run typecheck # type checking onlyArchitecture
src/
├── index.ts # MCP server, tools, resources wiring
├── figma/
│ ├── client.ts # Figma REST API client
│ ├── types.ts # Full TypeScript types for all Figma structures
│ └── cache.ts # In-memory cache (5-min TTL)
├── tools/
│ ├── listComponents.ts
│ ├── searchComponents.ts
│ ├── componentDetails.ts
│ └── designTokens.ts
├── resources/
│ ├── components.ts
│ ├── tokens.ts
│ └── typography.ts
├── utils/
│ ├── env.ts # Token validation and env reading
│ └── logger.ts # Clean stderr logging
└── constants/
└── config.ts # Base URLs, defaults, TTLLicense
MIT
Available Tools
4 toolsget_brix_component_detailsA
Get full details for a specific BrixUI component by Figma node ID. Returns metadata, auto-layout, variants, properties, fills, strokes, effects, and child structure.
Inputs: nodeId (required).
get_brix_design_tokensA
Retrieve all design tokens from BrixUI — colors, spacing, border radius, typography, and other variables. Prefers the Figma Variables API with automatic fallback to the Styles API.
Inputs: no named parameters.
list_brix_componentsA
List all components and component sets from the BrixUI Design System, grouped by category. Returns names, IDs, descriptions, and category groupings.
Inputs: no named parameters.
search_brix_componentsB
Search BrixUI components by name, category, or description. Supports fuzzy matching and optional category filtering.
Inputs: query (required), category, limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: retrieving component details, design tokens, listing all components, and searching. There is no overlap or ambiguity between them.
All tools follow the consistent pattern 'verb_brix_noun' using snake_case, making the naming predictable and easy to remember.
With only 4 tools, the server is quite minimal. While acceptable for a focused read-only surface, the count feels thin for a comprehensive design system interface.
The server only provides read operations (get, list, search). There are no tools for creating, updating, or deleting components or design tokens, leaving significant gaps for typical workflows.
Maintenance
Related MCP Connectors
The Figma MCP server brings Figma design context directly into your AI workflow.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.4 npm9MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI clients to Figma, enabling real-time reading, creation, and modification of designs using natural language.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding agents access to Figma design data, enabling pixel-perfect implementation of designs through structured data extraction, image downloads, and design token retrieval.43 npm1MIT