MCP server

Design Lazyyy Figma MCP: 46 Tools for Read and Write Access

Design Lazyyy's Figma MCP server gives an agent 46 tools for design system analysis, token extraction and accessibility audits, plus write access through a Desktop Bridge plugin.

Run
git clone https://github.com/plugin87/figma-remote-server.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

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 tools16, need only a personal access token
Write tools27, need the Desktop Bridge plugin running
Console tools3, local bridge log and status tools
figma_execute limitES5-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.