figma -write

This MCP server provides write access to Figma by leveraging the Figma Plugin API, enabling AI agents to create, modify, and manage designs in an open Figma session. The server exposes a set of 24 tools organized into categories such as Core Design, Layout & Positioning, Design System, Advanced Operations, Developer Tools, and System, giving agents programmatic control over shapes, text, styles, components, vectors, measurements, exports, and more. To use it, start the MCP server with the configured command, ensure you have an active Figma Desktop session with a file open, and connect via an MCP client that can issue tool invocations and file manipulations. The tools allow operations like creating frames, drawing shapes, applying styles, building design systems, performing boolean operations on shapes, exporting assets, and generating developer handoff data, all through the Plugin API rather than REST, which enables true write capabilities and live updates during a session.

Prerequisites:

• Node.js 22.x
• npm
• Figma Desktop with an active session
• Git

Install steps:

1. Install Node.js and npm from https://nodejs.org
2. Clone the repository:

git clone https://github.com/oO/figma-mcp-write-server.git
cd figma-mcp-write-server

3. Install dependencies and build:

npm install
npm run build

4. Configure Claude Desktop (or your MCP runner) with the following example configuration:

{
  "mcpServers": {
    "figma-mcp-write-server": {
      "command": "node",
      "args": ["/path/to/figma-mcp-write-server/dist/index.js"],
      "env": {
        "NODE_ENV": "production"
      }
    }
  }
}

5. Start the server via your CNC/CLI runner or Claude Desktop using the provided configuration. Ensure you have the Figma plugin installed and a current Figma file open during operation.

Tips and notes:

• The server requires an active Figma Desktop session; without an open file, write operations cannot proceed.
• The configuration relies on a built dist/index.js; ensure the build step completes successfully before starting.
• If you encounter plugin permission prompts, grant the necessary plugin permissions in Figma to allow programmatic edits.
• Check environment variables such as NODE_ENV for proper mode (production vs development).
• The tooling hierarchy intentionally maps to Figma capabilities; consult docs/guide.md for a complete reference of each tool and usage patterns.
• Network stability can affect plugin communication; keep a stable desktop environment during long-running designs.