Skip to main content
Glama
ccpopy

codesign-mcp

by ccpopy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codesign-mcp

No user-submitted related servers found.

    Related Servers

    • 蓝湖 Design Schema MCP

      andyjin5
      A
      license
      A
      quality
      C
      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

    • figma-bridge-mcp

      KaiUweHella
      A
      license
      B
      quality
      A
      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
      253 npm
      1
      MIT

    • Figma Native MCP

      tomasmarekk
      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

    • lanhu-design-mcp

      blantian
      A
      license
      A
      quality
      A
      maintenance
      MCP server for macOS that reads Lanhu designs, analyzes UI structures, and exports fine-grained design assets for multiple platforms.
      8
      5
      MIT

    • pholly-figma-mcp

      mubzie
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP bridge for live Figma documents, enabling design inspection, editing, asset export, component authoring, and variable management through a plugin and WebSocket server without consuming Figma REST API requests.
      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

    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

    ActivityMaintained
    ResponsivenessResponsive

    Resources