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/noemuch/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/noemuch/bridge/figma-console)<a href="https://agentmods.dev/mcp/noemuch/bridge/figma-console"><img src="https://agentmods.dev/badge/mcp/noemuch/bridge/figma-console/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/noemuch/bridge/figma-console"><img src="https://agentmods.dev/badge/mcp/noemuch/bridge/figma-console.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
figma-console 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 1mo 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-console": {
"command": "npx",
"args": [
"-y",
"figma-console-mcp@latest"
],
"env": {
"FIGMA_ACCESS_TOKEN": ""
},
"description": "Figma Console MCP — gives Claude native access to Figma Desktop via Plugin API. Required for design generation."
}
}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.
- 1mo ago First seen · 13 lines scan A 4cc999d4d553
figma-console is an MCP server published in the GitHub repository noemuch/bridge (155 stars, last pushed 4mo ago), 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-30.
Other mcp servers, from other repositories
mcp
Search Keyline Icons by name and get any icon's SVG source or React import. No key, no network. Runs locally from the @keyline-icons/mcp npm package.
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-mcp-bridge
MCP server "figma-mcp-bridge" as configured in atezer/FMCP. Runs /REPLACE/WITH/ABSOLUTE/PATH/TO/FCM/dist/local-plugin-only.js with node. Needs 1 environment variable to run.
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in naver/design-to-ui.
canicode
Analyze Figma designs for dev & AI readiness. 39 rules, scoring, HTML reports. Runs locally from the canicode npm package. Needs 1 environment variable to run.
figma
MCP server "figma", hosted remotely at mcp.figma.com, as configured in let-sunny/canicode.