Figma CLI for AI Agents

GET STARTED FOR FREE
Framework Integration Gradient
Figma Logo
CLI Logo
divider

Introduction

CLIs are eating MCPs. The industry is converging on the very same idea. MCPs for all their merit can be token hungry, slow, and unreliable for complex tool chaining. However, coding agents have become incredibly good at working with CLIs, and in fact they are far more comfortable working with CLI tools than MCP.

With Composio's Universal CLI, your coding agents can talk to over 850+ SaaS applications. With Figma, agents can add a comment to this figma file, convert design tokens to tailwind css, delete a reaction from a comment, and more — all without worrying about authentication.

This guide walks you through Composio Universal CLI and explains how you can connect it with coding agents like Claude Code, Codex, OpenCode, etc, for end-to-end Figma automation.

Also integrate Figma with

What is Universal CLI and why use it?

The idea behind building the universal CLI is to give agents a single command interface to interact with all your external applications. Here's what you'll get with it:

  • Agent-friendly: Coding agents like Claude Code, Codex, and OpenCode can use CLI tools natively — no MCP setup required.
  • Authentication handled: Connect once via OAuth or API Key, and all CLI commands work with your credentials automatically.
  • Tool discovery: Search, inspect, and execute 20,000+ tools across 850+ apps from one interface.
  • Trigger support: Use triggers to listen for events across your apps, powered by real-time webhooks or polling under the hood.
  • Type generation: Generate typed schemas for autocomplete and type safety in your projects.

Prerequisites

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login you'll be redirected to sign in page, finish the complete flow and you're all set.

Composio CLI authentication flow

Connecting Figma to Coding Agents via Universal CLI

Once it is installed, it's essentially done. Claude Code, Codex, OpenCode, OpenClaw, or any other agent will be able to access the CLI. A few steps to give agents access to your apps.

  1. Launch your Coding Agent — Claude Code, Codex, OpenCode, anything you prefer.
  2. Prompt it to "Authenticate with Figma"
  3. Complete the authentication and authorization flow and your Figma integration is all set.
  4. Start asking anything you want.

Supported Tools & Triggers

Tools
Add a comment to a filePosts 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 commentPosts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id.
Create a webhookCreates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`.
Create dev resourcesCreates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.
Create, modify, or delete variablesManages 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 commentDeletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.
Delete a reactionDeletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.
Delete a webhookPermanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible.
Delete dev resourceDeletes 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 tailwindConvert design tokens to tailwind css configuration.
Detect backgroundDetect background layers for selected nodes.
Discover Figma Resources🔍 smart figma resource discovery - never guess ids again!
Download Figma ImagesDownload images from figma file nodes.
Extract design tokensExtract design tokens from figma files.
Extract Prototype InteractionsExtract prototype interactions and animations from figma files.
Get activity logsRetrieves activity log events from figma, allowing filtering by event types, time range, and pagination.
Get a webhookRetrieves detailed information about a specific webhook by its id, provided the webhook exists and is accessible to the user.
Get comments in a fileRetrieves 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 componentGet component data with automatic simplification.
Get component setRetrieves detailed metadata for a specific published figma component set using its unique `key`.
Get current userRetrieves detailed information for the currently authenticated figma user.
Get dev resourcesRetrieves development resources (e.
Get file componentsRetrieves published components from a figma file, which must be a main file (not a branch) acting as a library.
Get file component setsRetrieves all published component sets from the specified figma main file (file key must not be for a branch).
Get file jsonGet figma file data with automatic simplification.
Get files in a projectFetches a list of files in a figma project, optionally including branch metadata.
Get file stylesRetrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main figma file (not a branch).
Get image fillsRetrieves temporary (14-day expiry) download urls for all image fills in a figma file; requires `imageref` from `paint` objects to map urls.
Get library analytics component action dataRetrieves component insertion and detachment analytics for a specified figma library, groupable by 'component' or 'team' and filterable by a date range (yyyy-mm-dd).
Get library analytics component usage dataRetrieves component usage analytics for a specified figma library file (identified by `file key`), with data groupable by 'component' or 'file'.
Get library analytics style action dataRetrieves style usage analytics (insertions, detachments) for a figma library, grouped by 'style' or 'team'; if providing a date range, ensure end date is not before start date.
Get library analytics style usage dataRetrieves style usage analytics for a figma library (specified by a valid `file key`), allowing data to be grouped by 'file' or 'style'.
Get library analytics variable action dataRetrieves weekly, paginated analytics data on variable insertions and detachments for a specified figma library (identified by `file key`), groupable by 'variable' or 'team', and filterable by an optional date range.
Get library analytics variable usage dataRetrieves paginated analytics data on variable usage from a specified figma library, grouped by 'file' or 'variable', for libraries with enabled analytics.
Get local variablesRetrieves all local/remote variables for a figma file/branch; crucial for obtaining mode-specific values which `/v1/files/{file key}/variables/published` omits.
Get paymentsRetrieves a user's payment information for a figma plugin, widget, or community file; the authenticated identity must own the resource.
Get projects in a teamRetrieves projects within a specified figma team that are visible to the authenticated user.
Get published variablesRetrieves variables published from a specified figma file; this api is available only to full members of enterprise organizations.
Get reactions for a commentRetrieves reactions for a specific comment in a figma file.
Get styleRetrieves detailed metadata for a specific style in figma using its unique style key.
Get team componentsRetrieves components published in a specific figma team's library; the team must have published components, otherwise an empty list is returned.
Get team component setsRetrieves a paginated list of published component sets (collections of reusable ui elements) from a specified figma team's library.
Get team stylesRetrieves a paginated list of published styles, such as colors or text attributes, from a specified figma team's library.
Get team webhooksRetrieves all webhooks registered for a specified figma team.
Get versions of a fileRetrieves the version history for a figma file or branch, as specified by its `file key`.
Get webhook requestsRetrieves a history of webhook requests for a specific figma webhook subscription; data is available for requests sent within the last seven days.
Render images of file nodesRenders specified nodes from a figma file as images (jpg, pdf, png, svg), returning a map of node ids to image urls (or `null` for failed nodes); images expire after 30 days and are capped at 32 megapixels (larger requests are scaled down).
Update a webhookUpdates an existing figma webhook, identified by `webhook id`, allowing modification of its event type, endpoint, passcode, status, or description.
Update dev resourcesUpdates the name and/or url of one or more existing figma dev resources, each identified by its unique `id`.

Universal CLI Commands for Figma

You can also manually execute CLI commands to interact with your Figma.

Connect your Figma account

Link your Figma account and verify the connection:

bash
# Connect your Figma account (opens OAuth flow)
composio connected-accounts link figma

# Verify the connection
composio connected-accounts list --toolkits figma

Discover Figma tools

Search and inspect available Figma tools:

bash
# List all available Figma tools
composio tools list --toolkit figma

# Search for Figma tools by action
composio tools search "figma"

# Inspect a tool's input schema
composio tools info FIGMA_ADD_A_COMMENT_TO_A_FILE

Common Figma Actions

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

bash
composio tools execute FIGMA_ADD_A_COMMENT_TO_A_FILE \
  --message "Great work on this design!" \
  --file_key "your_file_key_here"

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

bash
composio tools execute FIGMA_ADD_A_REACTION_TO_A_COMMENT \
  --emoji ":heart:" \
  --file_key "figma_file_key_123" \
  --comment_id "1234567890"

Create a webhook — Creates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`

