How to integrate Figma MCP with Claude Agent SDK

This guide walks you through connecting Figma to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Figma agent that can add a comment to this figma file, convert design tokens to tailwind css, delete a reaction from a comment through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Figma account through Composio's Figma MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Figma logoFigma
Oauth2Api Key

Figma is a collaborative interface design tool for teams and individuals. It streamlines design workflows with real-time collaboration and easy sharing.

52 Tools

Introduction

This guide walks you through connecting Figma to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Figma agent that can add a comment to this figma file, convert design tokens to tailwind css, delete a reaction from a comment through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Figma account through Composio's Figma MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Figma with

ChatGPTOpenAI Agents SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Figma
  • Configure an AI agent that can use Figma as a tool
  • Run a live chat session where you can ask the agent to perform Figma operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Figma MCP server, and what's possible with it?

The Figma MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Figma account. It provides structured and secure access to your Figma workspace, so your agent can perform actions like commenting on designs, managing design tokens, linking developer resources, and automating collaboration workflows on your behalf.

  • Automated commenting and feedback loops: Have your agent add, reply to, or delete comments on Figma files and branches to streamline design reviews and team discussions.
  • Design token management and conversion: Let the agent extract, update, or convert design tokens in your files, including generating Tailwind CSS configurations for seamless dev handoff.
  • Developer resource integration: Automatically attach, update, or remove dev resources linked to Figma nodes, bridging the gap between design and development with contextual documentation or code references.
  • Webhook setup and automation: Enable your agent to create or delete webhooks for team events, making it easy to trigger notifications or workflows based on design activity.
  • Collaborative variable management: Empower the agent to batch-create, modify, or delete variables, collections, and modes across your design system, keeping everything consistent and up to date.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Figma account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Figma functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Figma
  const session = await composio.create(USER_ID, {
    toolkits: ['figma'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Figma
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Figma tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Figma
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Figma and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['figma']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Figma tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Figma through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Figma action and event your agent gets out of the box.

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.

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.

Get library analytics component action data

Retrieves 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 data

Retrieves 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 data

Retrieves 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 data

Retrieves style usage analytics for a published Figma library.

Get library analytics variable action data

Retrieves 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 data

Retrieves paginated analytics data on variable usage from a specified Figma library, grouped by 'file' or 'variable', for libraries with enabled analytics.

Get local variables

Retrieves all local/remote variables for a Figma file/branch; crucial for obtaining mode-specific values which `/v1/files/{file_key}/variables/published` omits.

Get payments

Retrieves a user's payment information for a Figma plugin, widget, or Community file; the authenticated identity must own the resource.

Get projects in a team

Retrieves projects within a specified Figma team that are visible to the authenticated user.

Get published variables

Retrieves variables published from a specified Figma file; this API is available only to full members of Enterprise organizations.

Get reactions for a comment

Retrieves reactions for a specific comment in a Figma file.

Get SCIM service provider config

Get Figma's SCIM service provider configuration.

Get style

Retrieves detailed metadata for a specific style in Figma using its unique style key.

Get team components

Retrieves components published in a specific Figma team's library; the team must have published components, otherwise an empty list is returned.

Get team component sets

Retrieves a paginated list of published component sets (collections of reusable UI elements) from a specified Figma team's library.

Get team styles

Retrieves a paginated list of published styles (fill colors, text styles, effects, grids) from a specified Figma team's library.

Get webhooks

Retrieves all webhooks registered for a specified Figma context (team, project, or file).

Get versions of a file

Retrieves the version history for a Figma file or branch, as specified by its `file_key`.

Get webhook requests

Retrieves 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 nodes

Render Figma nodes as images (PNG, JPG, SVG, PDF).

Update a webhook

Updates an existing Figma webhook, identified by `webhook_id`, allowing modification of its event type, endpoint, passcode, status, or description.

Update dev resources

Updates the name and/or URL of one or more existing Figma Dev Resources, each identified by its unique `id`.

FRAMEWORKS

How to build Figma MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Figma MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Figma MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Figma MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Figma MCP with Claude Cowork

Codex logo

Codex

Use Figma MCP with Codex

Cursor logo

Cursor

Use Figma MCP with Cursor

OpenClaw logo

OpenClaw

Use Figma MCP with OpenClaw

Hermes logo

Hermes

Use Figma MCP with Hermes

CLI logo

CLI

Use Figma MCP with CLI

Google ADK logo

Google ADK

Use Figma MCP with Google ADK

LangChain logo

LangChain

Use Figma MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Figma MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Figma MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Figma MCP with LlamaIndex

CrewAI logo

CrewAI

Use Figma MCP with CrewAI

OpenCode logo

OpenCode

Use Figma MCP with OpenCode

VS Code logo

VS Code

Use Figma MCP with VS Code

FAQ

Frequently asked questions

With a standalone Figma MCP server, the agents and LLMs can only access a fixed set of Figma tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Figma and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Figma tools.

Yes, absolutely. You can configure which Figma scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

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.

Start with Figma.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Figma tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies