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/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/figma-desktop)<a href="https://agentmods.dev/mcp/pmdevsolutions/aurelius/figma-desktop"><img src="https://agentmods.dev/badge/mcp/pmdevsolutions/aurelius/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/pmdevsolutions/aurelius/figma-desktop"><img src="https://agentmods.dev/badge/mcp/pmdevsolutions/aurelius/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 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-desktop": {
"type": "http",
"url": "http://127.0.0.1:3845/mcp",
"description": "Figma desktop app MCP server (local) - requires Figma desktop with Dev Mode enabled"
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 7 lines scan A 5e627e3e51ad
figma-desktop is an MCP server published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed 3d 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-09-04.
Other mcp servers, from other repositories
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in naver/design-to-ui.
figma-query
MCP server "figma-query" as configured in standardbeagle/figma-query. Launched with ./figma-query. Needs 2 environment variables to run.
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.
figwright
MCP server "figwright" as configured in awdr74100/figwright. Runs packages/mcp/dist/index.mjs with node.
refero
MCP server "refero", hosted remotely at api.refero.design, as configured in referodesign/referoskill.
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.