Devign MCP
Allows AI models to create, read, and edit Figma designs in real time, including frames, components, styles, auto-layout, exports, and design system management.
Click on "Install 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., "@Devign MCPCreate a simple button component with text 'Submit'"
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.
Devign MCP - AI-Powered Figma Design Server
A Model Context Protocol (MCP) server that lets any AI model create, read, and edit Figma designs in real time. Not limited to Claude - works with OpenAI, Gemini, local models, Cursor, VS Code, or any MCP-compatible client.
How It Works
┌──────────────┐ stdio or HTTP ┌──────────────┐ WebSocket ┌──────────────┐
│ AI Model │ ◄──────────────────► │ MCP Server │ ◄──────────────► │ Figma Plugin │
│ (any model) │ MCP protocol │ (Node.js) │ localhost:3055 │ (in Figma) │
└──────────────┘ └──────────────┘ └──────────────┘The MCP server exposes 40 design tools to the AI. The Figma plugin runs inside your open Figma file and executes commands on the canvas via the Plugin API. Communication flows over a local WebSocket — no cloud services, no API keys, everything runs on your machine.
Related MCP server: Figma AI Bridge
Quick Start
Prerequisites
Node.js v18+
Figma Desktop app
An MCP-compatible AI client (Claude Code, Cursor, VS Code Copilot, etc.)
1. Install and Build
git clone <this-repo>
cd devign-figma-mcp
npm install
npm run build2. Load the Figma Plugin
Open the Figma desktop app
Open any file you want to design in
Go to Menu > Plugins > Development > Import plugin from manifest...
Navigate to
packages/figma-plugin/manifest.jsonand select itRun the plugin: Menu > Plugins > Development > Devign MCP Bridge
You'll see the plugin panel with a connection status dot. It will show red/Disconnected until you start the MCP server.
3. Start the MCP Server
npm startThe plugin dot should turn green/Connected. You're ready to go.
4. Connect Your AI
Claude Code / Claude Desktop
Add to your MCP config (~/.claude.json or Claude Desktop settings):
{
"mcpServers": {
"devign": {
"command": "node",
"args": ["/absolute/path/to/devign-figma-mcp/packages/mcp-server/dist/index.js"]
}
}
}Cursor / VS Code
Add to .cursor/mcp.json or VS Code MCP settings:
{
"servers": {
"devign": {
"command": "node",
"args": ["/absolute/path/to/devign-figma-mcp/packages/mcp-server/dist/index.js"]
}
}
}Any HTTP-capable Client (OpenAI, Gemini, custom apps)
Start the server in HTTP mode:
DEVIGN_TRANSPORT=http npm startThen point your client to:
MCP endpoint:
POST http://127.0.0.1:3100/mcpHealth check:
GET http://127.0.0.1:3100/health
This uses the Streamable HTTP transport from the MCP spec, compatible with any client that supports it.
What You Can Do
Ask your AI things like:
"Create a mobile login screen with email/password fields and a submit button"
"Read the current page and describe the layout"
"Set up a design system with color tokens, text styles, and elevation shadows"
"Import this SVG icon and place it in the header"
"Create a component with Light and Dark variants"
"Apply auto-layout to the card frame with 16px padding and 12px gap"
"Export the hero section as a 2x PNG"
Full Tool List (40 tools)
Category | Tools |
Creation |
|
Components |
|
Vectors |
|
Styling |
|
Layout |
|
Reading |
|
Mutation |
|
Organization |
|
Export |
|
Variables |
|
Design System |
|
System |
|
MCP Resources
AI clients that support MCP resources can read these directly:
Resource | URI | Description |
Current Page |
| Live node tree of the open page |
Selection |
| Currently selected nodes |
Styles |
| All local paint, text, effect, grid styles |
Variables |
| Variable collections and design tokens |
Components |
| Components on the current page |
MCP Prompts
Guided workflows the AI can use:
Prompt | Description |
| Build a full page/screen from a description |
| Set up variables, styles, and tokens from scratch |
| Check contrast, text sizes, and touch targets |
Configuration
Environment Variable | Default | Description |
|
| Transport mode: |
|
| WebSocket port for plugin connection |
|
| Command timeout in ms |
|
| HTTP server port (when |
Plugin UI
When the plugin is running in Figma, you'll see:
Green dot = Connected to MCP server, ready for AI commands
Red dot = Disconnected, waiting for MCP server
Command counter = How many commands have been processed
Activity log = Real-time log of commands flowing between AI and Figma
The plugin auto-reconnects if the server restarts. Keep it open while working.
Architecture
devign-figma-mcp/
├── shared/ # Shared types and protocol definitions
│ └── src/
│ ├── commands.ts # All command type constants
│ ├── protocol.ts # Request/response interfaces
│ └── index.ts
├── packages/
│ ├── mcp-server/ # Node.js MCP server
│ │ └── src/
│ │ ├── index.ts # Entry point, transport setup
│ │ ├── server.ts # Tool/resource/prompt registration
│ │ ├── ws-bridge.ts # WebSocket bridge to plugin
│ │ ├── tools/ # 11 tool modules (40 tools total)
│ │ └── utils/ # Zod schemas, error helpers
│ └── figma-plugin/ # Figma plugin (runs in Figma)
│ ├── src/
│ │ ├── main.ts # Command dispatcher
│ │ ├── ui.ts # WebSocket client + UI
│ │ └── handlers/ # 11 handler modules
│ ├── manifest.json # Figma plugin manifest
│ └── build.mjs # esbuild config
└── package.json # Workspace rootHow commands flow:
AI sends a tool call (e.g.
create_frame) to the MCP serverServer validates params with Zod, sends command over WebSocket to the plugin
Plugin's UI thread receives the message and forwards it to the main thread
Main thread dispatches to the appropriate handler, which calls the Figma Plugin API
Result flows back: handler → main thread → UI thread → WebSocket → MCP server → AI
Development
# Watch mode for both server and plugin
npm run dev:server # in one terminal
npm run dev:plugin # in another terminal
# Build everything
npm run build
# Build individually
npm run build:server
npm run build:pluginAfter changing plugin code, Figma will hot-reload if you ran the plugin via Development > Import plugin from manifest. For server changes, restart the server.
Troubleshooting
Plugin shows "Disconnected"
Make sure the MCP server is running (
npm start)Check that port 3055 is not in use by another process
Try restarting both the server and the plugin
AI says "Figma plugin not connected"
Open Figma and run the Devign MCP Bridge plugin
Wait for the green dot to appear before sending commands
Commands time out
Increase the timeout:
DEVIGN_WS_TIMEOUT=30000 npm startComplex operations (SVG import, large exports) may need more time
"Unknown command" errors
Rebuild both packages:
npm run buildRestart the plugin in Figma
HTTP transport not working
Make sure you set
DEVIGN_TRANSPORT=httpbefore startingCheck
http://127.0.0.1:3100/healthto verify the server is up
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Appeared in Searches
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SodiqOgundairo/devign-figma-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server