figlens
Related Servers
Alternatives to figlens
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables offline reading and rendering of Figma .fig files, allowing AI agents to extract design specs, export assets, and generate code without needing the Figma API or network access.262MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read and inspect local Figma .fig files entirely offline, exposing document structure, geometry, styles, text, components, variables, and embedded images via MCP tools.12100 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to extract, inspect, search, and bundle design context from local Figma .fig files entirely offline, exposing frame summaries, node context, style tokens, assets, vector SVGs, and visual-match review via MCP.MIT
- AlicenseAqualityBmaintenanceProvides read-only Figma design data to AI agents via MCP, supporting local .fig files and browser-based figma.com access without plugins or API tokens.1891 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to read and write a user's Figma file through the Figma Plugin API, offline and privately, without API tokens or rate limits.26 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI apps to open, inspect, modify, render, and save local Figma files—including Design, Slides, FigJam, and Sites—without a Figma account, app, or API limits, and to turn designs into code using exact values.1MIT
TDQS
Scored across 20 tools
Many tools touch the same design graph: tree, find, search, inspect and nodes all help locate or read nodes, while diff, changes and watch all relate to change tracking. The descriptions draw useful boundaries, but an agent must still choose carefully, and watch multiplexes many subscription/change operations into one tool.
Names are mostly lowercase and readable, but they mix verbs (export, find, inspect) with nouns (tree, nodes, changes) and inconsistent snake_case compounds (export_batch, compare_image). There is no predictable verb_noun convention throughout.
Twenty tools is heavy for one server, even though each maps to a real capability across export, inspection, indexing, jobs, models, tracking and verification. The scope is broad enough to justify many tools, but the surface feels unwieldy and several tools bundle multiple operations.
The set covers inspection, search, single and batch export, bundles, verification, visual comparison, freshness, indexing/jobs and change tracking, so core read-only design workflows have no major dead end. Minor gaps remain, such as explicit image-query search despite image model support, and some lifecycle actions are buried inside compound tools.