What is Figma MCP?
Figma MCP (repository name figma-mcp) is a Model Context Protocol server that connects AI coding agents to Figma. Its README calls it a fidelity-first server for design context extraction and verification, and the GitHub description sums it up as design to code with a fidelity DSL. An agent can pull the design context of a Figma selection, inspect large selections safely, fetch variable definitions and screenshots, resolve Code Connect mappings, and then check whether the built interface matches the design at the semantic and the visual level.
The project is written in OCaml and maintained by Jeongsik Yun. The repository was created in January 2026. Version 0.10.1, released in March 2026, reset the public surface to eight fidelity-focused tools, removed the in-process agent queue and the legacy gRPC transport, and rewrote the startup scripts around HTTP and stdio workflows. The opam package metadata lists version 0.11.0 and declares the MIT licence, although the GitHub API reports no licence file for the repository.
You build and run it yourself. The quickstart installs dependencies with opam, builds with dune, reads a Figma token from the FIGMA_TOKEN variable and starts the server over stdio or over HTTP on a local port such as 8940. MCP clients connect to the /mcp endpoint with an x-api-key header, and HTTP mode requires an API key unless the --allow-no-auth flag is set. Design data comes from the Figma REST API, with an optional bridge to a Figma desktop plugin.
Key capabilities
- Design context Figma_get_design_context and figma_get_metadata return the context of a Figma selection for an agent to build from.
- Variables and screenshots Figma_get_variable_defs fetches variable definitions and figma_get_screenshot fetches screenshots of the design.
- Code Connect lookup Figma_get_code_connect_map resolves Code Connect mappings from local mapping files.
- Parity checks Figma_verify_semantic and figma_verify_visual verify semantic and visual parity between the design and the implementation.
- A fixed tool set The server exposes exactly eight tools, figma_whoami included, and no agent queue, planning or category router tools.
- Two transports Start scripts for stdio and HTTP, plus an example MCP client config pointing at http://127.0.0.1:8940/mcp.
Where Figma MCP fits
- Figma REST extraction Design context is read through the Figma REST API. The FIGMA_TOKEN set on the server takes precedence over tokens sent in requests.
- Desktop plugin bridge An optional backend exposes /plugin/connect, /plugin/poll, /plugin/result, /plugin/event and /plugin/status for a Figma desktop plugin.
- Semantic verification The changelog describes a semantic-first verifier that compares the design IR with DOM metrics.
- Visual verification Visual parity checks, with an eval harness that the changelog records as using CIEDE2000 and SSIM.
- HTTP authentication HTTP mode requires FIGMA_MCP_API_KEY or MCP_API_KEY unless auth is switched off with --allow-no-auth.
- Composable design Orchestration stays outside the server and can consume the MCP tools or the underlying OCaml libraries.
Reviews of Figma MCP
Be the first to share your experience with Figma MCP.
Write a review
Loading review form…
Alternatives to Figma MCP
easi.runSelf-hosted Chrome for AI agents via MCP/REST, with live viewing and human takeover. Free AGPL-3.0-only software. Bring your Linux/Docker server and agent/model; their costs are separate.