claude-design-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_design_systemA | Create a new Claude Design project. Returns { projectId, url }. Does NOT start generation — call |
| generateA | Start generation for an existing project. Returns immediately once generation has STARTED — generation takes ~5 minutes, poll |
| get_statusB | Poll generation status. Returns { status: 'generating'|'ready'|'error'|'draft', detail?: string }. |
| iterateA | Send a chat message to iterate on the design. Non-blocking: returns once the run has STARTED (~seconds). Poll |
| list_filesB | List files generated for the project (tokens, components, screens, SKILL.md, etc.). |
| read_fileB | Read a single generated file by its path within the project. |
| exportC | Write all generated files into destDir, preserving structure. |
| mint_handoffA | PRIMARY handoff to Claude Code. Mints the official capability URL to the server-built bundle and returns a ready-to-run command (Fetch … / Implement: …). The URL is fetchable without auth and expires shortly. Pass destDir to also download + extract the bundle locally (returns projectDir, ready for |
| export_handoffA | DEPRECATED — prefer |
| publishB | Publish the design system (make it shareable / consumable as a Skill). |
| set_defaultC | Set this design system as the default one used by Claude Design. |
| list_design_systemsB | List all known design system projects. |
| list_projectsA | List ALL projects (both design systems and design projects) with their kind. |
| create_design_projectA | Create a new design PROJECT (screens/app/prototype), optionally attaching design systems. Returns { projectId, url }. Call |
| attach_design_systemC | Bind a design system to a project so it reuses that system's tokens/components. |
| detach_design_systemC | Unbind a design system from a project. |
| list_attached_design_systemsA | List the design systems currently bound to a project (with names). |
| refresh_design_systemA | Pull the latest version of bound design system(s) into the project. |
| list_conversationsA | List a project's conversations (chats): { chatId, title, turns, active }. |
| new_conversationA | Start a fresh conversation in the project (then use send_message). |
| send_messageA | Send a prompt / revision to the project chat. Non-blocking: returns once the run has STARTED. Optionally target a specific conversation by conversationId. Poll |
| search_filesC | Grep the project's files for a pattern. Returns { path, line, context } matches. |
| write_fileA | Create or overwrite a file in the project with the given UTF-8 content. |
| edit_fileC | Replace an exact string in a project file (single occurrence edit). |
| delete_fileC | Delete a file from the project. |
| rename_projectC | Rename a project. |
| delete_projectC | Delete a project permanently. |
| duplicate_projectC | Duplicate a project. Returns the new { projectId, url }. |
| remix_projectC | Remix a project into a new one (optionally including chats). |
| set_favoriteA | Mark/unmark a project as favorite. |
| get_usageB | Get account usage/quota status (5-hour and 7-day windows). |
| create_claude_code_sessionB | Open the project as a Claude Code session. Returns { sessionUrl }. May be gated per account. |
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 32 tools
Most tools have distinct purposes, but 'iterate' and 'send_message' both send chat messages to iterate on design, causing potential confusion. Also, 'export_handoff' is deprecated but remains, creating overlap with 'mint_handoff'. Overall, the set is mostly clear.
All tools follow a consistent verb_noun pattern in snake_case (e.g., attach_design_system, list_projects, rename_project). No mixing of styles or irregular names.
32 tools is excessive for a typical MCP server, even for a complex domain. The set includes deprecated tools and several overlapping functions (e.g., generate/iterate, export_handoff/mint_handoff) that could be consolidated.
The tool set covers the full lifecycle of design project management: creation, generation, iteration, file management, export, and handoff. Minor gaps exist (e.g., no direct tool to update design system properties), but core workflows are well-supported.