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/david-buck/figma-local-bridgeWrote 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/david-buck/figma-local-bridge/figma_local)<a href="https://agentmods.dev/mcp/david-buck/figma-local-bridge/figma_local"><img src="https://agentmods.dev/badge/mcp/david-buck/figma-local-bridge/figma_local/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/david-buck/figma-local-bridge/figma_local"><img src="https://agentmods.dev/badge/mcp/david-buck/figma-local-bridge/figma_local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
figma_local 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 8d 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_local": {
"command": "node",
"args": [
"./dist/server.mjs"
]
}
}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.
- 8d ago First seen · 8 lines scan A eca45eb1729a
figma_local is an MCP server published in the GitHub repository david-buck/figma-local-bridge (0 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-08-31.
Other mcp servers, from other repositories
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.
figma-mcp-rust
Figma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. Runs locally from the @alvinindra/figma-mcp-rust npm package.
figma-console
The most comprehensive MCP server for Figma — design tokens, variables, components, write tools, version history diff, accessibility audits, FigJam, Slides, and more. Local (WebSocket Desktop Bridge plugin) and Cloudflare Workers (paired + remote) modes. Runs locally from the figma-console-mcp npm package. Needs 1…
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in PMDevSolutions/Aurelius.
figma
MCP server "figma", hosted remotely at mcp.figma.com, as configured in PMDevSolutions/Aurelius.