mcp-design-models
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QWEN_VAE | No | Checkpoint filename for the Qwen VAE model | qwen_image_vae.safetensors |
| COMFY_URL | No | ComfyUI HTTP endpoint | http://127.0.0.1:8188 |
| QWEN_CLIP | No | Checkpoint filename for the Qwen CLIP model | qwen_2.5_vl_7b_fp8_scaled.safetensors |
| QWEN_UNET | No | Checkpoint filename for the Qwen UNet model | qwen_image_2512_fp8_e4m3fn.safetensors |
| PLANNER_MODEL | No | Model used for planning when an Anthropic API key is set | claude-sonnet-4-5 |
| MCP_PREFIX_BASE | No | Sub-path under the output root for renders + manifests | studio/design/mcp |
| ANTHROPIC_API_KEY | No | Optional API key that enables planning inside generate_product | |
| COMFY_OUTPUT_ROOT | No | Where ComfyUI writes images, for absolute paths | /data/studio/renders |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_screenA | Render one UI screen mockup with the local qwen pipeline. Give the screen a name, a prose layout of the main panel, and (for consistency across a product) the shared sidebar items plus which one is active. Returns the image path and a manifest entry. Text discipline (dark theme, colors as words, only short labels real, rows as bars) is applied for you. A render takes a few minutes. |
| generate_productA | Turn a product idea into a set of screen mockups. Either pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.