figlens
🔍 Design details for coding agents to build, compare and follow changes: layout, SVG assets, bundle checks, screenshot comparisons and saved-revision tracking. Reads Figma .fig files offline. CLI, MCP and host plugins.
Install / Use
claude mcp add runkids -- npx -y github:runkids/figlensIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
DesignSupported Platforms
Our assessment of figlens
figlens scores 76/100 on our quality scale, 237th of 269 Design skills we index.
Its MCP Server is 17 KB long, well organised into 16 sections with 12 code examples: a thorough specification that gives an agent plenty to work with.
It has 10 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated today, so figlens is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
figlens compared with similar skills
All 4 of these similar skills score higher than figlens; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| figlens (this skill)by runkids | 76 | 10 | today | MCP Server |
| taste-skillby Leonxlnx | 100 | 111.0k | 1d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 109.5k | 1d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.0k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 47.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install figlens?
- Run
claude mcp add runkids -- npx -y github:runkids/figlens. The install tabs above show the steps for each supported agent. - Which AI agents does figlens work with?
- It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is figlens safe to use?
- It is MIT-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is figlens still maintained?
- The repository was last updated today, so figlens is actively maintained.
Skill content
View source on GitHubfiglens turns saved Figma files into design context your coding agent can act on—not just a screenshot to interpret.
- Build from the source details. Read layout, text, styles, variables, Dev Mode annotations and Ready for dev status; export vector icons as SVG and images as assets.
bundlecollects a frame's data, assets and reference render;verifyreports missing files, font checks and handoff limitations. MCPnodescan save large node JSON to a file withoutinstead of returning it inline. - Compare the running UI.
compare-imagecompares your screenshot with figlens's render and names the layers under differing regions. Review those differences and rendering warnings; it is not a pixel-perfect guarantee. - Follow design changes.
diffcompares saved revisions;changesandwatchreport updates to tracked local scopes;freshnesstells when a saved copy is older than the online file, andpullsaves a new copy through your own browser sign-in. Save a new.figfrom Figma to pick up design edits—this is not live Figma sync. Named accounts route each design to separate browser profiles and API-token environment variables; existing defaults stay unchanged.figlens sources init [DIR]: Scan local.figfiles into.figlens/sources.jsonwithout overwriting it; names come frommeta.jsonor the filename. Fill in the blank URLs before pulling.
Offline at the foundation. In Figma, File > Save local copy. Put design.fig next to your code. Then a Figma link is enough: its node id picks the frame. With no saved copy, copy the layers in Figma (right-click > Copy) and run figlens clipboard screen.fig; a copy has no images or vector outlines (how). One native binary reads it locally, without a running Figma app, login or network calls to Figma; only the opt-in freshness check (with a configured API token; default: FIGMA_TOKEN) and pull (through your browser sign-in) reach Figma.
<a id="start"></a>
Get started
No design file yet? Check your setup with the tiny public example: verify your chosen binary, find one frame and validate its bundle. No model required.
Put design.fig in your project, then choose one setup. Each gives your agent the figlens tools and the same built-in guidance for planning, implementation and image preparation.
| Setup | Use it for | Guidance comes from |
|---|---|---|
| Plugin | Claude Code, Codex, Antigravity, Cursor, Kimi Code | the plugin's skill and the server's workflow tool |
| MCP | Claude Code, Cursor, Codex, Gemini CLI and other MCP clients | the server's workflow tool |
| Pi | Pi 1.3.0+ | the package, which ships the skill |
| OpenCode V2 | OpenCode V2 2.2.0 | the package skill |
| OMP | OMP 18.13.2 | the package skill |
| Herdr | a panel beside your agents in Herdr 0.1.12+: find a screen, hand it to one, track each screen's progress on a board | the receiving agent's own setup |
| CLI | agents that only run shell commands, scripts and CI, or you | figlens workflow <topic>, or the optional skill |
Ordinary vs advanced. Ordinary use needs no setup: figlens search design.fig "query" reads the .fig and creates nothing. An optional local index is created only when you ask for one (figlens index prepare design.fig --scope 0:0), then reused across restarts and hosts. See Ordinary search and the optional local index. Optional and experimental: --mode semantic or hybrid ranks by meaning with a local model you set up yourself; see Optional semantic search.
<a id="setup-plugin"></a>
Plugin
One install adds the figlens skill and MCP server to your agent (Node.js 18+). The server is pinned to the plugin's release (npx -y @runkids/figlens@<version> mcp); update the plugin to move to a new version.
| Host | Install |
|---|---|
| Claude Code | claude plugin marketplace add runkids/figlens, claude plugin install figlens@figlens |
| Codex | codex plugin marketplace add runkids/figlens, codex plugin add figlens@figlens |
| Antigravity | agy plugin install https://github.com/runkids/figlens/tree/main |
| Cursor | git clone --depth 1 https://github.com/runkids/figlens ~/.cursor/plugins/local/figlens, then reload the window |
| Kimi Code | /plugins install https://github.com/runkids/figlens/tree/main in a session, then /reload |
skillshare installs the same plugin on several hosts at once: skillshare plugin add https://github.com/runkids/figlens.git --target claude --target codex --target cursor -g; update it later with skillshare plugin update figlens -g.
Restart the host or start a new session, then check that the figlens tools are listed. A plugin install copies the repository: about 7 MB, plus the Git history (about 60 MB) in Codex. Antigravity loads only the first 24 KB of the skill; the server's workflow tool serves the full guidance. Muse is not supported yet. Host matrix and what was verified
<a id="setup-mcp"></a>
MCP
Claude Code (Node.js 18+, macOS/Linux):
claude mcp add --transport stdio --scope local figlens -- npx -y @runkids/figlens mcp
Codex CLI (Node.js 18+, macOS/Linux):
codex mcp add figlens -- npx -y @runkids/figlens mcp
Any MCP client:
{
"mcpServers": {
"figlens": {
"command": "npx",
"args": ["-y", "@runkids/figlens", "mcp"]
}
}
}
Without Node.js, install the standalone binary (CLI) and use "command": "figlens", "args": ["mcp"]. Start a new session and check that the figlens tools are listed (/mcp in Claude Code). No separate skill install is required. Add --root <dir> after mcp to limit which folders figlens may read and write.
<a id="mcp-args"></a>
MCP startup arguments
Add these options after mcp in your client's args. These are the only MCP startup options; both are optional and repeatable.
| Option | Meaning |
|---|---|
| --root DIR | Allows design reads and exports inside DIR and its subfolders. Without it, figlens adds no path restriction: OS permissions still apply. It does not default to the current project or scan the computer. |
| --storage-root DIR | Allows explicitly requested custom index storage inside DIR and its subfolders. It does not select or change the default storage location. |
Use absolute paths to existing directories. Each option and path is a separate array item; repeat the option for multiple folders. --root means a path boundary, not administrator access, and only restricts figlens MCP, not the agent's other tools.
Example with two design/output roots and two allowed storage roots:
{
"mcpServers": {
"figlens": {
"command": "npx",
"args": [
"-y", "@runkids/figlens", "mcp",
"--root", "/absolute/designs",
"--root", "/absolute/project",
"--storage-root", "/absolute/storage-a",
"--storage-root", "/absolute/storage-b"
]
}
}
}
There is no figlens mcp --storage option. Choose the actual location with the index tool's storage argument (an absolute path under an allowed storage root), or CLI figlens index prepare design.fig --storage /absolute/storage-a. After prepare, figlens remembers that workspace's location and reuses it across restarts and hosts without repeating storage or --storage-root. Without a custom location, the per-user defaults apply; no storage flag is needed.
To keep these paths out of a checked-in config, or to share designs across Git worktrees, see roots in a checked-in config.
Multiple storage roots only expand the allowed locations: each storage argument still selects one location. They do not distribute, sync or back up indexes. An existing workspace database cannot be moved by simply naming another root; figlens refuses the conflicting location.
<a id="setup-pi"></a>
Pi
One package ships the CLI, MCP, viewer, /figlens commands and skill:
pi install npm:@runkids/figlens
<a id="setup-opencode"></a>
OpenCode V2
Install the package in OpenCode V2:
opencode plugin add @runkids/figlens
Restart the host, then run /figlens help. OpenCode V2
<a id="setup-omp"></a>
OMP
Install the same package in OMP:
omp plugin install @runkids/figlens
Restart the host, then run /figlens help. OMP
<a id="setup-cli"></a>
CLI
Run it through npm, or install the standalone binary:
npx @runkids/figlens --help # Node.js 18+, no install
curl -fsSL https://raw.githubusercontent.com/runkids/figlens/main/scripts/install.sh | sh # macOS, Linux
brew install runkids/tap/figlens # Homebrew
irm https://raw.githubusercontent.com/runkids/figlens/main/scripts/install.ps1 | iex # Windows PowerShell
npx runs the binary of the package version it resolves. Script installs update with figlens update; Homebrew installs with brew upgrade figlens. Binaries cover macOS (Apple silicon, Intel), Linux (arm64, x86_64) and Windows (x86_64).
An agent that uses the CLI reads its guidance with figlens workflow build (also audit, images, search, plan, planning-details and the opt-in yolo), which always matches the binary's version, or from the agent skill.
Different Figma accounts can use figlens pull --login --account work and optional "account": "work" in the source mapping. Existing default sessions need no migration. Figma accounts: browser login and API tokens.
figlens sources init [DIR]: Scan local .fig files into .figlens/sources.json
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
111.0kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
109.5kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.0kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
47.8kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
