Design system guardrails for AI coding tools: tokens, components and a brand checker. Runs locally.
Connect Runs on your machine
claude mcp add brandrail -e BRANDRAIL_KEY=<BRANDRAIL_KEY> -- npx -y [email protected]{
"mcpServers": {
"brandrail": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRANDRAIL_KEY": "<BRANDRAIL_KEY>"
}
}
}
}{
"mcpServers": {
"brandrail": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRANDRAIL_KEY": "<BRANDRAIL_KEY>"
}
}
}
}{
"servers": {
"brandrail": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRANDRAIL_KEY": "<BRANDRAIL_KEY>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
BRANDRAIL_KEYOptional, secret | Optional. API key from Brandrail Dashboard > Connect, to load your organisation's Brand Kit. Without it, the repo's brandrail.config.json or starter tokens are used. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | au.com.brandrail/brandrail |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.