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-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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 2mo 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.
- 2mo 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 5mo 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.
claude-design compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| claude-designe-brokenc0de/claude-design-mcp | MCP server | 0 | 5mo ago | MIT | A | — | Claude Code |
| design-dataadobe/spectrum-design-data | MCP server | 159 | yesterday | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| figmaadobe/spectrum-design-data | MCP server | 159 | yesterday | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| figbridgerudraptpsingh/figbridge | MCP server | 15 | 28d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mimic-aimiapre/mimic-ai | MCP server | 15 | 29d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| figma-mcp-bridgeatezer/FMCP | MCP server | 10 | 23d ago | MIT | A | — | Claude Code |
| uisandboxIdeelab/uisandbox | MCP server | 7 | 16d ago | MIT | A | — | Claude Code |