Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/e-brokenc0de/claude-design-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/e-brokenc0de/claude-design-mcp/claude-design)<a href="https://agentmods.dev/mcp/e-brokenc0de/claude-design-mcp/claude-design"><img src="https://agentmods.dev/badge/mcp/e-brokenc0de/claude-design-mcp/claude-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/e-brokenc0de/claude-design-mcp/claude-design"><img src="https://agentmods.dev/badge/mcp/e-brokenc0de/claude-design-mcp/claude-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"claude-design": {
"type": "stdio",
"command": "node",
"args": [
"${CLAUDE_PROJECT_DIR:-.}/dist/server.js"
],
"env": {
"CLAUDE_DESIGN_CDP_PORT": "9222",
"CLAUDE_DESIGN_CDP_USER_DATA_DIR": "${CLAUDE_PROJECT_DIR:-.}/.auth/cdp-chrome",
"CLAUDE_DESIGN_STATE_DIR": "${CLAUDE_PROJECT_DIR:-.}/.claude-design-mcp"
},
"timeout": 600000
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 15 lines scan A eb755de7d078
claude-design is an MCP server published in the GitHub repository e-brokenc0de/claude-design-mcp (0 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
design-data
MCP server and Claude Code skill for the design-data agent surface — read tools run in-process via wasm. Runs locally from the @adobe/design-data-agent-mcp npm package. Needs 5 environment variables to run.
figma
MCP server "figma", hosted remotely at 127.0.0.1, as configured in adobe/spectrum-design-data.
roast-my-design-system
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system. Runs locally from the roast-my-design-system npm package.
colors-le
Extract colors from stylesheets and code, with their notation and position. Runs locally from the colors-le-mcp npm package.
figbridge
Free, local MCP bridge for Figma — HTML, CSS, Tailwind, tokens, agent handoff bundles. Runs locally from the figbridge-mcp npm package. Needs 1 environment variable to run.
standby-design-mcp
Generate design systems: OKLCH color palettes, fluid type scales, spacing, shape and icon tokens. Runs locally from the standby-design-mcp npm package.