Figma MCP connector
The Figma connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- OAuth or API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
List the files in our Design System project.
Working in Figma with Elaichi
-
List all Figma activity logs
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Figma to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Figma MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Figma MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Figma MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Figma MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Figma to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Figma through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Figma is logged.
-
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?”
What connecting Figma gets you
6 screens from Elaichi, each doing one job for your Figma account.
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, Cursor or Microsoft Copilot
The agent
Ask about Figma files in plain language.
Answers come from live files, projects, comments and versions in Figma.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Figma.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
55 Figma tools are ready to call.
Files, projects, components, comments and versions covered without custom code.
ElaichiToolboxesToolboxes
Every team gets its own Figma toolbox.
Curate toolboxes per team so each one sees the Figma tools it needs.
ElaichiConnectionsShared connections
Teammates work in Figma without a token.
See who connected each Figma account and which teams and members share it.
ElaichiAudit logAudit log
Every Figma call is on the record.
When, who, what happened, type and resource for each comment and file read.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Figma digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch files
Figma
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Figma
Queued
Automations
A schedule drafts your Figma digest.
Fetch files, group them, draft a digest, get approval, post a Figma comment.
Figma health
Refreshed 4 minutes ago · every 15 minutes · from the files collection
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%
Collections and dashboards
Figma activity counted, not summarized.
Four metrics, 14 days of files created and a team breakdown, refreshed on schedule.
For IT and engineering
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.
| 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricted separately in Elaichi. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot