figma-restoration-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment mode (development/production). | production |
| PUPPETEER_EXECUTABLE_PATH | No | Path to Chrome/Chromium executable for screenshot generation. |
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 |
|---|---|
| figma_compareB | Simple Figma component comparison tool: compare existing screenshots and generate diff.png for visual analysis |
| snapdom_screenshotB | Take high-quality screenshots using snapDOM technology for precise DOM-to-image capture |
| optimize_svgC | Optimize SVG files using SVGO (SVG Optimizer) with customizable configuration |
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 3 tools
The three tools have distinct purposes: comparing screenshots, optimizing SVGs, and taking screenshots. There is slight conceptual overlap between figma_compare and snapdom_screenshot, but their roles are clear: one captures, one compares. No two tools appear to do the same thing.
Names use consistent snake_case, but the pattern is mixed: optimize_svg and snapdom_screenshot are verb-first, while figma_compare is object-first. This is readable but not perfectly predictable.
With only 3 tools, the server is on the lighter side, but each tool serves a distinct function in a focused restoration workflow. The count is reasonable for a specialized utility server, though slightly thin.
The tools cover capture, comparison, and optimization, but the server name suggests a broader restoration workflow. Missing operations like image conversion, batch processing, or asset export create notable gaps that agents may need to work around.