FigmaMCP 2.0.0

FigmaMCP

FigmaMCP is a local .NET tool that lets MCP clients read and edit the active Figma Design document through the FigmaMCP Bridge plugin.

The MCP server communicates with its client over STDIO and accepts plugin connections through a loopback-only WebSocket. Document operations stay on the local machine.

Requirements

• Figma Desktop.
• .NET 10 SDK.
• The FigmaMCP Bridge plugin from the matching GitHub Release.

Install

dotnet tool install --global FigmaMCP

Extract figma-mcp-plugin.<version>.zip from the matching release and import its manifest.json in Figma Desktop as a development plugin.

Configure an MCP client

Configure the client to start the installed tool:

{
  "mcpServers": {
    "figma": {
      "command": "figma-mcp-server"
    }
  }
}

Open the Bridge plugin in the Figma document you want to use. The plugin connects to 127.0.0.1:3846 by default. If the server is started with --port <1-65535>, enter that port in the plugin.

Call get_server_info without arguments to find this instance's actual bridge.port, even with no plugin connected. Enter that port in Figma Bridge. Call list_figma_connections, then pass the returned connection_id to document-specific tools.

Update or uninstall

dotnet tool update --global FigmaMCP
dotnet tool uninstall --global FigmaMCP

Links

• Documentation
• GitHub repository
• Releases
• Issues

FigmaMCP is not affiliated with Figma. The project is distributed under the MIT License.

Shared backend lifecycle

Clients using the same OS user, version and Bridge port share one backend. Ports are fixed; a bind conflict is an error. The backend exits after 60 seconds without clients, plugins or operations. Set --idle-timeout-seconds or FIGMA_MCP_IDLE_TIMEOUT_SECONDS (1–86400); CLI wins, and the first launcher selects the effective value. Backend failure preserves MCP sessions, but interrupted operations are never automatically replayed. Before updating, close clients and plugins and wait for idle shutdown.