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.
npx agentmods add mcp/adobe/spectrum-design-data/figmagit clone --depth 1 https://github.com/adobe/spectrum-design-dataWrote 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/adobe/spectrum-design-data/figma)<a href="https://agentmods.dev/mcp/adobe/spectrum-design-data/figma"><img src="https://agentmods.dev/badge/mcp/adobe/spectrum-design-data/figma.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
figma 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 today.
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
{
"figma": {
"type": "http",
"url": "http://127.0.0.1:3845/mcp"
}
}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.
- today First seen · 6 lines scan A 6dc19448969d
figma is an MCP server published in the GitHub repository adobe/spectrum-design-data (151 stars, last pushed today), licensed Apache-2.0. 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-09-03.
Other mcp servers, from other repositories
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.
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.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
designscan
Extract a website’s design tokens (colors, type, spacing, shadows) as DESIGN.md, W3C, or CSS. Runs locally from the @designscan/extractor npm package.
claude-design
MCP server "claude-design" as configured in e-brokenc0de/claude-design-mcp. Runs ${CLAUDE_PROJECT_DIR:-.}/dist/server.js with node. Needs 3 environment variables to run.
saglitzdesign-mcp
Expert design & marketing MCP: UI/UX, design languages, SEO/GEO, tokens, a11y, recipes. Runs locally from the saglitzdesign-mcp npm package.