# 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. Source: https://elaichi.ai/connectors/latticescim/ ## Facts | | | | --- | --- | | Application | Lattice SCIM | | Category | HRIS | | AI tools | 9 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Lattice SCIM is connected - 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. ## Connect Lattice SCIM in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Lattice SCIM. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Lattice SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Lattice SCIM to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Lattice SCIM to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Lattice SCIM tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Lattice SCIM through Elaichi ### Set up a new hire in Lattice HR. 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. ### Offboard a leaver the same day IT. Find the departing employee's Lattice account and deactivate or remove it as part of the leaver checklist, then confirm it is gone. ### Catch Lattice up after a reorg People Ops. 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. ### Check who actually has a Lattice account IT. 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. ### Answer an access question in seconds Security. 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. ### Understand what Lattice will accept IT. 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. ## 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 my team share one Lattice SCIM connection? Yes. One admin connects Lattice SCIM in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each person still signs in to Elaichi as themselves, so every Lattice user they create, change or remove is logged under their own name. ### 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. ## All 9 Lattice SCIM tools Every tool below is callable through https://api.elaichi.ai/mcp once Lattice SCIM is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Lattice SCIM users** (List). List Lattice SCIM users with optional SCIM filter expressions. Returns each user with id, userName, displayName, active, name, emails, title, timezone, meta, and enterprise/lattice extension attributes. - **Create a Lattice SCIM user** (Create). Create a new Lattice SCIM user. Returns the created user object including id, userName, displayName, active, name, emails, title, timezone, and meta. Required: userName (work email in valid email format). - **Get single Lattice SCIM user by ID** (Get). Get a single Lattice SCIM user by id. Returns the full user resource including id, userName, displayName, active, name, emails, title, timezone, meta, and enterprise/lattice extension attributes. Required: id. - **Update a Lattice SCIM user by ID** (Update). Replace a Lattice SCIM user by id. Returns the updated user object including id, userName, displayName, active, name, emails, title, timezone, and meta. Required: id, userName (work email). - **Delete a Lattice SCIM user by ID** (Delete). Delete or deprovision a Lattice SCIM user by id. Returns an empty 204 response on success. Required: id. - **Lattice SCIM users partial update** (Update). Partially update a Lattice SCIM user by id. Used to activate or deactivate users by setting the active field, and to update syncable attributes like name, title, timezone, department, manager, startDate, birthDate, and gender. Returns: schemas, id, externalId, name, displayName, nickName, userName, profileUrl, title, timezone, active, emails, phoneNumbers, photos, groups, meta,… - **List all Lattice SCIM schemas** (List). List Lattice SCIM schema definitions available for user provisioning. Returns 6 schemas including the core User, enterprise extension, and Lattice custom attributes schemas. Returns: id, name, description, attributes, meta. - **List all Lattice SCIM service provider config** (List). Get the Lattice SCIM ServiceProviderConfig describing which SCIM features the service provider supports. Returns: patch, bulk, filter, sort, changePassword, etag, authenticationSchemes. - **List all Lattice SCIM resource types** (List). List the SCIM resource types available in Lattice. Returns: id, name, endpoint, schema, schemaExtensions.