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
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Installing 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/adobe/spectrum-design-data/corp-jira)<a href="https://agentmods.dev/mcp/adobe/spectrum-design-data/corp-jira"><img src="https://agentmods.dev/badge/mcp/adobe/spectrum-design-data/corp-jira/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/corp-jira"><img src="https://agentmods.dev/badge/mcp/adobe/spectrum-design-data/corp-jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
corp-jira 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
{
"corp-jira": {
"command": "node",
"args": [
"/Users/garthdb/Projects/adobe-mcp-servers/src/corp-jira/dist/index.js"
]
}
}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 First seen · 8 lines scan A 86556d750081
corp-jira 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-16.
Other mcp servers, from other repositories
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.
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.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.