claude.design-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_DESIGN_DIR | No | Where design_pull writes | the working folder |
| CLAUDE_DESIGN_CHROME | No | Path to Google Chrome | macOS Google Chrome |
| CLAUDE_DESIGN_PROFILE | No | Dedicated Chrome profile directory | ~/.cache/claude-design-mcp/chrome-profile |
| CLAUDE_DESIGN_CDP_PORT | No | Remote-debugging port | 9377 |
| CLAUDE_DESIGN_HEADLESS | No | Set 1 to drive headless Chrome instead of off-screen | |
| CLAUDE_DESIGN_TURN_TIMEOUT_MS | No | Generation-turn timeout (create ~180s, iterate ~120s defaults) |
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 |
|---|---|
| design_loginA | Open Chrome for claude.ai/design login and report the active account. |
| design_listA | List Claude Design projects from the logged-in web account. |
| design_createC | Create a Claude Design project and submit the initial prompt through the composer. |
| design_iterateC | Submit a follow-up prompt to an existing Claude Design project. |
| design_pullC | Pull one Claude Design project by projectId or exact name into a local directory. |
| design_previewC | Render a project's self-contained HTML to a full-page PNG screenshot for visual review. |
| design_getC | Read one file from a Claude Design project. |
| design_statusC | Summarize project data, chat count, and last message role. |
| design_editC | Apply direct string edits to one Claude Design project file. |
| design_deleteC | Delete one Claude Design project. |
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 10 tools
Each tool has a unique action (create, delete, edit, get, iterate, list, login, preview, pull, status) targeting distinct operations on projects or files, with no overlap in purpose.
All tools follow a uniform 'design_<verb>' pattern, using snake_case throughout, making naming predictable and easy to understand.
10 tools is well-scoped for a design-related server, covering essential operations from login to CRUD to preview and status without being excessive or insufficient.
The tool set covers core workflows (login, list, create, read, update, delete, preview, pull), but lacks explicit support for file deletion or project metadata updates, which are minor gaps.