Figma

Developer tools

Figma for AI agents. Managed auth, ready-made tools.

Read design files, export frames as images, and read and post comments in your users' Figma files.

About Figma

With the Figma connector, your agent works with each user’s own Figma files through Agent200: it reads a file’s frames and layers, renders them as images, follows the comment threads and replies, and lists a team’s projects and files. Every user connects their own account through managed OAuth.

Figma is a collaborative design tool where teams design interfaces, build prototypes and hand designs off to developers.

Tools

What your agent can do in Figma.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Figma connection.

  • Get a file

    Read
    figma_get_file

    Read a file's pages, frames, layers and styles.

  • Get nodes

    Read
    figma_get_file_nodes

    Read specific frames or layers of a file by their ids.

  • Render images

    Read
    figma_get_images

    Export frames or layers as PNG, JPG, SVG or PDF.

  • List comments

    Read
    figma_list_comments

    Read the comments on a file.

  • Add a comment

    Write
    figma_create_comment

    Comment on a file or reply to a comment.

  • List team projects

    Read
    figma_list_projects

    List the projects in a team.

  • List project files

    Read
    figma_list_project_files

    List the files in a project.

  • Get version history

    Read
    figma_list_versions

    List a file's saved versions.

Control

Limits you can set.

You decide what your agent may do in Figma, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let your agent read files and comments, and switch off figma_create_comment if it should never post in a file.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use. A call outside them is refused.

Get started

Connect Figma
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Figma

    Each end user authorizes their own Figma account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Figma account, once.
    const connection = await agent200
      .user("user_123")
      .connect("figma");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Figma tools

    Name the user, the model and the tools. The model decides which Figma tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "List the open comments on the checkout redesign",
        tools: ["figma"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Figma's own page. You never see or store their Figma password.

  • What access is requested

    Figma lists the scopes on its consent screen, such as reading file content and reading or writing comments. The agent opens only the files that user can already open.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Figma connector and how to use it.

Agent brief
Connector: Figma, through Agent200. In code: "figma".
What it does: Read design files, export frames as images, and read and post comments in your users' Figma files.
Page: https://www.agent200.com/tools/figma/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Figma's own page, through the authorization link Agent200 returns. Never ask a user for a Figma password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: figma_get_file, figma_get_file_nodes, figma_get_images, figma_list_comments, figma_list_projects, figma_list_project_files, figma_list_versions. Write tools: figma_create_comment. Name "figma" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/figma/framework/claude/
   https://www.agent200.com/tools/figma/framework/chatgpt/
   https://www.agent200.com/tools/figma/framework/claude-code/
   https://www.agent200.com/tools/figma/framework/muse/
   https://www.agent200.com/tools/figma/framework/grok-bot/
   https://www.agent200.com/tools/figma/framework/openai-dots/
   https://www.agent200.com/tools/figma/framework/claude-duet/
   https://www.agent200.com/tools/figma/framework/hermes-agent/
   https://www.agent200.com/tools/figma/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/figma.md

Guides

Use Figma with the AI you build on.

Step-by-step setup for Figma with a specific model, assistant or agent framework.

FAQ

Figma and Agent200, answered.

Who handles the Figma OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Figma.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Figma connection, never another user's. It cannot reach anything the user or Figma has not authorized.

Can I limit what my agent can do in Figma?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with Figma.
Your agent does the rest.

Your users connect their own Figma accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)