Skip to main content
Glama
BrixUI MCP Server

BrixUI MCP Server

by multicomak

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

brixui://components, brixui://tokens, brixui://colors, brixui://typography


Related MCP server: figmind

Requirements


Installation

Global install

npm install -g brixui-mcp-server

Or run without installing

npx brixui-mcp-server

Environment Setup

export FIGMA_PERSONAL_ACCESS_TOKEN=your_figma_token_here

To use a different Figma file (optional):

export BRIXUI_FILE_KEY=your_custom_file_key

The default BrixUI file key is 6Gvd4zkjc7K7RdRxkRF5wP.

Create a .env file for local development:

cp .env.example .env
# edit .env and add your token

Client 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_brix_components

List all components grouped by category

search_brix_components

Search by keyword with optional category filter

get_brix_component_details

Full details for a component by node ID

get_brix_design_tokens

All color, spacing, radius, and typography tokens

Available Resources

URI

Description

brixui://components

Full component catalog in plain text

brixui://tokens

All design tokens

brixui://colors

Color variables with hex values

brixui://typography

Typography scale


Example Prompts

Show all button components from BrixUI
Search for card components in BrixUI
Get the full details of BrixUI component with nodeId 1958:62429
What 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 it
Explain the auto-layout structure of this BrixUI navigation component: <nodeId>
Generate a React component using BrixUI design tokens for a pricing card
What 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 only

Architecture

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, TTL

License

MIT

Available Tools

4 tools
get_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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: retrieving component details, design tokens, listing all components, and searching. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow the consistent pattern 'verb_brix_noun' using snake_case, making the naming predictable and easy to remember.

    Tool Count3/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.
      4 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI clients to Figma, enabling real-time reading, creation, and modification of designs using natural language.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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 npm
      1
      MIT