Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/atezer/FMCPInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/atezer/fmcp/claude-desktop-figma-mcp-bridge)<a href="https://agentmods.dev/mcp/atezer/fmcp/claude-desktop-figma-mcp-bridge"><img src="https://agentmods.dev/badge/mcp/atezer/fmcp/claude-desktop-figma-mcp-bridge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/atezer/fmcp/claude-desktop-figma-mcp-bridge"><img src="https://agentmods.dev/badge/mcp/atezer/fmcp/claude-desktop-figma-mcp-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
figma-mcp-bridge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"figma-mcp-bridge": {
"command": "node",
"args": [
"/REPLACE/WITH/ABSOLUTE/PATH/TO/FCM/dist/local-plugin-only.js"
],
"env": {
"FIGMA_PLUGIN_BRIDGE_PORT": "5454"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 11 lines scan A f27a5c8b35f8
figma-mcp-bridge is an MCP server published in the GitHub repository atezer/FMCP (10 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-09.
Other mcp servers, from other repositories
mimic-ai
Builds Figma from your design system: real components and tokens, enforced, learning every build. Runs locally from the @miapre/mimic-ai npm package.
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot. Runs locally from the figma-developer-mcp npm package. Needs 1 environment variable to run.
refero
MCP server "refero", hosted remotely at api.refero.design, as configured in referodesign/referoskill.
web-stylebook-mcp
Design intelligence for coding agents — choose a direction, apply interface-design and UX principles, cover real UI states, and compose design tokens. Runs locally from the web-stylebook-mcp npm package.
standby-design-mcp
Generate design systems: OKLCH color palettes, fluid type scales, spacing, shape and icon tokens. Runs locally from the standby-design-mcp npm package.
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in naver/design-to-ui.