figlens
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workflowA | Read built-in figlens skill guidance for this agent: build for design-to-code and project reuse, images for website asset preparation, plan for scoped implementation planning, planning-details for page/multi-page work or unresolved design dependencies, yolo for explicitly requested autonomous implementation and temporary-plan cleanup. Returns the requested guide only; no design file, project read/write, implementation, verification or cleanup is performed. Ordinary design questions and exports can use the design tools directly. |
| treeA | List node ids, types and names under a chosen root. A shallow outline locates pages and frames when their names are unknown; find searches known names or visible text directly. |
| findA | Search stored layer names and text (case-insensitive). Returns ids, paths, local sizes and text previews. Does not expand instance children; use inspect on the instance. |
| inspectA | Compact expanded node summary: bounds, layout, typography, text previews and child counts. For image decisions, images=true adds original dimensions/bytes and source-pixel rectangles before masks, not blur diagnoses. Depth and a 200-node budget bound the summary; image paints have their own 200-item limit. nodes returns full design data. |
| nodesC | A node or exact instance sublayer as Figma REST nodes.json: instances expanded, fills, text, auto-layout. Can be large. |
| variablesB | The variables a frame binds (collections, modes, aliases); without a node, every local variable. |
| bundleA | Write a design bundle zip for one node or exact instance sublayer: nodes, variables, assets, reference render, context.md. When the user requests related component states, pass states=true to include their explicit variants and evidence gaps; no MCP configuration change is needed. |
| exportA | Export a node to SVG, PNG, JPG, WebP or AVIF. Create the output directory first. Returns metadata and, for raster formats, an inline image. PNG suits inline references. For website assets, follow the target project's existing image pipeline; otherwise start with WebP for bitmaps, sized for display dimensions and DPR using scale/maxSize and quality/maxKb. SVG embeds original images and can be large; keep it for vector artwork. scale, quality and maxSize affect raster formats only; maxSize defaults to 1600. Check returned dimensions/bytes and isError; read content on failure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.