Adobe XD MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XD_MCP_ROOTS | No | The folder(s) with your .xd files that the server is allowed to read. To allow more than one folder, separate them with ';' on Windows or ':' on Mac/Linux. If you don't set it, only the folder the server starts in is allowed. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xd_list_artboardsA | List the artboards in an Adobe XD file with their ids and names, plus document name. Set includeGeometry to also get each artboard's canvas position and size (slower on big files). |
| xd_get_artboardA | Get the layer tree of one artboard (positions, sizes, fills, strokes, text, fonts). Match by id or name (partial ok). |
| xd_extract_textB | Extract all text content from one artboard, or from every artboard if none is given. |
| xd_get_design_tokensA | Summarize colors and fonts used across the document (by frequency), plus shared styles if present. |
| xd_get_interactionsC | Return prototype interactions / flows (interactions.json) if the file has any. |
| xd_list_entriesB | List every file inside the XD archive (for debugging / finding raw data). |
| xd_read_rawA | Read a raw JSON entry from the archive (e.g. manifest, an artboard's graphicContent.agc), optionally drilling in with a dotted path like children.0.artboard.children.2. Output is truncated to maxChars. |
| xd_get_previewA | Return the embedded preview image of the XD file (first artboard render). |
| xd_extract_assetsC | Extract embedded images/resources from the XD file into an output directory. |
| xd_export_artboardA | Full-fidelity export of one artboard (or a sub-layer via nodeId) as clean JSON for rebuilding the design in another tool such as Figma: frames, rectangles (with corner radius), ellipses, lines, vector paths (SVG path data), boolean shapes, text (font, size, styled runs), fills (solid/gradient/image), strokes, shadows/effects, opacity, rotation, constraints, components, repeat grids and layout grids. Linked components (syncRef) are resolved to their real content. Text is normalised (top-left box, baselineY, line breaks as , alignment, autoResize, underline runs). The full transform matrix is given with transformOrigin top-left. Positions are relative to the parent; masks are in the masked group's local space. Images are referenced by imageRef; pass assetsDir to save them. Big screens are split into pages (page / pageCount / hasMore); each page lists whole top-level layers. Use nodeId to drill into one layer. |
| xd_render_artboardA | Render one artboard (or one layer via nodeId) to a PNG so you can SEE the result and verify a rebuild. Renders the full-fidelity export (linked components, masks, gradients, images, shadows, text) as one SVG and screenshots it in a local headless Chrome/Edge. Set XD_MCP_CHROME if the browser isn't found automatically. Nothing is uploaded. |
| xd_infer_layoutA | Phase 2 of a conversion: from the exact export of a screen, propose frames with AUTO-LAYOUT intent. Clusters layers into cards by containment, detects rows/columns and header-style space-between rows, derives item spacing (median gap) and padding (rounded to a grid), marks equal-width cards and full-width text as FILL, keeps illustrations/photos/masked or rotated groups as fixed leaves, puts overlapping decorations in absoluteChildren, turns centred-label rectangles into buttons, and suggests semantic layer names. Leaves reference the exact layers by ref. Returns a drift report (pixelDeltaEstimate, within3px, within5px, elementsAbsolute, elementsAutoLayout) so you know how far the auto-layout version moves things. A heuristic proposal: rebuild it beside the exact copy and compare with xd_render_artboard. |
| xd_export_svgA | Export one or more layers as ONE self-contained SVG (vectors, gradients, shadows, masks and images embedded), so an illustration, icon or any drawing can be imported into Figma as a single vector instead of dozens of pieces. Pass the layer ids of a group, or the |
| xd_font_reportA | Fonts used by the file (or one artboard): family, weights/styles, sizes, how often, whether each family is installed on this computer, a substitution table for missing weights (e.g. Medium -> Regular), and a licence note. Run this before rebuilding a design elsewhere and warn the user about missing fonts. Only reads font names; never creates or alters fonts. |
| xd_pingA | Health check: server version, allowed folders, Node and platform, whether a browser for xd_render_artboard was found, and a built-in self-test of the parser and exporter. Pass a file to also check that it opens. |
| xd_list_componentsB | List the reusable components (symbols) defined in the file: id, name, size. |
| xd_export_componentB | Export one component master (see xd_list_components) in the same format as xd_export_artboard. |
| xd_get_shared_assetsC | Document-level libraries: saved color swatches, library colors and character (text) styles. |
| xd_get_design_systemA | Extract the design system actually used in the file: color palette (ranked, with fill/text/stroke usage), typography styles and size scale, corner radii, stroke widths and shadows. Output as json, css (custom properties), tailwind (theme.extend) or figma-variables (variable collections, text styles named by role and effect styles, ready to create in Figma). |
| xd_audit_designA | Design QA. Checks text contrast (WCAG, background estimated), tiny text, small tap targets on interactive layers, placeholder text, near-duplicate colors, too many fonts/sizes and default layer names. Returns findings with artboard and layer ids plus per-check totals. |
| xd_find_layersA | Search layers across the file by text content, layer name, type (text, rectangle, ellipse, path, group, ...) or color (#rrggbb, matched with a small tolerance). |
| xd_export_copyA | Export all text content (a copy deck) for translation or review, as json or csv. CSV cells are protected against spreadsheet formula injection. |
| xd_get_flowB | Prototype flow map: every interaction (tap/hover/time triggers, transitions, destinations) with source screen and layer, the home screen, and a Mermaid flowchart of screen-to-screen links. |
| xd_project_overviewA | Scan a folder (inside the allowed roots) for .xd files and summarize each: name, size, artboard and component counts, whether it has a prototype. Searches up to 3 levels deep, max 60 files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| xd-to-figma | Recreate one artboard in Figma (needs the Figma MCP server too). |
| xd-to-code | Generate a responsive UI component from one artboard. |
| xd-design-review | Run a design QA pass over a whole file. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
There are several overlapping tool clusters: design-system/tokens/shared-assets extraction, get-artboard vs export-artboard, get-interactions vs get-flow, and extract-text vs export-copy. Descriptions usually clarify the intended use, but an agent can still plausibly misselect within these pairs.
All tools use the xd_ prefix and most follow a verb_noun pattern such as xd_list_artboards, xd_get_flow, and xd_export_svg. A few names are noun phrases or exceptions (xd_project_overview, xd_font_report, xd_ping), but the convention remains readable and predictable.
At 24 tools, the surface is heavy for an MCP server and includes several specialized and debug-oriented tools. Most tools serve the broad XD extraction/conversion workflow, but the count is borderline rather than comfortably scoped.
The read-only extraction and conversion surface is comprehensive: artboards, components, assets, text, design tokens, interactions, rendering, QA, and conversion planning are covered. Minor gaps remain around batch artboard/component export and some write/edit operations, though writing may be intentionally out of scope.