Skip to main content
Glama
codesign-mcp

codesign-mcp

by ccpopy

Related Servers

Alternatives to codesign-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for reading and analyzing Lanhu (Blue Lake) design projects, providing tools to retrieve design lists, previews, node trees, schemas, and exportable resources.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local MCP server that reads and edits a Figma Design file through a development plugin, creating real editable layers (frames, text, shapes, components, images) rather than flattened screenshots. It runs entirely on loopback with no personal access token, API key, or cloud bridge, letting an agent inspect documents, build and update layers, export previews, and wire up prototype navigation.
      10
      539 npm
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A local MCP server that lets AI assistants inspect, create, and update designs in Figma Desktop through a development plugin, requiring no Figma Personal Access Token or cloud services.
      12
      16 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that lets MCP clients inspect and edit the Figma document currently open in the Figma desktop app using a local bridge and development plugin.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for macOS that reads Lanhu designs, analyzes UI structures, and exports fine-grained design assets for multiple platforms.
      8
      29 PyPI
      5
      MIT

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: login, logout, status, debug, download slice, get image, get spec, list artboards. No overlap in functionality.

    Naming Consistency3/5

    Naming is inconsistent: some tools have 'codesign_' prefix, others like 'download_slice' lack it, and 'debug_collect_network' uses a different prefix. While snake_case is used, the pattern is not uniform.

    Tool Count5/5

    8 tools is an appropriate number for a design-to-code MCP server. It covers essential operations without being bloated or insufficient.

    Completeness4/5

    Completeness is high: the tool set covers login lifecycle, listing designs, fetching specs, downloading assets, and debugging. Minor gaps like version handling or design upload could exist, but core workflows are well-covered.

    Maintenance

    ActivityStale
    ResponsivenessUsually handled