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/KaiUweHella/figma-bridge-mcpWrote 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/kaiuwehella/figma-bridge-mcp/figma-bridge)<a href="https://agentmods.dev/mcp/kaiuwehella/figma-bridge-mcp/figma-bridge"><img src="https://agentmods.dev/badge/mcp/kaiuwehella/figma-bridge-mcp/figma-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/kaiuwehella/figma-bridge-mcp/figma-bridge"><img src="https://agentmods.dev/badge/mcp/kaiuwehella/figma-bridge-mcp/figma-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
figma-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-bridge": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}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 Changed 668e42ced8e6
- 8d ago Changed 803e0c3b4f7a
- 12d ago First seen · 9 lines scan A af7c2e593148
figma-bridge is an MCP server published in the GitHub repository KaiUweHella/figma-bridge-mcp (1 stars, last pushed 4d 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-31.
Other mcp servers, from other repositories
best-cad-mcp
MCP server "best-cad-mcp" as configured in LokmenoWer/best-cad-mcp. Runs ${CLAUDE_PROJECT_DIR:-.}/src/server.py with python. Needs 3 environment variables to run.
composer_kit_mcp
A Model Context Protocol (MCP) server for Composer Kit UI components and Celo Composer project creation. Runs locally from the composer_kit_mcp Python package.
drawio
MCP server "drawio" as configured in os-tack/fcp-drawio. Runs locally from the @os-tack/fcp-drawio npm package.
agent-canvas
Local MCP canvas for Modellix image generation, editing, task recovery, and visual project work. Runs locally from the @modellix/agent-canvas npm package.
tokens-studio-mcp
MCP server "tokens-studio-mcp" as configured in Blyawon/tokensStudioMCP. Runs locally from the tokens-studio-mcp npm package.
figma-compaction-mcp
MCP bridge that prunes Figma design context into compact plain-text context for agents. Runs locally from the figma-compaction-mcp npm package.