adobe/spectrum-design-data is a monorepo containing the design tokens, component schemas, specifications, and related datasets that define Adobe's Spectrum design system; a monorepo keeps these related packages in one repository. It is for Adobe Spectrum SDK and tooling developers who need canonical design-system data and validation artifacts. The catalogue add-ons provide workflows and integrations for working with this design data.
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/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/design-data)<a href="https://agentmods.dev/mcp/adobe/spectrum-design-data/design-data"><img src="https://agentmods.dev/badge/mcp/adobe/spectrum-design-data/design-data/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/adobe/spectrum-design-data/design-data"><img src="https://agentmods.dev/badge/mcp/adobe/spectrum-design-data/design-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
design-data 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 1mo 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
{
"design-data": {
"command": "npx",
"args": [
"-y",
"@adobe/design-data-agent-mcp"
],
"env": {
"DESIGN_DATA_ROOT": ".",
"DESIGN_DATA_BIN": "sdk/target/release/design-data",
"DESIGN_DATA_PATH": "packages/design-data/tokens",
"DESIGN_DATA_COMPONENTS": "packages/design-data/components",
"DESIGN_DATA_FIELDS": "packages/design-data/fields"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago Changed 2bf46ff1d556
- 1mo ago First seen · 16 lines scan A a6a03064a0f9
design-data is an MCP server published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed yesterday), 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.
figma-mcp-bridge
MCP server "figma-mcp-bridge" as configured in atezer/FMCP. Runs /REPLACE/WITH/ABSOLUTE/PATH/TO/FCM/dist/local-plugin-only.js with node. Needs 1 environment variable to run.
mimic-ai
Builds Figma from your design system: real components and tokens, enforced, learning every build. Runs locally from the @miapre/mimic-ai npm package.
uisandbox
Play with your app's design in the browser: load a build, turn the knobs, export the code. Runs locally from the uisandbox-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.
colors-le
Extract colors from stylesheets and code, with their notation and position. Runs locally from the colors-le-mcp npm package.