bash
composio tools execute FIGMA_CREATE_A_WEBHOOK \
  --team_id "YOUR_TEAM_ID_HERE" \
  --endpoint "https://example.com/api/figma-webhooks" \
  --passcode "s3cr3tPa$$c0de" \
  --event_type "VAL_FILE_COMMENT"

Create dev resources — Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node

bash
composio tools execute FIGMA_CREATE_DEV_RESOURCES \
  --dev_resources "<array>"

Generate Type Definitions

Generate typed schemas for Figma tools to get autocomplete and type safety in your project:

bash
# Auto-detect language
composio generate --toolkits figma

# TypeScript
composio ts generate --toolkits figma

# Python
composio py generate --toolkits figma

Tips & Tricks

  • Always inspect a tool's input schema before executing: composio tools info <TOOL_NAME>
  • Pipe output with jq for better readability: composio tools execute TOOL_NAME -d '{}' | jq
  • Set COMPOSIO_API_KEY as an environment variable for CI/CD pipelines
  • Use composio dev logs tools to inspect execution logs and debug issues

Next Steps

  • Try asking your coding agent to perform various Figma operations
  • Explore cross-app workflows by connecting more toolkits
  • Set up triggers for real-time automation
  • Use composio generate for typed schemas in your projects

How to build Figma MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Figma MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Figma MCP with Claude Agent SDK

Claude Code

Claude Code

Use Figma MCP with Claude Code

Codex

Codex

Use Figma MCP with Codex

OpenClaw

OpenClaw

Use Figma MCP with OpenClaw

Google ADK

Google ADK

Use Figma MCP with Google ADK

LangChain

LangChain

Use Figma MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Figma MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Figma MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Figma MCP with LlamaIndex

CrewAI

CrewAI

Use Figma MCP with CrewAI

FAQ

What is the Composio Universal CLI?

The Composio Universal CLI is a single command-line interface that lets coding agents and developers interact with 850+ SaaS applications. It handles authentication, tool discovery, action execution, and trigger setup — all from the terminal, without needing to configure MCP servers.

Which coding agents work with the Composio CLI?

Any coding agent that can run shell commands works with the Composio CLI — including Claude Code, Codex, OpenCode, OpenClaw, and others. Once the CLI is installed, agents automatically discover and use the composio commands to interact with Figma and other connected apps.

How is the CLI different from using an MCP server for Figma?

MCP servers require configuration and can be token-heavy for complex workflows. The CLI gives agents a direct, lightweight interface — no server setup needed. Agents simply call composio commands like any other shell tool. It's faster to set up, more reliable for multi-step tool chaining, and works natively with how coding agents already operate.

How safe is my Figma data when using the Composio CLI?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Figma data and credentials are handled as safely as possible. You can also bring your own OAuth credentials for full control.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free