tokensqueezer-mcp
Related Servers
Alternatives to tokensqueezer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to draw UI directly on a Figma Desktop canvas and read existing designs back as structured JSON, tokens, CSS, and screenshots, all over a localhost bridge without external API keys.109 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to inspect the currently selected Figma element or find layers by name, extracting layout, colors, typography, borders, and shadows as compact design tokens while exporting SVG and PNG assets straight into the local project. It connects over a local WebSocket to a running Figma session, so no API key, Dev Mode subscription, or manual ZIP export is required.-
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect Figma selections, navigate pages, render previews, generate starter code, and submit user-approved canvas edits through a local bridge.3 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to read and edit the file currently open in Figma Desktop through a local development plugin, supporting node inspection, JSON/image exports, and arbitrary Plugin API scripts without REST API rate limits.711 npmMIT
- FlicenseNot 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.-
TDQS
Scored across 8 tools
Most tools have distinct purposes (search_layers, compare_selections, add_figma_annotation, get_accessibility_report), but three tools overlap heavily on extracting design data: get_figma_context, get_design_spec, and get_design_tokens all return tokens/structure from the same selection in different formats. An agent must read descriptions carefully to pick the right one, since the 'squeezed design context' could plausibly include the spec and tokens.
All names follow a consistent snake_case verb_noun pattern (get_, list_, add_, search_, compare_). Minor inconsistency: 'figma' is embedded in some names (add_figma_annotation, list_figma_components, get_figma_context) but absent in others (get_design_spec, get_design_tokens, search_layers), which adds noise but doesn't break predictability.
Eight tools is well within the ideal 3-15 range and each earns its place: four read/extract tools, one search, one compare, one audit, and one write-back. No redundant or trivially thin tools for a Figma design-context server.
The surface covers the full read lifecycle (context, spec, tokens, components, layers, accessibility) plus a write-back tool (add_figma_annotation) and a delta tool (compare_selections), which is strong coverage. Minor gaps: no asset/image export beyond the PNG preview, and no bulk annotation or token export-to-file operation, but agents can work around these.