Figma SCIM MCP connector
The Figma SCIM connector brings Figma user accounts and groups into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent can list, create, update, and remove Figma members and groups within each person's own access, with every change logged.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Figma user who is not in a group yet
Working in Figma SCIM with Elaichi
-
List all Figma SCIM users
-
Get single Figma SCIM user by ID
-
List all Figma SCIM groups
How to connect Figma SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Figma SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM is logged.
-
IT
Provision a new hire's Figma account
Create the Figma user on day one and drop them into the right groups, without opening the admin console or waiting for a ticket to move.
-
People ops
Remove a leaver from Figma the same day
Ask for someone's Figma account to be removed as part of offboarding, and confirm it is gone before the day ends.
-
Security
Run a Figma access review in minutes
Pull every Figma user and group, spot accounts that should not be there, and tidy group membership while the list is in front of you.
-
Design ops
Keep Figma groups matched to project teams
Add a contractor to the Brand group for a launch, then take them out when the work wraps, with the change recorded.
-
Finance
Check who is actually holding a Figma seat
List Figma users by status to see which seats are in use, so license renewals are based on real headcount rather than a guess.
-
Compliance
Answer who changed what in Figma
Every user created, updated or removed through the connector is in the audit log with a name and a time, ready for the next audit request.
Try asking
- “List every Figma user who is not in a group yet”
- “Add the new designers to the Brand group in Figma”
- “Remove Priya's Figma account, she left on Friday”
What connecting Figma SCIM gets you
6 screens from Elaichi, each doing one job for your Figma SCIM account.
Ask Elaichi to work across your apps.
List every Figma user who is not in a group yet
Add the new designers to the Brand group in Figma
Remove Priya's Figma account, she left on Friday
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Figma seats in plain language.
Elaichi's agent answers from live Figma SCIM users and groups, no admin console needed.
Copy the endpoint
AI apps
One endpoint puts Figma SCIM in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
All 14 Figma SCIM tools, no code needed.
Users, groups and provider config, every method cataloged without a line of custom code.
Toolboxes
Each team gets its own Figma SCIM toolbox.
IT provisions, HR offboards, Design ops manages groups, each scoped to what that team does.
Shared connections
Share the Figma SCIM connection, never the key.
One admin connects, teammates provision users and groups without ever seeing the API key.
Audit log
Every Figma SCIM change names who made it.
When, who, what happened, type and resource, for each user created, updated or removed.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Figma SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Figma SCIM
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 SCIM
Queued
Workflows
Scheduled Figma SCIM cleanup runs end to end.
Users are fetched, grouped by status, a digest drafted, approved, then changes posted back.
Figma SCIM health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT 34%
People ops 27%
Security 21%
Design ops 18%
Collections and dashboards
Figma SCIM seat numbers, computed without a model.
Four metrics, 14 days of users created and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Figma SCIM
All three can connect Figma SCIM 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 SCIM tools | Allow or restrict single Figma SCIM 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 SCIM 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 SCIM tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect Figma SCIM, 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 SCIM to Claude?
Connect Figma SCIM in Elaichi by pasting the Figma SCIM API key from your Figma organization settings, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi as yourself and Figma SCIM is available in the conversation.
Does Figma SCIM work with ChatGPT and Cursor as well as Claude?
Yes. Figma SCIM is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. Each person signs in as themselves in every client.
What can an AI agent actually do with my Figma SCIM data?
With Figma SCIM connected, an agent can list the Figma users and groups in your organization, look up a single person, create a new user, update their details, add them to or remove them from groups, and delete an account when someone leaves. It can also check the provisioning configuration. Short, concrete asks such as "remove Priya's Figma account" work better than long sentences.
Does connecting Figma SCIM give the AI control of my whole Figma organization?
No. Figma SCIM in Elaichi runs within the scope of the API key that was connected and the access of the person who signed in, and Elaichi can narrow that further by team or by action. Elaichi never widens what Figma allows, and provisioning actions never touch design files.
Can I stop an agent from deleting or changing things in Figma SCIM?
Yes. Restrictions in Elaichi apply per action, so you can allow listing Figma users and groups while restricting deletes or updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Figma SCIM connection when someone leaves?
Offboarding that person in Elaichi ends their access to Figma SCIM at once, across every client they used. A shared Figma SCIM connection keeps working for everyone else on the team. Disconnecting Figma SCIM once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Figma SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Figma SCIM 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 SCIM?
Yes. Both let Claude, ChatGPT or Cursor use Figma SCIM. 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 SCIM call.
How is Elaichi different from Composio for Figma SCIM?
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 SCIM: 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 SCIM 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