What is the Design Lazyyy Figma MCP server?
Design Lazyyy is a Figma MCP server with 46 tools: 16 read and analyze tools that need only a personal access token, 27 write tools for nodes, fills and components that need the Figma Desktop Bridge plugin running, and 3 local console tools for bridge logs and status. It supports driving the same file from two separate AI clients at once.
Design Lazyyy connects an agent to Figma through 46 tools split into three groups: reading and analyzing a file, writing to nodes and components, and local console access to the write-side bridge plugin.
Reading needs only a personal Figma access token. Writing needs that same token plus the Figma Desktop Bridge plugin running inside the Figma Desktop app, since Figma gives plugins, not outside tools, the ability to edit a file directly.
What you can ask it to do
- Pull file data, version history, variables, styles and component specs, or render an asset, without needing the Desktop Bridge plugin at all.
- Run a design system analysis, an accessibility audit or a token parity check against an existing file.
- With the Desktop Bridge plugin running, create, move, resize or delete nodes, edit fills, strokes and text, and arrange component variants.
- Drive the same Figma file at once from Claude Desktop and Claude Cowork, since the bridge supports more than one connected host.
Setup at a glance
| Design Lazyyy Figma MCP | |
|---|---|
| Read tools | 16, need only a personal access token |
| Write tools | 27, need the Desktop Bridge plugin running |
| Console tools | 3, local bridge log and status tools |
| figma_execute limit | ES5-compatible code only, no arrow functions, template literals or async/await |
Who it is for
Best for
- Teams who want an agent to audit a Figma file for accessibility or design system drift without needing write access at all.
- Workflows that also want an agent editing nodes, fills and component variants directly inside a live Figma Desktop file.
- Setups already running Claude Desktop and Claude Cowork against the same project that want both connected at once.
Not for
- If the write path should need no personal access token at all, Figma MCP Console lets an agent read and write Figma through its own plugin with no token required.
- When all you need is a local bridge for one open Figma file from a terminal, Relay MCP can search, audit, restyle and rename those components instead.
- If avoiding the Figma REST API's rate limit matters more than a token-based read path, Figma MCP Bridge can read and edit Figma through its own plugin with no rate limit to manage.
- When the goal is compiling design-system intent into Figma rather than general read and write tools, Bridge DS compiles that design-system output through its own MCP server.
Use it with UiChemy
Design Lazyyy reads and edits the Figma source itself. UiChemy Figma to WordPress and Composer then turn that same source into an editable WordPress page. Click Get Started on uichemy.com.
Connect Design Lazyyy Figma MCP: 46 Tools for Read and Write Access to your AI client
git clone https://github.com/plugin87/figma-remote-server.gitClone and build
Run
git clone https://github.com/plugin87/figma-remote-server.git, thennpm installandnpm run buildinside the repository.Generate a Figma token
In Figma, go to Settings, Security, Personal Access Tokens, and create one with Read and Write scopes.
Set the token
Copy .env.example to .env and add your token, then add the config block above to Claude Desktop's config file with the real path and token.
Install the Desktop Bridge plugin
For any create or edit tool to work, install the Figma Desktop Bridge plugin from inside the Figma Desktop app, not the browser version.
Restart Claude Desktop
Restart the client after saving the config so it picks up the new server before you call a tool.
Client configuration
{
"mcpServers": {
"figma-remote": {
"command": "node",
"args": ["/absolute/path/to/figma-remote-server/dist/index.js"],
"env": { "FIGMA_TOKEN": "your-figma-token" }
}
}
}Endpoints and ports
Read and WritePersonal access token scope needed for read tools, and for write tools alongside the bridge plugin.9223 to 9232Port range the Desktop Bridge plugin scans for an automatic, self-healing connection.What you can do with it
- 46 tools in three groupsRead and analyze, write, and local console tools each cover a distinct part of working with a Figma file.
- Multi-host operationThe same Figma file can be driven at once from two separate connected AI clients, with automatic connection healing across a scanned port range.
- Design system and accessibility checksDedicated tools run a design system analysis, an accessibility audit and a token parity check against an existing file.
- Bridge-gated write accessWrite tools only work with the Desktop Bridge plugin running inside Figma Desktop, keeping edit access tied to Figma's own plugin permissions.
- Component documentation generationA read tool generates documentation for a component directly from its real specs rather than a manually written summary.
- ES5-safe script executionfigma_execute runs custom code against the file, limited to ES5-compatible syntax, so arrow functions and async and await are not supported.
Tools it exposes
Read and analyze (16 tools)
File data, metadata, version history, variables, styles, component specs, asset rendering, comments, design system analysis, accessibility audits, token parity checks and documentation generation.
Write operations (27 tools)
Variable creation and management, mode configuration, node resize, move, clone and delete, fill, stroke and text editing, component property management and variant arrangement.
Console tools (3 tools)
Plugin log retrieval, log clearing and bridge status monitoring, local mode only.
Frequently asked questions
What is the Design Lazyyy Figma MCP server?
It is an MCP server with 46 tools for Figma: 16 read and analyze tools that need only a personal access token, 27 write tools that also need the Desktop Bridge plugin, and 3 local console tools for bridge status.
How do I install the Design Lazyyy Figma MCP server?
Clone the repository, run npm install and npm run build, set a Figma personal access token in .env, then add the server to Claude Desktop's config with the correct node path and restart the client.
Do I need the Figma Desktop app for every tool?
No, only for the 27 write tools. The 16 read and analyze tools work against the Figma REST API with just a personal access token, so auditing or extracting tokens does not need the desktop app at all.
What is the Desktop Bridge plugin for?
It is the piece that lets any create, edit or delete tool actually change a Figma file, since Figma only grants that kind of access to a plugin running inside its own desktop app, not to an outside server.
Can I run figma_execute with modern JavaScript?
No. The project states that figma_execute only supports ES5-compatible code, so arrow functions, template literals and async or await are not available inside the script you pass it to run.
Can two clients edit the same Figma file through this server at once?
Yes. The project supports multi-host operation, so the same file can be driven simultaneously from two connected AI clients, with automatic reconnection and port scanning if a bridge connection happens to drop.
Does it work with agents other than Claude?
The README documents setup for Claude Desktop and Claude Cowork specifically, and does not list a separate configuration path for other MCP clients, though the server itself speaks standard MCP.


