designer-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 |
|---|---|
| designer_openA | Open a URL in the designer's headed Chromium (launches it if not running). Use this before designer_pick. |
| designer_pickA | Activate the picker in the designer browser. Three modes: element — user clicks one element; returns { selector, tag, classes, text, html, rect, source, screenshot_path } area — user drags a marquee; returns { rect, elements: [{selector, source, rect, ...}], screenshot_path } draw — user ink-annotates with a red pen, Enter to finish; returns { strokes, viewport, screenshot_path (strokes only), viewport_screenshot_path (full view with drawings) } Esc cancels in any mode. screenshot_path / viewport_screenshot_path point to PNGs in /tmp; open with the Read tool. |
| designer_screenshotA | Screenshot the current page or a specific element selector. Returns { path, bytes } — a filesystem path to a PNG in /tmp that you can Read with the Read tool. |
| designer_closeA | Close the designer browser and release resources. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: open launches the browser, pick activates the picker with specific modes, screenshot captures images, and close terminates the session. The descriptions clearly differentiate their functions, eliminating any ambiguity in tool selection.
All tool names follow a consistent 'designer_' prefix with descriptive action suffixes (open, pick, screenshot, close), using snake_case uniformly. This predictable pattern makes the tool set easy to navigate and understand at a glance.
With 4 tools, this server is well-scoped for its purpose of browser-based design interactions. Each tool earns its place by covering essential operations: launching, picking elements, capturing screenshots, and cleaning up, without being overly sparse or bloated.
The tool set provides complete lifecycle coverage for the designer domain: it supports opening the browser, interactive element selection, screenshot capture, and proper resource closure. There are no obvious gaps, as all core workflows from initiation to termination are addressed effectively.