OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Figma Console MCP

Figma Console MCP is a TypeScript MCP server that connects AI clients to Figma to extract design-system information, create or modify designs, manage variables, and support design debugging and checks.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Figma Console MCP — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when an MCP-compatible AI client needs structured access to Figma data or actions. Choose Remote SSE for read-only exploration, Cloud Mode for web-client writing without Node.js, or NPX/Local Git when the full local tool set and monitoring are needed.

Who it is for

  • Designers who want an AI assistant to inspect or change Figma work.
  • Design-system teams that need structured access to components, variables, styles or tokens.
  • Developers working across Figma and code who want token exchange or design-code parity checks.

Documented uses

  • Extract Figma variables, components and styles for an AI assistant.
  • Create or edit components, frames and layouts in Figma.
  • Manage design tokens and variables.
  • Capture screenshots and inspect design work while debugging.
  • Check design-code parity, accessibility or design-system health.
Before you choose

Requirements & limits

The project documents Remote SSE as read-only, Cloud Mode as write-enabled after pairing, and NPX/Local Git as full-tool options. NPX requires Node.js 18+, Figma Desktop and an MCP client. The repository lists an MIT license.

  • Remote SSE cannot create or modify designs; writing requires Cloud Mode, NPX or Local Git.
  • Cloud Mode does not require Node.js but provides fewer tools than NPX/Local Git and omits real-time monitoring and codebase-to-design-system extraction.
  • NPX setup requires a Figma personal access token and the listed permissions.
  • The repository identifies TypeScript as its primary language and MIT as its license.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Configure the NPX server for an MCP client

Set up the documented NPX connection so an MCP client can access Figma design tools.

Before you start

  • Node.js 18+
  • Figma Desktop
  • An MCP client such as Claude Code, Cursor, Windsurf or Claude Desktop
  • A Figma personal access token with the listed file-content, file-version and variable read scopes, and comments read/write scope

Steps

  1. Create a Figma personal access token and select the scopes listed in the project README.

  2. Add the server configuration to the MCP client's configuration, using the command the command below and providing the token as FIGMA_ACCESS_TOKEN.

    Documented command
    npx -y figma-console-mcp@latest

  3. For the documented configuration, set ENABLE_MCP_APPS to true and save the client configuration.

Expected outcome

The MCP client is configured to connect to Figma Console MCP using the NPX server command.

Guide limitations

  • The guide describes setup, not a verified connection or successful task run.
  • This NPX route requires Figma Desktop; the README describes Cloud Mode as an alternative for web AI clients without Node.js.
  • The tool set and capabilities differ by connection mode.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
9 October 2026
Original website title
southleft/figma-console-mcp · Official homepage title · retained in its source language
How we review sourcesSuggest a correction