Skip to content

Figma MCP connector

The Figma connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read your Figma files, components, styles, versions, and comments, and post comments back, with every person signed in as themselves and every action logged.

  • How it connects. OAuth or API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Figma to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Figma once

  1. Open Connections, choose Add connection, and pick Figma.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own Figma app, then approve. Figma needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

figma
Figma
Aurora Solar
Figma SCIM
Lucid
Magic Patterns
Miro
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Figma MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Figma MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Figma MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Figma to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Figma through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Design

    Read the comment thread before a review

    Ask for every open comment on a file and who left it, then walk into the review already knowing where the disagreements are.

  • Product

    Leave feedback without opening the file

    Post a comment on a specific frame in Figma from Claude while writing the spec, and react to a teammate's comment to show it has been seen.

  • Engineering

    Find the right component before building

    Look up a component or component set by name, read its description, and confirm which file it lives in so the build matches the library.

  • Brand

    Check a page against the style library

    Pull the team's color and text styles from Figma and compare them with what a landing page or deck is actually using.

  • Design ops

    See what changed in a file this week

    List a file's version history and the team's recent activity in Figma to catch up after time away or prepare a weekly update.

  • Marketing

    Grab a frame for the launch post

    Ask for an image of a named frame in Figma and drop it into release notes or a campaign brief without exporting by hand.

Try asking

  • “List the files in our Design System project.”
  • “Show unresolved comments on the checkout flow file.”
  • “Which components changed in this file since last week?”

See all 55 Figma tools below

Compare

Elaichi vs Zapier MCP vs Composio for Figma

All three can connect Figma to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Figma, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Figma tools Allow or restrict single Figma tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Figma call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Figma tools for your AI agents

55 tools are ready to call through Elaichi's MCP endpoint the moment you connect Figma, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Figma gets you

6 screens from the product, each doing one job for your Figma account.

The agent

Ask about Figma files in plain language.

Answers come from live files, projects, comments and versions in Figma.

  • files
  • projects
  • comments
  • components

Ask Elaichi to work across your apps.

List the files in our Design System project.

Show unresolved comments on the checkout flow file.

Which components changed in this file since last week?

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Figma.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

55 Figma tools are ready to call.

Files, projects, components, comments and versions covered without custom code.

  • List all Figma activity logs
  • List all Figma me
  • Get single Figma file by ID
  • List all Figma team projects
ElaichiTools
Tool Action Description
List all Figma activity logs List List organization activity logs in Figma, newest or oldest first (order asc or desc), optionally filtered by events (comma-separated event types) and a start_time/end_time Unix range. Returns event id, timestamp, actor, action type and context; paginate with cursor. Requires a plan access token (API key auth) or an OAuth connection granted org:activity_log_read by an organization admin.
List all Figma me List Get information about the authenticated user in Figma. Returns id (unique user identifier), handle (user name), img_url (profile image URL), and email (user email).
Get single Figma file by ID Get Get details of a file in Figma using id. Returns name, lastModified, thumbnailUrl, editorType, linkAccess, and version as metadata, along with document structure, components, componentSets, schemaVersion, styles, mainFileKey, and branches.
List all Figma team projects List List projects in a specified Figma team using team_id. Returns project fields such as id, name, and last_modified that identify and describe each visible project.
List all Figma project files List List files in a given project in Figma. Requires project_id. Returns file details such as name, key, thumbnail_url, and file type in the response.

Toolboxes

Every team gets its own Figma toolbox.

Curate toolboxes per team so each one sees the Figma tools it needs.

  • Product design
  • Design systems
  • Engineering
  • Brand
ElaichiToolboxes
Name Source template Tools Created

Product design toolbox

Figma · files and prototypes

Figma starter 18 Mar 4, 2026

Design systems toolbox

Figma · components and libraries

— 9 Mar 2, 2026

Engineering toolbox

Figma · file versions and specs

— 24 Feb 27, 2026

Brand toolbox

Figma · marketing projects and assets

Figma starter 6 Feb 19, 2026

Research toolbox

Figma · comments and feedback

— 31 Jan 30, 2026

Design ops toolbox

Figma · team projects and activity logs

— 12 Jan 22, 2026

Shared connections

Teammates work in Figma without a token.

See who connected each Figma account and which teams and members share it.

  • Product design
  • Design systems
  • Brand studio
  • Mobile
ElaichiConnections
Connection Scope Status Access
FI

Figma (Product design)

Connected by Emily Carter

Personal • Active 1 team · 6 members
FI

Figma (Design systems)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
FI

Figma (Brand studio)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
FI

Figma (Mobile)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
FI

Figma (Web platform)

Connected by Ryan Hayes

Personal • Active Not shared
FI

Figma (Design ops)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Figma call is on the record.

When, who, what happened, type and resource for each comment and file read.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Figma Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Figma Files Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Figma Files List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your Figma digest.

Fetch files, group them, draft a digest, get approval, post a Figma comment.

Figma digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch files

    Figma

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Figma

    Queued

Collections and dashboards

Figma activity counted, not summarized.

Four metrics, 14 days of files created and a team breakdown, refreshed on schedule.

Figma health

Refreshed 4 minutes ago · every 15 minutes · from the files collection

Live

Files

1,284 ↓ 12%

Projects

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Files created

Last 14 days

By team

Share of activity

Product design 34%

Design systems 27%

Brand studio 21%

Mobile 18%

FAQ

Frequently asked questions

How do I connect Figma to Claude?

Connect Figma in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Figma asks each company to register its own OAuth application inside Figma, so an administrator brings a client ID and secret once when setting up the connector in Elaichi. After that, each person simply approves access in the normal Figma sign-in window and nobody else handles a credential.

Does Figma work with ChatGPT and Cursor as well as Claude?

Yes. Once Figma is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Figma once and every client your team uses can reach it.

What can an AI agent actually do with my Figma files?

An agent can browse your Figma teams, projects, and files, read the comments on a file, list version history and recent activity, and look up components, component sets, and styles from your libraries. It can also fetch an image of a frame, post a comment, and add or remove a reaction. Short, specific asks such as "list open comments on the checkout file" work better than long paragraphs.

Does connecting Figma give the AI access to every file in my workspace?

No. Access follows the person who signed in, so the agent only sees the Figma teams, projects, and files that person can already open. Elaichi can narrow that further with restrictions, and it can never widen access beyond what Figma itself allows that person.

Can my team share one Figma connection?

Yes. One person connects Figma in Elaichi and shares the connection with a team, so nobody else has to register an application or touch a client secret. Each teammate still signs in to Figma as themselves, so their own permissions apply and the audit log names the actual person behind every comment or lookup.

Can I stop an agent from deleting or changing things in Figma?

Yes. In Figma the connector can only create and delete comments and reactions, and each of those actions can be blocked separately in Elaichi. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can trigger it, and the rest of the connector keeps working read-only.

What happens to a Figma connection when someone leaves the company?

Offboarding a person in Elaichi ends their access to Figma through every AI client at once. If they connected Figma and shared it with a team, the shared connection keeps working for everyone else. Disconnecting Figma once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Does the Figma MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Figma is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Figma?

Yes. Both let Claude, ChatGPT or Cursor use Figma. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Figma call.

How is Elaichi different from Composio for Figma?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Figma: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Figma in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.