Figma

Figma MCP integration

Finds files, reads nodes and comments, posts feedback, extracts design tokens and variables, and renders node images.

52actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Add a comment to a file

    Lyro posts a comment on a Figma file to flag feedback or a question for the design team. Reviewers see notes right where the design lives instead of in a separate thread.

  • Get current user

    Lyro checks which Figma account is currently authenticated before running other actions. Support can confirm the right person is connected before troubleshooting further.

  • Render images of file nodes

    Lyro renders a Figma design node as an image file in the format someone needs. A designer or stakeholder gets a shareable preview without opening the Figma file.

See all 52 actions

How businesses use Figma + Lyro

Each card is one request a support team gets, and the Figma actions Lyro runs to close it.

  • Find the file and read what is actually in it

    Lyro locates the file across a team's projects, reads its metadata and the specific nodes in question, so a question about a screen is answered from the current file rather than an outdated export.

    Discover Figma ResourcesGet File MetadataGet File Nodes
  • Leave and follow feedback on a frame

    Lyro posts a comment on the frame being discussed, reads the thread that already exists on the file, and acknowledges a resolved note with a reaction, so review stays in Figma where designers see it.

    Add A Comment To A FileGet Comments In A FileAdd A Reaction To A Comment
  • Hand design tokens to engineering

    Lyro extracts the design tokens from a file, reads the local and published variables behind them, and converts the set into a Tailwind config, so the values reach code without being retyped.

    Extract Design TokensGet Local VariablesDesign Tokens To Tailwind
  • Watch a file for changes

    Lyro registers a webhook against a team, checks the deliveries it has received, and updates or removes it when the trigger is no longer needed, so downstream work reacts to real file activity.

    Create A WebhookGet Webhook RequestsUpdate A Webhook

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Figma actions it has and picks the ones a request needs.

  1. 01

    Connect Figma

    Authorize the Figma account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Figma actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Figma · Lyro

Everything else about Figma

Setup, permissions, and the limits of what Lyro can do inside Figma.

  • Not the canvas. The write surface is comments, dev resources, webhooks, and variables - Add A Comment To A File, Create Dev Resources, and Create, Modify, Or Delete Variables - so Lyro can annotate a file and change its variable values, but there is no action that moves a layer or edits a frame.

Every action available in Figma

All 52 actions your agent can call on Figma, straight from the live MCP connection.

  • Add a comment to a file

    Posts a new comment to a Figma file or branch, optionally replying to an existing root comment (replies cannot be nested); region_height and region_width in client_meta must be positive if defining a comment region.

  • Add a reaction to a comment

    Posts a specified emoji reaction to an existing comment in a Figma file or branch, requiring valid file_key and comment_id.

  • Create a webhook

    Creates a Figma webhook to receive POST notifications when specific events occur.

  • Create dev resources

    Creates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node.

  • Create, modify, or delete variables

    Manages variables, collections, modes, and their values in a Figma file via batch create/update/delete operations; use temporary IDs to link new related items in one request and ensure variableModeValues match the target variable's resolvedType.

  • Delete a comment

    Deletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment.

  • Delete a reaction

    Deletes a specific emoji reaction from a comment in a Figma file; the user must have originally created the reaction.

  • Delete a webhook

    Permanently deletes an existing webhook, identified by its unique webhook_id; this operation is irreversible.

  • Delete dev resource

    Deletes a development resource (used to link Figma design elements to external developer information like code or tasks) from a specified Figma file.

  • Design tokens to tailwind

    Convert design tokens to Tailwind CSS configuration.

  • Detect background layers

    Detect background layers for selected nodes in a Figma file.

  • Discover figma resources

    Smart Figma resource discovery - extract IDs from any Figma URL.

  • Download figma images

    Download images from Figma file nodes.

  • Extract design tokens

    Extract design tokens from Figma files by combining styles, variables, and node-extracted values.

  • Extract prototype interactions

    Extract prototype interactions and animations from Figma files.

  • Get activity logs

    Retrieves activity log events from Figma, allowing filtering by event types, time range, and pagination.

  • Get a webhook

    Retrieves detailed information about a specific webhook by its ID, provided the webhook exists and is accessible to the user.

  • Get comments in a file

    Retrieves all comments from an existing Figma file, identified by a valid file_key, returning details like content, author, position, and reactions, with an option for Markdown formatted content.

  • Get component

    Fetches metadata for a specific component using its unique identifier.

  • Get component set

    Retrieves detailed metadata for a specific published Figma component set using its unique key.

  • Get current user

    Retrieves detailed information for the currently authenticated Figma user.

  • Get dev resources

    Retrieves development resources (e.g., Jira/GitHub links) for a Figma main file, optionally filtering by specific node IDs.

  • Get file components

    Retrieves published components from a Figma file, which must be a main file (not a branch) acting as a library.

  • Get file component sets

    Retrieves all published component sets from the specified Figma main file (file_key must not be for a branch).

  • Get file JSON

    Get Figma Design file data with automatic simplification.

  • Get file metadata

    Get Figma file metadata including name, creator, last modification details, thumbnail, and access information.

  • Get file nodes

    Fetch JSON for specific node IDs from a Figma file to avoid full-file payload limits.

  • Get files in a project

    Fetches a list of files in a Figma project, optionally including branch metadata.

  • Get file styles

    Retrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main Figma file (not a branch).

  • Get image fills

    Retrieves temporary (14-day expiry) download URLs for all image fills in a Figma file; requires imageRef from Paint objects to map URLs.

Ready to connect Figma?

Authorize the account and your agent has all 52 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot