Superdesign MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| superdesign_generateC | Returns design specifications for Claude Code to generate UI designs, wireframes, components, logos, or icons |
| superdesign_iterateC | Returns iteration instructions based on existing design and feedback |
| superdesign_extract_systemC | Returns instructions for extracting design system from screenshot or image |
| superdesign_listC | List all created designs in the workspace |
| superdesign_galleryC | Generate an HTML gallery to view all designs in a browser |
| superdesign_deleteC | Delete a design file and update metadata |
| superdesign_cleanupB | Clean up old design files based on age and count limits |
| superdesign_live_galleryC | Start a live gallery server with real-time updates and file watching |
| superdesign_check_filesB | Check for file changes by comparing current files with a manifest (for gallery refresh integration) |
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 9 tools
Each tool has a clearly distinct purpose with no ambiguity: checking files, cleaning up, deleting, extracting systems, generating galleries, generating designs, iterating, listing, and live galleries. The descriptions clearly differentiate their functions, such as 'superdesign_generate' for creating designs versus 'superdesign_iterate' for refining them, preventing misselection.
All tool names follow a consistent 'superdesign_' prefix with a descriptive verb_noun pattern (e.g., superdesign_check_files, superdesign_generate). There are no deviations in style or convention, making the naming predictable and easy to understand across the set.
With 9 tools, the count is well-scoped for a design-focused server, covering key operations like creation, iteration, listing, and cleanup. Each tool earns its place by addressing specific aspects of the design workflow, avoiding bloat or thin coverage.
The tool set provides comprehensive coverage for design workflows, including create (generate), read (list, gallery), update (iterate), and delete (delete, cleanup), with additional utilities like file checking and live galleries. A minor gap exists in direct update or metadata management tools, but agents can work around this using iteration and deletion.