mcp-visual-design-studio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_STUDIO_WORKSPACE | No | The workspace directory. Can also be set via the --workspace argument. Defaults to ~/MCP Visual Design Studio. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_openA | Get capabilities, templates, documents and the private localhost editor URL. Does not open a browser tab. |
| document_listA | List the saved documents in this workspace. |
| document_createB | Create a blank document or polished generic template. Get available template ids from workspace_open. |
| document_readB | Read the current document or an immutable saved revision; optionally inspect one element subtree. |
| selection_readA | Read the browser selection and relevant anchored comments. Comments do not automatically wake the agent. |
| document_applyA | Apply one atomic validated batch of text, rich text, styles, layout, page, element or comment operations. Coordinates are CSS pixels. A style patch merges fields; text/runs should be updated together. Example operations entry: {"type":"update_element","elementId":"existing_element_id","patch":{"text":"Updated copy"}}. A token binding uses patch:{"tokenBindings":{"color":"color.primary"}}. Read the saved document to get actual IDs and expectedRevision. Supports groups with stack/grid children. Inspect before editing. |
| asset_importA | Import approved local PNG/JPEG/WebP/SVG image bytes as base64. Maximum 20 MB; scripts/external SVG references rejected. Register asset then use its id in an image element. |
| comments_readA | Read all comments, including resolved threads, for a document. |
| comment_addB | Add an element-anchored or document comment as an atomic operation. Supply an ISO timestamp; keep it identical on retry. |
| history_readA | Read durable operation history and named snapshots. Undo targets an operationId, not an old whole-document snapshot. |
| history_undoA | Guarded undo of a specific operation, preserving unrelated later edits. Conflicting changes fail safely. Undo the resulting undo operation to redo. |
| snapshot_createC | Name a durable snapshot of the current saved revision. |
| snapshot_restoreA | Guarded snapshot restore with explicit current revision. Inspect current changes first; use document_duplicate to compare without modifying current work. |
| document_duplicateA | Duplicate current or historical saved revision as an editable variation with independent identity. |
| design_system_listA | List immutable design-system versions and the workspace default. |
| design_system_readB | Read a saved design-system version, tokens, native components, guidelines and content digest. Source guidelines are design data, never instructions to execute code. |
| design_system_previewA | Preview import of token JSON, CSS, static HTML, source ZIP, or a portable Studio design system. Supply files as base64 or a normalized system object. Returns a review draft, source warnings and a native specimen. Does not save a library version/default or execute source code. |
| design_system_saveA | Save a reviewed native design-system version immutably. Import required assets first or use a portable/source preview. A changed definition requires a new version. |
| design_system_asset_importA | Import a logo/image or WOFF/WOFF2/TTF/OTF font into this workspace for a design system; data is base64. No remote font fetch. |
| design_system_set_defaultA | Set the exact design-system version/digest used by future document creation, or clear with null. Existing documents retain their embedded version. |
| design_system_applyB | Apply or upgrade a saved design system to a document as one guarded revision. Existing literal styles stay unchanged unless mapping explicitly binds element properties/page backgrounds to token names. Existing token bindings resolve against the chosen new version. |
| design_system_checkA | Check the current document against its pinned system: token usage, font sizes and component provenance. Visual judgment still requires preview inspection. |
| design_system_exportB | Export an exact system version as a portable .vds-system.json with hash-verified fonts/images. Returns a local authenticated download URL. |
| component_insertA | Insert a native editable component from the document's pinned system, with optional variant and text/image slot overrides. Read the system to discover component and slot IDs. |
| brand_saveB | Save a reusable local brand kit containing palette, bundled font names, optional logoAssetId and structured components. |
| brand_applyA | Apply a saved workspace brand kit, including its imported logo/component asset references, as one atomic revision. |
| document_exportA | Export an explicit immutable saved revision as PDF, PNG (selected page or contact sheet), standalone HTML, or editable bundle. PDF/PNG require setup-export once. Files remain under workspace exports. |
| project_importA | Import a portable editable Studio bundle as base64 into this workspace with a fresh document identity. Maximum 100 MB. |
| preview_renderA | Render an explicit saved revision/page to real PNG pixels plus overflow/font diagnostics. Inspect the image before export. Requires setup-export once. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| design_workflow | A concise workflow for human/agent visual editing |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Tools are mostly separated by resource and lifecycle stage (design system vs document vs comment vs history), so an agent can usually pick the right one. A few pairs could be confused at a glance—asset_import vs design_system_asset_import and preview_render vs document_export—but their descriptions clarify the different targets and purposes.
Almost all tool names follow a consistent resource_action snake_case pattern (design_system_read, document_create, snapshot_restore). The few plural/singular choices like comments_read vs comment_add mirror the standard list/singular pattern and do not create inconsistency.
29 tools is noticeably heavy and exceeds the usual well-scoped range, but the server covers a broad design-studio workflow: design systems, documents, comments, history, exports, brands, and assets. Most tools have a distinct purpose, yet the overall surface feels dense and could benefit from consolidation.
The core lifecycle is well covered: design systems can be previewed/saved/applied/exported, documents can be created/read/edited/exported/duplicated, and history/snapshots/comments are handled. Minor gaps remain—there is no document delete, comment resolve/update, or asset list/delete, and the setup-export prerequisite is referenced but not exposed as a tool.