Design system guardrails for AI coding tools: tokens, components and a brand checker. Runs locally.
MCPpedia last refreshed this data
au.com.brandrail/brandrail is an MCP server that design system guardrails for AI coding tools: tokens, components and a brand checker. Runs locally. Its tool list has not been published yet over stdio and http, requires no API key, and scores 64/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"brandrail": {
"args": [
"-y",
"brandrail",
"mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Design system guardrails for AI coding tools: tokens, components and a brand checker. Runs locally.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked brandrail against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in design / marketing
Design tokens from any live site: colours, type, spacing, components, drift against a baseline.
Draw and visually collaborate with your agents on tldraw's canvas.
Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
MeiGen-AI-Design-MCP — Turn Claude Code / OpenClaw into your local Lovart. Local ComfyUI, 1,400+ prompt library, multi-direction parallel generation.
MCP Security Weekly
Get CVE alerts and security updates for au.com.brandrail/brandrail and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Your design system, in every AI coding tool.
AI coding tools don't know your design system, so every screen comes out with different colours, buttons and spacing. Brandrail's MCP server gives the tool your Brand Kit and components before it writes UI, then checks what it wrote and returns the fixes, so it corrects itself before you see the code.
get_guidelines, get_design_tokens, find_component, get_component_docs,
get_template, get_migration_map, validate_snippet.In each repo:
npx brandrail connect
It signs you in through the browser and writes the MCP config and rule files for Claude Code, Cursor, Copilot, Codex, Windsurf and Gemini CLI. The files it writes hold no key, so commit them.
You type the code it shows on the Brandrail page, so nobody can approve a terminal for you with a link. The
key is made on your machine (only its hash is sent) and saved outside the repo. To help you recognise the
request, the terminal's description (user@computer · folder) is shown on the approval page.
Or add the MCP server by hand (works without an account):
{
"mcpServers": {
"brandrail": { "command": "npx", "args": ["-y", "brandrail", "mcp"] }
}
}
Cursor install link:
cursor://anysphere.cursor-deeplink/mcp/install?name=brandrail&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImJyYW5kcmFpbCIsIm1jcCJdfQ==
Set BRANDRAIL_KEY (an API key from Dashboard → Connect) to load your organisation's Brand Kit without
running connect. Full docs: https://www.brandrail.com.au/docs/connect
BRANDRAIL_KEY is only ever sent to www.brandrail.com.au (or localhost). If BRANDRAIL_API_URL points
anywhere else, the CLI says so on every run and won't send the key; sign in to that server with connect.
| Tool | What it does |
|---|---|
get_guidelines | The project's design system rules: components to use in its framework, allowed tokens, what the checker enforces. Called once before writing UI. |
get_design_tokens | Every colour, spacing, radius and type token with the CSS variable to use. |
find_component | Finds the component for a need ("date picker", "primary action") with its import, rules and an example. |
get_component_docs | Full docs for one component in the project's framework: import or tag, props, rules, example. |
get_template | A whole page (list, detail, form, settings, dashboard, sign-in) built from your components, with the files to create and the page's rules. |
get_migration_map | What replaces each piece of Material, MUI, Bootstrap, Ant, Chakra or PrimeNG. |
validate_snippet | Runs the checker on generated code and returns a brand score and each fix. |
The same package is a command-line checker:
npx brandrail check --changed # only what you changed vs origin/main
npx brandrail scan http://localhost:3000 --pages 3 # a running app, in a real browser
npx brandrail migrate # what's left of Material, MUI, Bootstrap and others
Every command and option: packages/cli/README.md and https://www.brandrail.com.au/docs/cli
The MCP server and CLI run on your machine. Code is checked locally and never up