Skip to main content
Glama
renzer83

mcp-design-models

by renzer83
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-design-models

No user-submitted related servers found.

    Related Servers

    • artisign by artisign

      artisignofficial

      artisign
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create and manage consistent multi-screen UI designs through a token-efficient MCP interface, with design system tokens, components, flows, and visual review.
      336 npm
      1
      AGPL 3.0

    • DesignPort

      MarlonJD
      F
      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
      1
      -

    • UI Canvas MCP

      Alemusica
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read and manipulate visual UI designs drawn on a canvas, translating them into precise JSON specs for production code generation.
      11,972 npm
      4
      ISC

    • maketa-mcp

      demdas
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to build and edit app-screen mockups and clickable prototypes by reading and writing structured scene models, including screen creation, node manipulation, and branching from code-based screens.
      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.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    render_screen is explicitly for a single UI screen mockup with full control, while generate_product is for turning an idea into a multi-screen product set. Although generate_product can take explicit screens, the descriptions clearly separate single-screen rendering from product-level generation, so an agent should not misselect.

    Naming Consistency5/5

    Both tool names follow the same verb_noun snake_case pattern: render_screen and generate_product. The verbs differ semantically but the structural convention is consistent and predictable.

    Tool Count3/5

    Two tools is at the thin end of the scale; the server covers only single-screen and product-level generation. It is not excessive, but the surface feels minimal for a design-model server.

    Completeness4/5

    The core workflows for rendering one screen and generating a full product are covered, including manifest output. Missing conveniences like listing past renders or editing manifest entries are minor gaps that agents can work around via the filesystem.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources