Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for remote SSE mode (default 3000).
LOG_LEVELNoLog level for structured logging (pino). Defaults to 'info'.
MCP_TRANSPORTNoTransport mode: 'stdio' (default) for local, 'sse' for remote HTTP/SSE.
FIGMA_ACCESS_TOKENNoFigma personal access token for REST API tools (optional).

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_statusA

Check whether the Figma Desktop companion plugin is connected and get active document metadata

ping_figmaA

Ping the connected Figma companion plugin to verify live canvas communication

get_document_infoA

Retrieve the active Figma document name, all pages, current page, and currently selected nodes

create_frameA

Create a new frame (container or artboard) on the Figma canvas

create_rectangleB

Create a rectangle or box element (useful for cards, buttons, visual dividers)

create_textA

Create a styled text element on the Figma canvas or inside a container. Strictly disallows emojis (use 'create_svg_icon' for vector icons). Automatically calculates and applies calibrated proportional leading (line-height) and optical tracking (letter-spacing) according to typographic hierarchy.

set_autolayoutA

Configure Flexbox/AutoLayout rules (direction, padding, gap, alignment, wrapping) on an existing frame

update_nodeC

Update dimensions, coordinates, fills, images (supports local file paths), corner radius, opacity, layout alignment, or text auto-resize of an existing node

apply_typography_themeB

Batch apply heading and body typography system across all text nodes inside a frame or artboard

delete_nodesA

Delete one or more nodes from the Figma canvas by their IDs

duplicate_nodeA

Duplicate an existing node or screen (e.g. for creating variant states for prototyping)

set_strokeB

Add or update border stroke on a frame, card, button, or rectangle

set_text_contentA

Update the characters of an existing text layer. Emojis are strictly sanitized and proportional leading and tracking are automatically recalibrated.

find_nodesA

Search for nodes on the current page by name keyword or node type (FRAME, TEXT, RECTANGLE, etc.)

manage_pageA

Create a new page in the document or switch the active page

export_node_imageB

Render a PNG snapshot of a frame or component and return as base64 data URI for visual feedback

inspect_nodeA

Inspect detailed properties, layout settings, dimensions, and children of any node by ID

get_selectionB

Inspect currently selected elements on the Figma canvas

get_design_contextB

Retrieve a token-efficient semantic outline of the active document page or a specific screen (screens, buttons, cards, inputs, and flow starting points) without heavy vector noise

generate_ui_treeA

