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/jozrftamson/figma-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/jozrftamson/figma-mcp/figma-mcp)<a href="https://agentmods.dev/mcp/jozrftamson/figma-mcp/figma-mcp"><img src="https://agentmods.dev/badge/mcp/jozrftamson/figma-mcp/figma-mcp/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/jozrftamson/figma-mcp/figma-mcp"><img src="https://agentmods.dev/badge/mcp/jozrftamson/figma-mcp/figma-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
figma-mcp 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 10d 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.
This is a copy
100% identical to figma-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "figma-mcp": { "command": "uvx", "args": [ "figma-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.
- 10d ago First seen · 8 lines scan A 1d0a09eec5fd
figma-mcp is an MCP server published in the GitHub repository jozrftamson/figma-mcp (0 stars, last pushed 1mo 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. It is 100% identical to figma-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
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
MCP server "figma", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-figma.
figma-comments-mcp
Figma Comments MCP: an MCP server that fetches and filters Figma file comments for triage in Claude Code. Runs locally from the figma-comments-mcp npm package.
mcp-figma
Figma MCP server for accessing Figma API. Runs locally from the mcp-figma npm package.
cursor-talk-to-figma-mcp
Cursor Talk to Figma MCP. Runs locally from the cursor-talk-to-figma-mcp 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.