Skip to main content
Glama
e-brokenc0de

claude-design-mcp

by e-brokenc0de
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claude-design-mcp

No user-submitted related servers found.

    Related Servers

    • figma-unified-mcp

      sso-ss
      A
      license
      C
      quality
      C
      maintenance
      A comprehensive MCP server that enables Claude to read, create, edit, and generate code from Figma designs. Supports design tokens, code generation to multiple frameworks, and accessibility checks.
      100
      4
      MIT

    • Figma Forge

      Liljimbo
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that bridges Claude Code to Figma, enabling AI-driven design creation, modification, and export via semantic tools and WebSocket communication.
      -

    • claudecode-mcp

      trevoraspencer
      A
      license
      A
      quality
      C
      maintenance
      Local MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.
      3
      MIT

    • @dsk/mcp

      rabindranath1311
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'iterate' and 'send_message' both send chat messages to iterate on design, causing potential confusion. Also, 'export_handoff' is deprecated but remains, creating overlap with 'mint_handoff'. Overall, the set is mostly clear.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., attach_design_system, list_projects, rename_project). No mixing of styles or irregular names.

    Tool Count2/5

    32 tools is excessive for a typical MCP server, even for a complex domain. The set includes deprecated tools and several overlapping functions (e.g., generate/iterate, export_handoff/mint_handoff) that could be consolidated.

    Completeness4/5

    The tool set covers the full lifecycle of design project management: creation, generation, iteration, file management, export, and handoff. Minor gaps exist (e.g., no direct tool to update design system properties), but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources