DesignPort
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESIGNPORT_PORT | No | The local port for the host-plugin WebSocket bridge. Defaults to 5514. | 5514 |
| DESIGNPORT_REQUEST_TIMEOUT_MS | No | Timeout for host requests in milliseconds. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| design.list_hostsA | List connected Figma and Adobe XD DesignPort plugins. |
| design.list_eventsB | Read recent selection, document, and write status events from plugins. |
| design.get_capabilitiesB | Return the active plugin capabilities for a design host. |
| design.get_selection_contextC | Return the current host selection normalized as DesignIR nodes. |
| design.get_screen_contextC | Return one screen/artboard and its normalized descendants. |
| design.get_visual_contextB | Render the selected node or screen as PNG image content and return its visual metadata. |
| design.export_irB | Export the document, current selection, or one screen as DesignIR. |
| design.generate_codeC | Export DesignIR from a host and generate a semantic starter implementation for web, React, Vue, Flutter core widgets, SwiftUI, or Jetpack Compose. Layout metadata maps to flex, Row/Column, stacks, and fill-sized children where possible. |
| design.get_design_contextA | Return design properties, a visual PNG, and generated target code together so an agent can reason from structure, appearance, and implementation. |
| design.create_screenC | Create an artboard/screen through the active design host adapter. |
| design.create_componentC | Create a component or symbol through the active host adapter. |
| design.update_selectionC | Apply a normalized patch to the current host selection. |
| design.pingC | Check that the selected plugin can receive bridge requests. |
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 13 tools
Several tools overlap: get_selection_context and export_ir both return DesignIR, get_visual_context and get_design_context both include PNG, and get_design_context duplicates generate_code's code output. Descriptions clarify some boundaries, but an agent could easily struggle to choose between the composite get_design_context and the more specific tools.
All tools share a consistent design. prefix and use a clear verb-first snake_case pattern: list, get, export, generate, create, update, ping. The naming is predictable and easy to navigate.
13 tools is a well-scoped set for a design bridge covering host discovery, context retrieval, IR export, code generation, and mutation actions. Each tool serves a distinct workflow step without unnecessary bloat.
The surface covers the core design-to-code journey: reading selection/screen context, getting visuals, exporting IR, generating code, and creating/updating design artifacts. Some operations like listing all screens/components or deleting/updating components are missing, but agents can still complete primary workflows.