Skip to main content
Glama
Sign In
mcp-design-models

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

      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.
      118 npm
      2
      AGPL 3.0

    • niblet

      Brittanys5005
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to ground UI work in real product screens by returning inline screenshots of concrete layouts, states, and interactions, plus fonts and icons with their recorded licenses. It also serves a bundled design workflow that settles a screen's contract and verifies the rendered result, available with or without an API token.
      MIT

    • Niblet

      tScott624
      F
      license
      Not graded
      quality
      A
      maintenance
      Gives coding agents concrete, real product screens as inline references for unresolved layout, state, or interaction questions, plus licensed fonts and icons and the recorded design system behind a chosen web screen. Also bundles a token-free design workflow, diagnostics, and command playbooks that keep UI work grounded in the agent's own product.
      -
    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources