"An official Figma MCP server" matching MCP servers:

Allow your AI coding agents to access Figma files & prototypes directly. You can DM me for any issues / improvements: https://x.com/jasonzhou1993 1. Access all figma pages 2. Access all figma components 3. Access figma prototype flows

Enables a live two-way bridge between a running web app and Figma, letting users push app screens into Figma as auto-layout frames and sync edits in both directions—Figma changes update the source code, and code changes update the Figma frames.

Enhanced Figma MCP Server that exposes prototype flow data — screen lists, prototype connections, and full flow maps — via the Figma REST API. Designed as a replacement for the official Figma MCP server, adding prototype interaction layer so Claude Code can understand entire user flows from a single Figma URL.

Enables Cursor (MCP client) to interact with an active Figma document through a local WebSocket bridge and Figma plugin, providing tools to read and modify canvas elements like text and frames.

A bridge between Figma designs and React implementations that enables pixel-perfect conversion of Figma designs into React applications by processing Figma file data into React-friendly format.

An MCP server that integrates AI agents with Figma, enabling reading and programmatic modification of designs.

Bridges a local Figma development plugin to a local MCP server, letting the client read and write real canvas layers through the Figma Plugin API without consuming official MCP or Dev Mode quota. Supports layer and auto-layout editing, component and variable inspection, design-to-code context retrieval, and PNG/JPG/SVG/PDF export.

An MCP server that gives AI coding tools access to Figma design data for accurate one-shot implementation of designs.

Enables integrating Figma with AI assistants like Claude Desktop and Gemini CLI for accessing and managing Figma design files.

An MCP server that provides write access to Figma through the Plugin API, enabling AI agents to create, modify, and manage Figma designs programmatically.

Model Context Protocol integration for the Figma API, enabling AI applications to access Figma files, components, and design tokens.

Enables AI assistants to control Figma in real-time through Model Context Protocol, allowing design creation, editing, and reading operations directly from VS Code.

An MCP server that bridges Claude to Figma, enabling read access via REST and full create/edit capabilities through the Figma Plugin API over a local WebSocket.

A local-only MCP bridge that connects an MCP client to an open Figma file via a Figma plugin, enabling direct document editing, inspection, export, and audit without using the Figma REST API.

An MCP server that enables AI tools to read and write Figma designs via a plugin bridge, bypassing the Figma REST API and rate limits.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

A Model Context Protocol (MCP) server that enables Claude to create and manipulate designs in Figma through either a Figma plugin or directly via the Figma API.

Read-only MCP server that wraps the Figma REST API, providing tools like get file metadata, list frames, and export node image URLs for AI SDLC agents.

Enables AI agents to read and draw on Figma canvas safely, with built-in safeguards for layout, overlays, and verification.

Bidirectional MCP bridge enabling AI assistants to draw UI on Figma canvas and read designs back as structured data or code tokens via localhost, requiring Figma Desktop.

Enables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.

The Figma desktop app as an MCP server. Gives AI agents the full Figma Plugin API on your open file: read, write, tokens, components, exports, undo. Runs locally with no cloud API, no token and no quota.

Enables automated export, compression, and cloud upload of Figma design assets by simply providing Figma links. Supports batch processing of nodes and children, returning structured data with publicly accessible image URLs.

figmcp gives your coding agent the Figma file you have open in Figma Desktop. A development plugin streams the file to a server on your machine over localhost, so reads never touch the Figma REST API: no access token, no quota and no rate limits, on any Figma plan. * Design to code: Flutter widgets for Flutter projects, React + Tailwind for everything else, with assets and a scree

Converts a Figma file into a React project using Ant Design, AG Grid, ApexCharts, and Tailwind CSS, with optional export of mobile screens as a React Native (Expo) app.

Enables interaction with Figma files through intelligent API access, providing navigation, asset extraction, and design token retrieval with 95% token-optimized compact tree output format.

Enables AI agents to read and inspect local Figma .fig files entirely offline, exposing document structure, geometry, styles, text, components, variables, and embedded images via MCP tools.

Enables listing top-level frames in a Figma file and fetching a selected frame's rendered PNG, node JSON, and image-fill map into a local output directory.

Pull a Figma frame once, then let Claude Code, Codex or any MCP agent read it offline with no rate limits. Six read-only tools serve the normalized node tree, design tokens and locally built SVG icons from a vault you can commit, so teammates need no Figma token.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.