HRIS
Lattice SCIM MCP connector
The Lattice SCIM connector brings Lattice user accounts to Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can look up, create, update and remove Lattice users with one endpoint and every change recorded.
-
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.
9 tools
How to connect
How to connect Lattice SCIM to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Lattice SCIM once
-
Open Connections, choose Add connection, and pick Lattice SCIM.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Lattice SCIM API key. One person generates a token in Lattice 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.
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.
Connect Lattice SCIM to 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.
Connect Lattice SCIM to 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.
Connect Lattice SCIM to 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 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.
Use cases
What teams do with Lattice SCIM through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Lattice SCIM gets you
6 screens from the product, each doing one job for your Lattice SCIM account.
The agent
Ask about Lattice SCIM users in plain language.
The agent reads live Lattice SCIM user records and answers in a sentence.
- users
- schemas
- resource types
- service provider configs
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Lattice SCIM.
One org endpoint over OAuth, no SDK to write and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
9 Lattice SCIM tools, no custom code.
User, schema, resource type and service provider config methods are cataloged and ready.
- List all Lattice SCIM users
- Create a Lattice SCIM user
- Get single Lattice SCIM user by ID
- Update a Lattice SCIM user by ID
ElaichiToolsToolboxes
Each team gets its own Lattice SCIM toolbox.
People Ops, IT and Security work from separate curated toolboxes over the same connector.
- People Ops
- IT
- Security
- Engineering
ElaichiToolboxesShared connections
Teammates use Lattice SCIM without seeing credentials.
One admin connects the account, the table shows every team and member sharing it.
- People Ops
- IT Provisioning
- Security
- EMEA
ElaichiConnectionsAudit log
Every Lattice SCIM call is written down.
When, who, what happened, type and resource, appended for each user record touched.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 provisions and reports, not a chat.
Six steps fetch Lattice SCIM users, group them, draft a digest, then a person approves.
Lattice SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Lattice SCIM
Queued
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.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking creating, updating or deleting them. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client at all, so no prompt, however worded, can reach it.
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 and every other client together.
Put Lattice SCIM in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.