BrixUI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIXUI_FILE_KEY | No | The Figma file key for BrixUI design system | 6Gvd4zkjc7K7RdRxkRF5wP |
| FIGMA_PERSONAL_ACCESS_TOKEN | Yes | Your Figma Personal Access Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_brix_componentsA | List all components and component sets from the BrixUI Design System, grouped by category. Returns names, IDs, descriptions, and category groupings. |
| search_brix_componentsB | Search BrixUI components by name, category, or description. Supports fuzzy matching and optional category filtering. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| brixui-components | Full catalog of all BrixUI components organized by category |
| brixui-tokens | All design tokens: colors, spacing, border radius, and other variables |
| brixui-colors | All color variables from the BrixUI design system with hex values |
| brixui-typography | Typography tokens and text styles from the BrixUI design system |
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.