Can my team share one Figma SCIM connection?

Yes. One admin connects Figma SCIM in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every Figma user or group change in the audit log carries their own name.

Design

Figma SCIM MCP connector

The Figma SCIM connector brings Figma user accounts and groups into Elaichi, so Claude, ChatGPT, Cursor, and the Elaichi Agent can list, create, update, and remove Figma members and groups within each person's own access, with every change logged.

Connect on Elaichi How to connect

How it connects. Connects with an 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.

14 tools

How to connect

How to connect Figma SCIM to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Figma SCIM once

Open Connections, choose Add connection, and pick Figma SCIM.
Optionally set Share with to give a team access, then press Connect.
Paste a Figma SCIM API key. One person generates a token in Figma SCIM and pastes it once. Everyone else works through Share with, and never sees it.

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

Add connection

Choose a connector.

figma scim

All categories

Figma SCIM

Aurora Solar

Figma

Lucid

Magic Patterns

Miro

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 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 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 today. 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.

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.

Connect Figma SCIM on Elaichi See pricing

Use cases

What teams do with Figma SCIM through Elaichi

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

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”

See all 14 Figma SCIM tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Figma SCIM, 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 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	$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 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.

See it in Elaichi

What connecting Figma SCIM gets you

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

The agent

Ask about Figma seats in plain language.

Elaichi's agent answers from live Figma SCIM users and groups, no admin console needed.

users
groups
service provider configs
tenants

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 or Cursor

MCP clients

One endpoint puts Figma SCIM in every client.

Claude, ChatGPT and Cursor connect over OAuth, with 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

All 14 Figma SCIM tools, no code needed.

Users, groups and provider config, every method cataloged without a line of custom code.

List all Figma SCIM users
Get single Figma SCIM user by ID
Delete a Figma SCIM user by ID
Create a Figma SCIM user

ElaichiTools

Tool	Action	Description
List all Figma SCIM users	List	List SCIM-provisioned users in the Figma organization (GET /scim/v2/{tenant}/Users). Returns SCIM user resources with id, userName (email), displayName, active, seat role, name, externalId, enterprise attributes (department, cost center, organization) and the figmaAdmin flag. Filter with userName eq "email" or externalId eq "value"; pages with count (max 3000) and startIndex. Calling this also binds existing Figma accounts to SCIM.
Get single Figma SCIM user by ID	Get	Get one SCIM user in Figma by Figma user id (GET /scim/v2/{tenant}/Users/{id}). Returns the full SCIM user resource. Required: id. To find an id, list users with a userName filter.
Delete a Figma SCIM user by ID	Delete	Permanently delete a user from Figma and from the SCIM provisioning log (DELETE /scim/v2/{tenant}/Users/{id}). To keep the account but revoke access, deactivate instead with partial_update (active=false). Required: id. Returns 204 with no body.
Create a Figma SCIM user	Create	Provision a user in Figma via SCIM (POST /scim/v2/{tenant}/Users). If a Figma account with that email already exists it is bound to SCIM and updated. Required: schemas, userName (email) and active; optional seat role (Enterprise plan), display name, title, name, externalId, enterprise attributes and figmaAdmin. Returns the created user with its Figma id.
Update a Figma SCIM user by ID	Update	Overwrite all attributes of a SCIM user in Figma (PUT /scim/v2/{tenant}/Users/{id}). Send the complete user; attributes omitted are cleared. Common uses: change email (userName), display name, seat role, cost center. Required: id, schemas, userName, active. Returns the updated user.

Toolboxes

Each team gets its own Figma SCIM toolbox.

IT provisions, HR offboards, Design ops manages groups, each scoped to what that team does.

IT
People ops
Security
Design ops

ElaichiToolboxes

Name	Source template	Tools	Created
IT toolbox Figma SCIM · users and groups	Figma SCIM starter	18	Mar 4, 2026
People ops toolbox Figma SCIM · joiners and leavers	—	9	Mar 2, 2026
Security toolbox Figma SCIM · access reviews	—	24	Feb 27, 2026
Design ops toolbox Figma SCIM · project groups	Figma SCIM starter	6	Feb 19, 2026
Finance toolbox Figma SCIM · seat counts	—	31	Jan 30, 2026
Compliance toolbox Figma SCIM · audit evidence	—	12	Jan 22, 2026

Shared connections

Share the Figma SCIM connection, never the key.

One admin connects, teammates provision users and groups without ever seeing the API key.

IT
People ops
Security
Design ops

ElaichiConnections

Connection	Scope	Status	Access
FI Figma SCIM (IT) Connected by Emily Carter	Personal	• Active	1 team · 6 members
FI Figma SCIM (People ops) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
FI Figma SCIM (Security) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
FI Figma SCIM (Design ops) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
FI Figma SCIM (Finance) Connected by Ryan Hayes	Personal	• Active	Not shared
FI Figma SCIM (Contractors) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every Figma SCIM change names who made it.

When, who, what happened, type and resource, for each user created, updated or removed.

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 SCIM Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Figma SCIM Users Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Figma SCIM Users 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

Scheduled Figma SCIM cleanup runs end to end.

Users are fetched, grouped by status, a digest drafted, approved, then changes posted back.

Figma SCIM digest

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

Run now

✓

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 Michael Brennan

Approve Deny
Post the digest

Figma SCIM

Queued

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.

Figma SCIM health

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

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

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, 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 blocking deletes or updates. A restricted action is left out of the AI client's tool list entirely and cannot be called, 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, 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Connect Figma SCIM Talk to us

Works with: 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.