What is F-MCP?
F-MCP, published as @atezer/figma-mcp-bridge, is a local bridge between an AI agent and Figma. A Figma plugin talks to localhost, so design data stays on your computer. Version 1.9.15 lists 63 tools and 29 skills for design systems, tokens, prototypes and code handoff.
F-MCP listens only on localhost, in the port range 5454 to 5470, and a Figma plugin named F-MCP ATezer Bridge connects to that same address. Nothing about your designs is sent over the internet, and it can run offline.
The README, written in Turkish, describes two-way work. The agent reads a design to list components or extract tokens, and writes back by creating frames, updating color tokens or exporting icons as SVG.
What you can ask it to do
- Design system audit and compliance checks, using a design system the agent discovers from your Figma environment.
- Token work: manage colors, type and spacing, and compare Figma tokens with the ones in code.
- Quality checks such as contrast, plus export to SVG, PNG or PDF.
- Prototype automation: build links between screens, set transitions and animations such as SLIDE_IN or SMART_ANIMATE.
- Design to code context, including Code Connect mappings.
How it finds your design system
Version 1.9.13 added automatic onboarding. Ask for something against your design system and the agent scans the libraries a file subscribes to, open library files and instance sources, then saves the result locally so it never asks twice.
Who it is for
Best for
- Design system teams who want audits, token sync and change tracking from one local setup, alongside patterns such as design system patterns.
- Teams already mapping components to code, who may also read about Code Connect component mapping.
- Anyone comparing it with the official Figma MCP server or generating libraries through a library generation skill.
Not for
- Browser or cloud agent sessions. The bridge is localhost only, so the agent and Figma must run on the same computer.
- People who want a single copy and paste config. The README installs it by asking an agent to set up the repository.
Use it with UiChemy
F-MCP keeps a Figma design system tidy and consistent. When a screen is ready, UiChemy's Figma to WordPress converts it into an editable WordPress page, with Composer for later edits. Click Get Started on uichemy.com.
Connect F-MCP Bridge: Local Figma Bridge With 63 Tools for Design Systems to your AI client
Tell your AI agent: install this repo https://github.com/atezer/FMCPGet an agent that can run installs
The README uses Claude Code for setup, downloaded from claude.ai/download. It needs Figma and an agent that can create files, run commands and install software on your machine.
Ask for the install
Open Claude Code and type the repository address with a request to install it. The README says it handles Node.js, the build and the settings, and may ask for your computer password. Restart the agent when it reports completion.
Open the Figma plugin
In Figma choose Plugins, then F-MCP ATezer Bridge, and wait for the green Ready state. First time only: Plugins, Development, Import plugin from manifest, then select
f-mcp-plugin/manifest.json.Start with your agent open
Open the AI tool first, then run the plugin. A yellow auto-connect state means no bridge is listening, which happens with cloud sessions. To test, run
node dist/local-plugin-only.jsin the clone folder, then stop it with Ctrl+C.Clean up stuck processes
If the plugin cannot connect, run
bash scripts/cleanup-ports.shto stop old F-MCP processes on ports 5454 to 5470.
Endpoints and ports
localhost:5454 to 5470Plugin and agent must share one machinef-mcp-plugin/manifest.jsonImport from Plugins, Developmentdocs/TOOLS_FULL_LIST.mdIn the repositoryWhat you can do with it
- Plugin only and localThe bridge listens on localhost, so design data stays on your computer.
- Design system discoveryThe agent finds your libraries from the Figma environment and remembers them locally.
- Design to code bridgeCollects component, token and Code Connect context for the selected component.
- Prototype automationBuilds screen links, transitions and animations, including overlays and scroll behavior.
- Contrast and token checksRuns accessibility contrast checks and compares Figma tokens with tokens in code.
- Export in several formatsExports assets as SVG, PNG or PDF.
- Design system change trackerVersion 1.9.15 compares snapshots and version history to report what changed.
- Optional API tokenAdding a Figma token adds comments, version history and REST image export.
Tools it exposes
figma_scan_ds_compliance
Runtime audit of the design against the active design system.
figma_use
Gathers design context for a selection. With intent=design_context it collects component, token and Code Connect data.
figma_get_code_connect
Returns Code Connect mappings. With scanCurrentPage=true it gets every mapping on the page.
Frequently asked questions
What is F-MCP?
F-MCP, packaged as @atezer/figma-mcp-bridge, is a local Figma MCP bridge. A plugin in Figma connects to a bridge on localhost, so an AI agent can read and change designs, audit design systems and manage tokens without data leaving your computer.
How do I install F-MCP?
The README installs it by asking an agent to set up the repository from its GitHub address. Restart the agent afterwards, then open Plugins, F-MCP ATezer Bridge in Figma and wait for the green Ready state.
Which AI tools work with F-MCP?
The README table marks Claude Desktop, Claude Code in a local terminal and Cursor as working. It marks Claude Code on the web or mobile, and the Claude chat website, as not working, because they cannot reach a plugin on your computer.
Does F-MCP send my designs to the cloud?
The README says everything stays on your computer and design data is not sent to the internet. The bridge listens only on localhost, between ports 5454 and 5470, and it can be used without an internet connection.
Do I need a Figma API token?
No. Core features work without one. Adding a personal access token in the plugin's Advanced section adds comments, version history, REST image export and file details. The token stays on your computer.
Why is the plugin stuck on yellow auto-connect?
No bridge is listening on your machine. This happens when the agent session runs in the cloud, or when the AI tool was not opened first. Open the AI tool, then run the plugin again.
What commands does it add?
The README lists add-library, ds-add with a Figma link, ds-sync with a design system name, ds-validate with a design system name and track-ds-changes with a Figma link, all as slash commands. Desktop chat apps do not run slash commands, so you paste the instructions instead.
What are alternatives to F-MCP?
For the official route, see the Figma MCP server. For library creation, see a library generation skill. F-MCP differs in its local plugin bridge and its design system audit tooling.