Skip to main content
Glama
Sign In
srayan-uxd

Adobe XD MCP

by srayan-uxd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Adobe XD MCP

No user-submitted related servers found.

    Related Servers

    • Adobe XD MCP Server

      dekdee
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables Claude to interact with Adobe XD files, extract design information, and generate React components from designs.
      19 npm
      21
      MIT

    • psd-mcp-server

      drapon
      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.
      18 npm
      1
      MIT

    • DesignPort

      MarlonJD
      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
      2
      GPL 3.0

    • layerbridge

      muradyf
      A
      license
      Not graded
      quality
      A
      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

    • F-MCP (Figma MCP Bridge)

      atezer
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to read, analyze, and modify Figma designs, manage design tokens, and create prototype connections, all while keeping data local.
      63
      86 npm
      10
      MIT

    • AI-Canvas MCP Server

      laoluojuhai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect, modify, export, and validate design documents with 47 tools covering design, code generation, branding, and print/mockup workflows.
      2 npm
      2
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation3/5

    Several clusters overlap: xd_get_design_tokens, xd_get_design_system, and xd_get_shared_assets all report colors/fonts; xd_extract_text and xd_export_copy both dump text; xd_get_interactions and xd_get_flow both expose prototype links. Descriptions clarify intended differences, but an agent could still misselect within these clusters.

    Naming Consistency4/5

    All tools use the xd_ prefix and snake_case, mostly following a verb_noun pattern such as xd_list_artboards, xd_export_artboard, xd_find_layers, and xd_audit_design. xd_project_overview is a minor noun-phrase outlier, but the overall convention remains clear and predictable.

    Tool Count3/5

    At 19 tools the surface is borderline heavy for a read/export/QA server, and the overlapping text, design-system, prototype, and artboard extraction tools suggest some consolidation is possible. The breadth is defensible, but it sits above the ideal 3-15 range.

    Completeness4/5

    Coverage is broad: artboards, components, text, assets, design tokens/system, prototype flows, QA, search, raw archive access, and project scanning are all represented. Minor gaps remain, such as batch/multi-artboard export or per-artboard previews, but agents can generally work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources