Lattice SCIM MCP connector
The Lattice SCIM connector brings Lattice user accounts to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can look up, create, update and remove Lattice users with one endpoint and every change recorded.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Lattice SCIM user created this month.
Working in Lattice SCIM with Elaichi
-
List all Lattice SCIM users
-
Get single Lattice SCIM user by ID
-
List all Lattice SCIM schemas
How to connect Lattice SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lattice 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.
Lattice 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.
Lattice 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.
Lattice 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.
Lattice 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 Lattice 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 Lattice 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 Lattice SCIM is logged.
-
HR
Set up a new hire in Lattice
Create the Lattice user account on their first day with the right name, email, title and manager, straight from the offer details, without opening the admin console.
-
IT
Offboard a leaver the same day
Find the departing employee's Lattice account and deactivate or remove it as part of the leaver checklist, then confirm it is gone.
-
People Ops
Catch Lattice up after a reorg
When someone changes team, title or manager, update just those fields on their Lattice user so reviews and one-on-ones route to the right person.
-
IT
Check who actually has a Lattice account
Pull the full list of Lattice users and compare it with your HR roster to spot people who are missing, duplicated or should no longer be there.
-
Security
Answer an access question in seconds
Look up a single Lattice user by ID to see whether the account is active and what it holds when a manager or auditor asks.
-
IT
Understand what Lattice will accept
Read the Lattice SCIM schemas, resource types and provider settings to know which user fields exist before you plan a bulk change or a new provisioning flow.
Try asking
- “List every Lattice SCIM user created this month.”
- “Which Lattice SCIM users are missing a work email?”
- “Create a Lattice SCIM user for our new analyst.”
What connecting Lattice SCIM gets you
6 screens from Elaichi, each doing one job for your Lattice SCIM account.
Ask Elaichi to work across your apps.
List every Lattice SCIM user created this month.
Which Lattice SCIM users are missing a work email?
Create a Lattice SCIM user for our new analyst.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Lattice SCIM users in plain language.
The agent reads live Lattice SCIM user records and answers in a sentence.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Lattice SCIM.
One org endpoint over OAuth, no SDK to write and no shared API key.
Tool catalog
9 Lattice SCIM tools, no custom code.
User, schema, resource type and service provider config methods are cataloged and ready.
Toolboxes
Each team gets its own Lattice SCIM toolbox.
People Ops, IT and Security work from separate curated toolboxes over the same connector.
Shared connections
Teammates use Lattice SCIM without seeing credentials.
One admin connects the account, the table shows every team and member sharing it.
Audit log
Every Lattice SCIM call is written down.
When, who, what happened, type and resource, appended for each user record touched.
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.
Lattice SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Lattice 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
Lattice SCIM
Queued
Automations
A schedule provisions and reports, not a chat.
Six steps fetch Lattice SCIM users, group them, draft a digest, then a person approves.
Lattice SCIM health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Schemas
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
People Ops 34%
IT Provisioning 27%
Security 21%
EMEA 18%
Collections and dashboards
Lattice SCIM headcount numbers arrive on schedule.
Four metrics, 14 days of users created and a team breakdown, computed without a model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lattice SCIM
All three can connect Lattice 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 Lattice SCIM tools | Allow or restrict single Lattice 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 Lattice 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.
Lattice SCIM tools for your AI agents
9 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lattice 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 Lattice SCIM to Claude?
Connect Lattice SCIM in Elaichi first: you paste the SCIM API key from your Lattice admin settings, and that is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi, and from then on it can work with your Lattice users.
Does Lattice SCIM work with ChatGPT and Cursor as well as Claude?
Yes. Once Lattice SCIM 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 Lattice once and every client you use picks it up.
What can an AI agent actually do with my Lattice SCIM data?
With Lattice SCIM connected, an agent can list every Lattice user, look one up by ID, create an account for a new hire, update a person's name, email, title or manager, change only a single field, and deactivate or delete an account when someone leaves. It can also read the Lattice SCIM schemas, resource types and provider settings so it knows which fields exist. In practice that means asking in plain language to set up, fix or remove a Lattice user and having it done.
Does connecting Lattice SCIM give the AI everything in Lattice?
No. The Lattice SCIM connector only reaches user accounts and the SCIM configuration that the API key you pasted is allowed to see, and nothing else in Lattice. Elaichi can narrow that further, for example to reading users but never removing them, and it can never grant more than the key itself allows.
Can I stop an agent from deleting or changing things in Lattice SCIM?
Yes. In Elaichi you restrict Lattice SCIM per action, so you can allow listing and looking up users while restricting creating, updating or deleting them. 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 Lattice SCIM connection when someone leaves?
When you offboard a person in Elaichi, their access to Lattice SCIM and every other connected application ends at once, in every client they used. A shared Lattice SCIM connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Lattice SCIM once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Lattice SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lattice 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 Lattice SCIM?
Yes. Both let Claude, ChatGPT or Cursor use Lattice 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 Lattice SCIM call.
How is Elaichi different from Composio for Lattice 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 Lattice 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 Lattice 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