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/naver/design-to-uiWrote 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/naver/design-to-ui/design-to-ui-figma-desktop)<a href="https://agentmods.dev/mcp/naver/design-to-ui/design-to-ui-figma-desktop"><img src="https://agentmods.dev/badge/mcp/naver/design-to-ui/design-to-ui-figma-desktop/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/naver/design-to-ui/design-to-ui-figma-desktop"><img src="https://agentmods.dev/badge/mcp/naver/design-to-ui/design-to-ui-figma-desktop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
figma-desktop 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 12d 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-desktop": {
"type": "http",
"url": "http://127.0.0.1:3845/mcp"
}
}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.
- 12d ago First seen · 6 lines scan A 21540548d101
figma-desktop is an MCP server published in the GitHub repository naver/design-to-ui (5 stars, last pushed 1mo ago), licensed Apache-2.0. 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
phonebook
Storybook-style static gallery generated from Compose @Preview / SwiftUI #Preview screenshots. Runs locally from the @stag-build/phonebook npm package.
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.
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…
swiftindex
MCP server "swiftindex" as configured in DesignPipe/exfig. Launched with ./bin/mise exec -- swiftindex serve.
figma-ui-mcp
Claude Code to Figma — Bidirectional MCP bridge. AI draws UI on Figma canvas, reads designs back. Works with Claude, Cursor, VS Code, Windsurf, Antigravity. No API key needed. Runs locally from the figma-ui-mcp npm package.