All servers / Design / Adobe Spectrum MCP server
Adobe Spectrum MCP server
MCP server for Spectrum design tokens, component schemas, and design guidelines (embedded, offline)
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.14.5. Package: @adobe/design-data-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (4.3 seconds including download)
- Tools offered: 11
- Last published: 2026-11-18
- Weekly downloads (npm): 4,821
- License: Apache-2.0 · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
design-data-primerno parametersGet a structural overview of the Spectrum design dataset: token count, available mode-sets (color-scheme, scale, contrast), component list, taxonomy fields, guideline categories, and data provenance. Call this at the start of a design-token session to understand what data is available.
design-data-query3 of 3 parameters describedFilter Spectrum tokens by a query expression. Filterable fields: property, component, variant, state, colorScheme, scale, contrast, uuid. `key=value` pairs join with `,` (AND) or `|` (OR); `!=` negates and `*` is a wildcard. `component` matches tokens bound to that component by its relationships. Examples: `component=button`, `component=button,state=hover`, `property=*color*`, `colorScheme=dark`. Property names are exact or wildcard (e.g. `*color*`); variant values are listed in the dataset, so `variant=accent` matches nothing. Returns { total, shown, tokens }: each token has its name, final value (aliases already followed; `values` by mode instead when it differs by colorScheme, scale or contrast), layer, uuid and modes, active tokens first. At most `limit` (default 25) are shown; when `total` is larger, narrow the filter (state=, property=, colorScheme=) instead of raising the limit. Pass detail "full" for the complete token objects.
design-data-suggest2 of 2 parameters describedSuggest Spectrum tokens matching a natural-language intent using Jaccard similarity scoring over token name segments, name-object fields, and description text. Returns matches ranked by confidence, each with its token name, final value (aliases already followed; `values` by mode when it differs by mode), layer, uuid and modes. Use when the user describes what they need rather than knowing the token name.
design-data-component1 of 1 parameter describedGet the full component declaration for a Spectrum component by ID. Returns the component's displayName, description, and all available options (variants, sizes, states, boolean props, etc.). Component IDs are kebab-case, e.g. button, action-button, text-field, picker.
design-data-component-search3 of 3 parameters describedSearch Spectrum components by name, description, or documentation text (e.g. "date", "form input", "navigation"). Returns id, displayName, category, and a snippet per match. Use the id with design-data-component for the full declaration.
design-data-resolve9 of 9 parameters describedResolve the concrete value of a Spectrum token property for a given mode-set context (color-scheme, scale, contrast). Optionally narrow by component, variant, state, or colorRole; a property name is shared by many tokens, so narrowing is usually needed. Returns the winning token (active tokens rank above deprecated ones) with its resolved value. `ambiguous: true` means several tokens still match: see `candidateCount` and `alternatives`, and narrow further.
design-data-guideline-list1 of 1 parameter describedList available Spectrum design guideline pages. Returns catalog entries with slug, title, category, status, and sourceUrl. Use this to discover guideline IDs before calling design-data-guideline. Optionally filter by category: designing, fundamentals, developing, or support.
design-data-guideline1 of 1 parameter describedGet the full guideline document for a Spectrum design page by ID. Returns the guideline's title, category, metadata, and documentBlocks body (purpose, guideline, accessibility, do-dont, and examples blocks). Call design-data-guideline-list first to discover available guideline IDs. The `id` is the `slug` value returned by design-data-guideline-list.
design-data-visual-recipe1 of 1 parameter describedGet the visual recipe (parts, layout, and token bindings used to draw it) for a Spectrum component by ID, e.g. button, action-button, badge. Only components with a recipe are available; use design-data-render to draw one as SVG.
design-data-render12 of 12 parameters describedRender a Spectrum component from its visual recipe, resolving token values for the given size, states, options, and mode. Returns SVG markup as text by default, or a PNG image with format "png". Only components with a recipe can be rendered (see design-data-visual-recipe). SVG label boxes are sized with Adobe Clean Spectrum VF when it is installed on this machine (not with fontPath), otherwise with Source Sans 3 widths. PNG text uses Adobe Clean Spectrum VF when it is installed on this machine (found automatically, or set with the fontPath argument or the DESIGN_DATA_FONT environment variable), else Adobe Clean VF (Roman .ttf), else a bundled open font. The result includes a font status: when font.fallback is true, tell the user which font was used (font.using, font.family), that its metrics, spacing and wrapping may differ, and pass on font.help; do not call the image exact. When font.found is true, do not tell the user to download anything.
design-data-font-status1 of 1 parameter describedCheck which font draws text in PNG renders from design-data-render: Adobe Clean Spectrum VF if it is installed on this machine, else Adobe Clean VF (Roman .ttf), else a bundled open font. Returns { found, fallback, using, family, installed, rejected, related, searched, help }; found means Adobe Clean Spectrum VF (or a font you chose), installed means a font file on this machine is used. When fallback is true, tell the user and pass on help (Adobe employees can download the font from the Brand Center; they install the .ttf, or point DESIGN_DATA_FONT or fontPath at it). If the user says it is installed but found is false, ask for the file path and pass it as fontPath. Do not tell the user to download anything when found is true. Never offer or attach the font file.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.