Skip to main content
Glama
Sign In
leethoneid

Figma Spec Compressor

by leethoneid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Figma Spec Compressor

No user-submitted related servers found.

    Related Servers

    • Figma To Code MCP

      felixAnhalt
      A
      license
      Not graded
      quality
      A
      maintenance
      Transforms Figma design data into a compact, LLM-friendly format for code generation, reducing size by 99.5% while preserving UI-critical information.
      836 npm
      7
      MIT

    • Figma MCP

      alucardeht
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Figma files through intelligent API access, providing navigation, asset extraction, and design token retrieval with 95% token-optimized compact tree output format.
      15
      1
      MIT

    • smart-figma-mcp

      drake-yuan
      F
      license
      B
      quality
      B
      maintenance
      Enables mapping Figma designs to a project's own component library — shadcn/ui, antd, mui, or Astryx — by resolving variants against authoritative component contracts instead of guessing. It compiles Figma nodes into code and then deterministically writes the resulting files into the codebase, cleaning node-id artifacts and updating exports.
      12
      9 npm
      -

    • Figma Context MCP

      cola-sk
      A
      license
      A
      quality
      D
      maintenance
      Converts Figma designs into structured code context with token-aware styling, enabling AI agents to generate production-level frontend code.
      1
      5 npm
      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

    A3.6/5.0

    Scored across 2 tools

    Disambiguation4/5

    Both tools perform the same core operation (compressing Figma data into a spec), so an agent must read descriptions to pick correctly. However, the split is clean and explicit: one takes raw JSON, the other takes a live Figma URL, which makes selection straightforward in practice.

    Naming Consistency5/5

    Both names follow the same verb_noun pattern with a shared prefix (compress_figma_json, compress_figma_url). The distinguishing suffix directly reflects the input source, which is exactly the right naming convention here.

    Tool Count3/5

    Two tools is thin for a server, though it matches the narrow purpose of compressing Figma input. Each tool earns its place by covering a distinct input source, but the surface is minimal enough to feel borderline.

    Completeness4/5

    The two main input paths (raw JSON and live URL) are covered, along with two output formats (YAML/Markdown). Minor gaps exist around batch processing, node selection options, or caching, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources