Skip to main content
Glama
tokensqueezer-mcp

tokensqueezer-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_figma_contextB

Get the current squeezed Figma design context + optional multimodal PNG preview. Supports 9 output formats and on-the-fly compression levels (full, compact, sparse).

get_design_specB

Get the DESIGN.md specification (YAML tokens, Multi-Theme Light/Dark modes, Components, and WCAG 2.2 Accessibility Audit) for the selected Figma frame.

add_figma_annotationB

Write an AI feedback note or annotation directly back onto the selected Figma layer (attaches native Dev Mode annotation + visual AI Note card on the Figma canvas).

list_figma_componentsA

List all components, component sets, instances, and variant states in the current Figma selection tree with full hierarchy paths.

get_design_tokensA

Get design tokens from the current Figma selection in W3C Design Tokens Community Group (DTCG) JSON format, including colors, multi-theme modes, typography, spacing, shadows, and gradients.

compare_selectionsB

Compare the current Figma selection with the previous selection (token delta, node count delta, and added/removed layer names).

get_accessibility_reportA

Get WCAG 2.2 sRGB relative-luminance contrast audit results for the current Figma selection.

search_layersA

Search layers by name, text content, or semantic type in the current Figma selection tree and return full breadcrumb paths.

Prompts

Interactive templates invoked by user choice

NameDescription
implement_componentGenerate production-ready UI code from the current TokenSqueezer Figma selection using semantic tokens and visual preview.
extract_design_tokensMap W3C DTCG tokens and Light/Dark variable modes from the current Figma frame into CSS variables / Tailwind theme config.
audit_accessibilityReview color contrast, heading hierarchy, button/link semantics, and post actionable findings back to Figma.

Resources

Contextual data attached and managed by the client

NameDescription
figma-contextLatest squeezed Figma design output from the currently selected frame.
figma-design-tokensW3C DTCG JSON design tokens for the current Figma selection.
figma-design-specDESIGN.md specification + WCAG 2.2 audit for the current Figma selection.

TDQS

A3.6/5.0

Scored across 8 tools

Disambiguation3/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.