Figma MCP Server

Connect Figma to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Figma API server implementation based on Model Context Protocol (MCP), supporting Figma plugin and widget integration. The figma mcp server is what makes that connection.

What the server does

• Interact with Figma API through MCP
• WebSocket server for Figma plugin communication
• Support for Figma widget development
• Environment variable configuration via command line arguments
• Rich set of Figma operation tools

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: FIGMA_PERSONAL_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by sichang824; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.