Validator MCP server
{
"mcpServers": {
"swatchdog-check": {
"type": "http",
"url": "https://swatchdog-mcp-970396648818.us-central1.run.app/mcp"
}
}
}{
"mcpServers": {
"swatchdog-check": {
"type": "http",
"url": "https://swatchdog-mcp-970396648818.us-central1.run.app/mcp"
}
}
}{
"mcpServers": {
"swatchdog-check": {
"type": "http",
"url": "https://swatchdog-mcp-970396648818.us-central1.run.app/mcp"
}
}
}{
"servers": {
"swatchdog-check": {
"type": "http",
"url": "https://swatchdog-mcp-970396648818.us-central1.run.app/mcp"
}
}
}{
"mcpServers": {
"swatchdog-check": {
"type": "http",
"url": "https://swatchdog-mcp-970396648818.us-central1.run.app/mcp"
}
}
}What it does
Swatchdog is an MCP server that runs on-demand design-token drift checks for AI coding assistants. It compares generated CSS against a design system (either a curated pack or your own tokens) and reports which color, radius, spacing, and type values deviate from the system, with suggestions for the nearest matching token. Intended for developers using Claude, Cursor, or other MCP clients who want their AI agents to write brand-consistent styles.
- Have an AI agent generate CSS, then call Swatchdog to verify all colors, spacing, and typography match your design tokens before committing the code.
- Check a stylesheet against a curated design pack (Workbench, Showcase, Terminal, or Studio) to detect and fix off-brand values.
- Extract your own tokens from tailwind.config.js or CSS variables and pass them to Swatchdog so it reports which hard-coded values should be replaced with token references.
Tools this server exposes
| Tool | Does |
|---|---|
| check_drift | Checks CSS or markup against a design pack or a custom token set, returning all off-token values with their nearest matching token suggestion. |
| check_design_drift | Connector endpoint for BYO-mode checks; accepts your design tokens and code, returns drift violations with suggested token replacements. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.
This server has not seen a commit in 2 mo. It may still work, but nobody is currently fixing it — check the alternatives before you build on it.