DesignPort
1-line summary: This server bridges Figma and Adobe XD to MCP clients, exposing design context and read/write tools for agents to inspect, extract, and modify designs.
Host & capability discovery: List connected design hosts (
design.list_hosts), list recent events (design.list_events), and check host capabilities (design.get_capabilities).Read design context: Get current selection (
design.get_selection_context), a specific screen/artboard (design.get_screen_context), visual PNG renders (design.get_visual_context), and full DesignIR exports (design.export_ir).Combined context for agents:
design.get_design_contextreturns structured DesignIR properties, a visual PNG, and optionally generated target code together.Generated code:
design.generate_codeproduces starter implementations for web, React, Vue, Flutter, SwiftUI, or Jetpack Compose.Write operations: Create screens (
design.create_screen) and components (design.create_component), update the current selection with a normalized patch (design.update_selection).Health check:
design.pingverifies whether a host plugin can receive requests.
Provides tools for reading Figma designs, including selections, screens, and normalized design context, rendering visual previews as PNGs, exporting design IR, generating starter code for web and native frameworks, and creating or updating screens and components in Figma.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DesignPort Generate React starter code for the selected screen in Figma."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DesignPort
Free, local-first Figma MCP for AI coding agents — read, create and edit designs without a Figma API token or paid MCP access.
DesignPort gives Codex, Claude Code and Cursor both a PNG visual reference and structured design context: hierarchy, layout, typography, tokens, components and interactions. One MCP process connects to the Figma Plugin API through a local WebSocket bridge. DesignPort does not generate framework code; the agent implements the design using the target repository's own stack.
Codex / Claude Code / Cursor
│ MCP over stdio
DesignPort
│ WebSocket on localhost:5514
Figma plugin
│ Figma Plugin API
Open design fileStart from this checkout
Requires Node.js 22 or later and Figma desktop to import the development plugin.
npm ci
npm run buildIn Figma, choose Plugins → Development → Import plugin from manifest…, select plugins/figma/manifest.json, and run DesignPort Figma in the document you want the agent to use. Keep the plugin running.
Register the built server with one command from the repository root:
codex mcp add designport -- node "$PWD/dist/src/index.js"Codex MCP setup. For Claude Code:
claude mcp add --transport stdio designport -- node "$PWD/dist/src/index.js"For Cursor, add this to .cursor/mcp.json, replacing the path:
{
"mcpServers": {
"designport": {
"command": "node",
"args": ["/absolute/path/to/designport/dist/src/index.js"]
}
}
}The MCP client starts the server and bridge together. Use one client process on port 5514 at a time. Call figma.status to check the connection. Multiple open Figma documents require an explicit sessionId from that response.
The npm package and Community listing are release pending. Once the npm package is published, the equivalent Codex setup is codex mcp add designport -- npx -y designport@1.0.0. The package includes the Figma plugin files.
Related MCP server: figmad-mcp
Eight public tools
Tool | Purpose |
| Connections, capabilities, bounded recent events and limits. |
| DesignIR, tokens, layout, component properties and overrides, internal audit/graph and matching PNG. |
| Bounded original or rendered asset bytes from a capture. |
| Native frame, text, rectangle, component and local instance trees with Auto Layout. |
| A distinct patch per node: text, typography, geometry, parent, layout, fills, strokes and exposed instance text properties. |
| Explicit captured subtree deletion. |
| Subtree cloning with destination parent, name and position. |
| Bounded instant on-click navigation and named flow starts. |
There are no legacy tool aliases. Version 1.0 removes Adobe XD, provider adapters, design.* tools and delta responses. Audit and graph remain part of context, without separate tools. FigJam connectors, remote component imports, variant authoring and annotation workflows are outside the current scope.
Read, then write
Use
figma.get_contextforselection,screen,pageordocument. PNG is included by default for non-document scopes; useincludeVisual: falsefor properties alone.Inspect
properties.snapshot.complete, coverage and omissions. A paginated or budget-incomplete capture cannot authorize a write.Pass
properties.snapshot.idasexpectedSnapshotIdandproperties.snapshot.identity.sessionIdascaptureSessionId. The separatesessionIdselects the bridge connection.Send explicit node IDs. Update targets and destination parents must be captured; delete and clone require all descendants in scope. Selection changes do not redirect a write.
Read fresh context after each write or mutation failure. Writes are serialized and invalidate the previous snapshot immediately.
Creation is limited to 256 specifications, 32 roots and depth 12. Update and delete accept at most 100 targets; clone accepts 32 roots. Expanded instance creation and subtree operations are limited to 2000 native nodes. PNG/JPEG input is limited to 4 MB per image, 4096 pixels per side and 16 million pixels. Prepared write requests are capped at 8 MB.
Create and clone clean up task-created nodes on failure. Update and prototype operations attempt native rollback. Unexpected deletion failures report exactly which IDs were removed; deletion is not a database transaction. Figma's normal Undo remains available.
See examples, the DesignIR guide and the security boundaries.
Configuration
Variable | Default |
|
|
|
|
|
|
|
|
The plugin's WebSocket URL and pairing value must match the server; edit plugins/figma/ui.html, code.js and the manifest together for a custom port or pairing value. The bundled pairing value is public, not a secret. No Figma REST token is involved. Design data stays between the plugin, local server and your configured coding agent; that agent may send context to its model provider.
The plugin uses Figma's required dynamic-page manifest and async APIs. It explicitly loads all pages before subscribing to document changes so external edits invalidate snapshots. Large files can take longer to initialize.
Verify and package
npm test
npm run typecheck
npm run build
node --check plugins/figma/code.js
npm run test:package
npm run package:plugintest:package creates artifacts/designport-1.0.0.tgz, installs it in a clean temporary directory without development dependencies, checks the real stdio tool surface and shutdown, then removes the temporary install. package:plugin prepares artifacts/figma/; supply -- --id FIGMA_ASSIGNED_NUMERIC_ID when preparing an actual Community submission. Release instructions distinguish local verification from publication.
npm run smoke:figma -- --document-name "Your scratch document" runs the create/image/clone/edit/delete scenario in a named scratch file and saves PNG evidence. npm run fixture:avia -- --port 5514 exercises the three-screen fixture in its explicitly named scratch document. Run npm run visual:compare -- reference.png candidate.png --json for local PNG comparison.
DesignPort is licensed under GPL-3.0-or-later. This implementation uses no copied Grab source.
Available Tools
13 toolsdesign.create_componentCreate a design componentC
Create a component or symbol through the active host adapter.
Inputs: name (required), fill, host, kind, +3 more.
design.create_screenCreate a design screenC
Create an artboard/screen through the active design host adapter.
Inputs: name (required), x, y, host, +3 more.
design.export_irExport DesignIRB
Export the document, current selection, or one screen as DesignIR.
Inputs: host, scope, screenId.
design.generate_codeGenerate application 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.
Inputs: host, scope, target, screenId.
design.get_capabilitiesGet design host capabilitiesB
Return the active plugin capabilities for a design host.
Inputs: host.
design.get_design_contextRead complete design contextA
Return design properties, a visual PNG, and generated target code together so an agent can reason from structure, appearance, and implementation.
Inputs: host, scope, target, screenId, +1 more.
design.get_screen_contextRead screen contextC
Return one screen/artboard and its normalized descendants.
Inputs: host, screenId.
design.get_selection_contextRead selection contextC
Return the current host selection normalized as DesignIR nodes.
Inputs: host.
design.get_visual_contextRead design visual contextB
Render the selected node or screen as PNG image content and return its visual metadata.
Inputs: host, scope, screenId.
design.list_eventsList design host eventsB
Read recent selection, document, and write status events from plugins.
Inputs: host.
design.list_hostsList connected design hostsA
List connected Figma and Adobe XD DesignPort plugins.
Inputs: no named parameters.
design.pingPing a design hostC
Check that the selected plugin can receive bridge requests.
Inputs: host.
design.update_selectionUpdate the design selectionC
Apply a normalized patch to the current host selection.
Inputs: patch (required), host.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
A design agent in your coding agent's loop: briefs each screen, reviews UX and visual quality.
Give your AI agents a design superpower. Generate, edit, and publish publication-grade decks, reports, landing pages, resumes, and marketing visuals directly within your agent workflow. Delivering frontier-level design quality at 3× the speed and 53× lower cost -from conversational prompt to live link or vector PDF in minutes.
UI design from prompts, screenshots, and URLs for AI coding agents and theme tokens.
Serves your design system and coding standards to coding agents, so they stop guessing.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with access to Figma design data through the Figma API. Enables accurate one-shot implementation of designs in any framework by translating Figma files into simplified layout and styling information.1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Figma to create, read, and manage designs using the Figma REST API and a dedicated plugin. It supports advanced features like UI generation from text, webpage reconstruction in Figma, and design token synchronization with codebases.20MIT
- AlicenseBqualityDmaintenanceEnables extraction of design context from Figma files as CSS-like properties and provides tools to render Figma nodes as images. It integrates with AI agents via the Model Context Protocol to facilitate design-to-code workflows by providing layout, style, and typography information.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to extract design systems, analyze components, and maintain design-code consistency from Figma files, providing intelligent component analysis and accessibility compliance.103 npm27MIT