Generate a complete UI screen or component hierarchy in a single atomic pass from a structured JSON specification. Enforces enterprise UI/UX & HCI standards: strictly disallows emojis (use 'create_svg_icon' for icons), snaps spacing to 8pt grid, enforces minimum 44px interactive touch targets per Apple HIG / WCAG (Fitts's Law), and applies calibrated typography leading and tracking.

plan_screen_architectureA

Architect and plan a multi-section UI screen creation OR design edit/refactor before code generation. Decomposes the UI into an ordered sequence of structured steps, establishes typography scale, 8pt grid dimensions, and layout constraints (wrapping, auto-layout directions, stretch alignment) to guarantee zero overflow/overlap. MANDATORY PROTOCOL GATE: Once this tool returns, the LLM MUST present the generated roadmap to the user for explicit confirmation before executing any canvas mutations.

set_prototype_interactionA

Wire an interactive prototype transition from a clickable element (button, card) to a target screen or modal

set_flow_starting_pointB

Mark a screen frame as a named prototype flow starting point (e.g. 'Onboarding Flow', 'Purchase Flow')

get_prototype_connectionsA

Inspect all flow starting points and interactive prototype wiring across the current page

batch_link_prototypeB

Link multiple prototype transitions in a single call (e.g. wiring up an entire user journey)

get_document_tokensA

Extract active design tokens from the document (local paint color styles, text typography styles, and effect styles)

create_svg_iconB

Render and insert scalable SVG vector graphics (icons, logos, custom vector shapes) onto the canvas

create_ellipseA

Create an ellipse or circular shape node on the canvas (ideal for user avatars, status badges, circular buttons, and indicator dots)

create_componentA

Create a reusable Figma component master on the canvas, or convert an existing frame/node into a component

create_component_instanceA

Instantiate a reusable component instance from a master component ID, retaining link to the main component

set_effectsB

Apply elevation shadows, inner shadows, and blurs to a node (DROP_SHADOW, INNER_SHADOW, LAYER_BLUR, BACKGROUND_BLUR)

create_sectionA

Create a Figma Section to organize related artboards, user journeys, or screen flows on the canvas

focus_viewportA

Pan and zoom the Figma canvas viewport to focus on specific nodes, with optional selection

set_overlay_interactionB

Configure interactive overlay prototype interactions (modals, dialogs, bottom sheets, slide-over panels, and dropdowns)

lint_design_complianceA

Audit and score any screen or the active canvas page against enterprise UI/UX and HCI compliance standards (Fitts's Law 44px touch targets, 8pt grid spacing consistency, proportional typography leading, and zero emojis)

generate_state_matrixB

Generate the complete 5 States of UI (Ideal, Empty with onboarding CTA, Loading/Skeleton shimmer, Empathetic Error with 1-click retry, and Partial/Boundary stress-test) as a Figma Section or Component Set

audit_ux_heuristicsB

Audit visual design and interaction architecture against empirical cognitive psychology and Laws of UX (Hick's Law choice overload, Fitts's Law touch target reach & destructive action proximity, Miller's Law chunking, and Jakob's Law conventions)

validate_user_journeyB

Verify user journey continuum and prototype interaction completeness across canvas artboards, flagging orphan screens, dead-end traps, and unprotected destructive actions without confirmation safeguards

generate_interactive_variantsB

Generate a complete interactive Component Set with Default, Hover, Pressed, Focused (WCAG 2.4.7 accessible focus ring), and Disabled states with pre-wired prototype Smart Animate transitions

lint_ux_microcopyA

Audit text copy across screens for UX writing anti-patterns (Lorem Ipsum placeholders, ambiguous/lazy CTAs like 'Submit', robotic blaming error messages, and cognitive strain all-caps text), recommending empathetic high-converting alternatives

rest_get_fileB

Headless read of full Figma file metadata, version history, components, styles, and document tree from Figma Cloud via REST API (requires FIGMA_ACCESS_TOKEN)

rest_get_file_nodesA

Fetch specific nodes by ID directly from the cloud via REST API without loading the entire document

rest_get_imagesB

Render high-resolution cloud images/exports of frames or components using Figma Cloud rendering engine

rest_get_commentsA

Read collaboration feedback, review threads, and pins left on the file from Figma Cloud

rest_post_commentB

Post a review comment or design critique directly to a Figma screen or pin via REST API

rest_get_variablesC

Read Figma Enterprise / Organization Variables and token collections (color palettes, spacing, modes) via REST API

rest_get_componentsB

List published component library definitions, component sets, and documentation links in the file

Prompts

Interactive templates invoked by user choice

NameDescription
design_product_flowGuide the AI assistant to design a multi-screen product flow with AutoLayout and wire interactive prototyping
wire_interactive_prototypeInstruct the AI assistant to inspect existing screens and wire up user journey transitions
audit_ux_designInstruct the AI assistant to perform an automated HCI, typography, and UX design compliance audit
architect_ux_experienceInstruct the AI assistant to conduct a comprehensive UX architectural review, generate the 5 UI states, audit cognitive heuristics, and validate user journey flow continuity

Resources

Contextual data attached and managed by the client

NameDescription
document_summaryActive Figma document name, all pages, current page, and selection count
active_tokensActive design tokens extracted from the document (color styles, typography styles, effects)
prototype_flowsInteractive prototype flow starting points and connection graph on the current page

TDQS

B3.2/5.0

Scored across 47 tools

Disambiguation2/5

Several tools overlap heavily: ping_figma vs get_figma_status both check companion-plugin connectivity, and validate_user_journey, lint_design_compliance, audit_ux_heuristics, and lint_ux_microcopy all perform design/UX audits with subtle boundaries. Creation/planning tools (generate_ui_tree, plan_screen_architecture, create_frame) and retrieval tools (get_document_info, get_design_context, inspect_node, rest_get_file) also blur together, making misselection likely.

Naming Consistency4/5

Nearly all tools follow a verb_noun snake_case pattern, with a clear rest_ prefix grouping cloud/REST operations. Minor deviations in verb choice (create vs generate vs plan vs audit vs lint) but the convention is predictable and readable throughout.

Tool Count2/5

47 tools is heavy for a Figma companion server, and the surface includes many overlapping audit, retrieval, and creation paths that could be consolidated. The breadth is partly justified by canvas editing plus REST access, but the count clearly exceeds a well-scoped set.

Completeness4/5

Coverage is broad: create/update/delete nodes, text, frames, components, prototype wiring, design tokens, inspection, export, and cloud REST access including comments and variables. Minor gaps exist (e.g., no page deletion, no dedicated component-update or prototype-removal tool), but core workflows are well supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues