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.261MIT
- 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.12275 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityAmaintenanceProvides 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.18115 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.236 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read the live state of an open Figma file — variables, modes, components, prototype edges and assets — and to export design tokens and code packages for web, iOS, Android, React, Django and Tauri through a user-run loopback bridge with separate read and write gates.2MIT
TDQS
Scored across 8 tools
The tools mostly have distinct roles: tree/find for discovery, inspect/nodes for detail levels, variables for bindings, bundle/export for outputs, and workflow for guidance. There is some potential overlap between tree and find, and between inspect and nodes, but the descriptions explicitly route agents based on known names, depth, and data size.
All tool names are single lowercase tokens with no casing or separator inconsistencies. The set mixes nouns and verbs (tree, nodes, variables vs. find, inspect, export, bundle), so it does not follow a strict verb_noun pattern, but it is still highly readable and consistent in style.
Eight tools is well-scoped for a Figma inspection, variable extraction, export, and design-bundle workflow. Each tool has a clear lane, and there is no obvious redundancy or missing count pressure.
The surface covers discovery, detailed node extraction, variables, export formats, bundle creation, and workflow guidance, which is strong lifecycle coverage for a read-only design-to-code server. Minor gaps may exist around richer project/file metadata or style-token extraction separate from nodes/variables, but agents can work around them.