Skip to main content
Glama
Adobe XD MCP

Adobe XD MCP

by srayan-uxd

Related Servers

Alternatives to Adobe XD MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI apps to open, inspect, modify, render, and save local Figma files—including Design, Slides, FigJam, and Sites—without a Figma account, app, or API limits, and to turn designs into code using exact values.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables parsing of PSD files and extraction of layer information, design tokens, and assets to assist LLMs in converting designs to code.
      19 npm
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to read, render, and normalize design documents from Figma and Adobe XD, providing visual context plus structured design data and generating starter code for web, React, Vue, Flutter, SwiftUI, and Jetpack Compose.
      13
      343 npm
      2
      GPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI tools to read, edit, check, and export the currently open Figma file locally, with support for design files, FigJam boards, and Slides decks plus quality checks and design-to-code workflows.
      1
      MIT

    TDQS

    B3.3/5.0

    Scored across 24 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues