Finds files, reads nodes and comments, posts feedback, extracts design tokens and variables, and renders node images.
52actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro 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.
Ayro checks which Figma account is currently authenticated before running other actions. Support can confirm the right person is connected before troubleshooting further.
Ayro 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.
Each card is one request a support team gets, and the Figma actions Ayro runs to close it.
Ayro 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.
Ayro 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.
Ayro 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.
Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Figma actions it has and picks the ones a request needs.
Authorize the Figma account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Figma actions that close it and chains as many as the request needs.
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 freeFigma · Ayro
What can you do in Figma without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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 Ayro can annotate a file and change its variable values, but there is no action that moves a layer or edits a frame.
All 52 actions your agent can call on Figma, straight from the live MCP connection.
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.
Posts a specified emoji reaction to an existing comment in a Figma file or branch, requiring valid file_key and comment_id.
Creates a Figma webhook to receive POST notifications when specific events occur.
Creates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node.
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.
Deletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment.
Deletes a specific emoji reaction from a comment in a Figma file; the user must have originally created the reaction.
Permanently deletes an existing webhook, identified by its unique webhook_id; this operation is irreversible.
Deletes a development resource (used to link Figma design elements to external developer information like code or tasks) from a specified Figma file.
Convert design tokens to Tailwind CSS configuration.
Detect background layers for selected nodes in a Figma file.
Smart Figma resource discovery - extract IDs from any Figma URL.
Download images from Figma file nodes.
Extract design tokens from Figma files by combining styles, variables, and node-extracted values.
Extract prototype interactions and animations from Figma files.
Retrieves activity log events from Figma, allowing filtering by event types, time range, and pagination.
Retrieves detailed information about a specific webhook by its ID, provided the webhook exists and is accessible to the user.
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.
Fetches metadata for a specific component using its unique identifier.
Retrieves detailed metadata for a specific published Figma component set using its unique key.
Retrieves detailed information for the currently authenticated Figma user.
Retrieves development resources (e.g., Jira/GitHub links) for a Figma main file, optionally filtering by specific node IDs.
Retrieves published components from a Figma file, which must be a main file (not a branch) acting as a library.
Retrieves all published component sets from the specified Figma main file (file_key must not be for a branch).
Get Figma Design file data with automatic simplification.
Get Figma file metadata including name, creator, last modification details, thumbnail, and access information.
Fetch JSON for specific node IDs from a Figma file to avoid full-file payload limits.
Fetches a list of files in a Figma project, optionally including branch metadata.
Retrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main Figma file (not a branch).
Retrieves temporary (14-day expiry) download URLs for all image fills in a Figma file; requires imageRef from Paint objects to map URLs.
Same connection, same setup. Pick the next one your team already uses.
Creates and imports designs, uploads assets to the content library, exports finished work in the right format, and comments on drafts under review.
Lists and creates DynaPictures workspaces, uploads the media assets templates draw on, and reports which templates are ready to generate from.
Compresses, resizes, or converts an image from a public URL, preserves EXIF metadata on request, and reports remaining quota.
Searches team files, creates projects and design files, reorganises what has drifted, and registers webhooks for Penpot events.
Captures a live page as a PDF or screenshot, hands over the finished link, and retires renders once they are no longer needed.
Reads project colours, text styles, and components, updates design tokens, uploads new screen versions, and clears annotations left on screens.

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