# Indeed SCIM MCP connector The Indeed SCIM connector brings your Indeed employer user accounts into Elaichi, so Claude, ChatGPT, Cursor, or the Elaichi Agent can list, look up, create, update, and remove Indeed users on your behalf, inside your own access. Source: https://elaichi.ai/connectors/indeedscim/ ## Facts | | | | --- | --- | | Application | Indeed SCIM | | Category | HRIS | | AI tools | 5 | | Authentication | App credentials | | 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 Indeed SCIM is connected - List Indeed SCIM users created in the last 14 days. - Show the Indeed SCIM user record for Priya Nair. - Which Indeed SCIM users have no active email set? ## Connect Indeed SCIM in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Indeed SCIM. 2. Optionally set Share with, then press Connect. 3. Paste your Indeed SCIM app credentials. Indeed SCIM authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Indeed SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Indeed 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 Indeed 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 Indeed 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 Indeed 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 Indeed 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 Indeed SCIM through Elaichi ### Set up a new recruiter's Indeed account IT. When a recruiter joins, ask for their Indeed user to be created with the right name and work email, so they can start posting jobs on their first day without a ticket. ### Check who still holds an Indeed seat HR. Pull the full list of Indeed users and compare it against the current staff roster to spot anyone who has moved teams or left the company. ### Fix a name or email after a change Recruiting. When someone changes their name or the company switches email domains, update the Indeed user record in one request instead of clicking through the admin console. ### Remove Indeed access on the last day Security. As part of leaver processing, delete the departing employee's Indeed user so nobody outside the company can post jobs or view candidates under your employer account. ### Look up one person's Indeed account details People operations. Ask which email, display name, and status are on file for a colleague's Indeed user before you answer their question about why they cannot sign in. ### Audit hiring team access before a campaign Talent acquisition. Before a big hiring push, list every Indeed user, confirm the hiring managers who need access already have accounts, and create the ones that are missing. ## Frequently asked questions ### How do I connect Indeed SCIM to Claude? First connect Indeed SCIM in Elaichi by entering the app credentials Indeed gives you for SCIM provisioning. There is no OAuth application to register and 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. Claude will ask you to sign in to Elaichi, and from then on it can work with your Indeed user accounts as you. ### Does Indeed SCIM work with ChatGPT and Cursor as well as Claude? Yes. Once Indeed 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 Indeed SCIM once and every client you use picks it up. ### What can an AI agent actually do with my Indeed SCIM data? An agent connected to Indeed SCIM can list every user on your Indeed employer account, look up one person's account details, create a new Indeed user for a joiner, update a name or email on an existing user, and remove a user when someone leaves. It works with user accounts only, so it does not touch job postings, candidates, or applications. You ask in plain language, for example asking it to create an Indeed user for the recruiter who starts Monday. ### Does connecting Indeed SCIM give the AI access to every user on our Indeed account? The AI only ever sees what the person who signed in to Indeed SCIM is allowed to see. If your Indeed SCIM credentials cover your whole employer account, the agent can work across all of those users, and if they are scoped to a subset, so is the agent. Elaichi can narrow that further with restrictions, but it can never widen what Indeed itself allows. ### Can my team share one Indeed SCIM connection? Yes. One administrator connects Indeed SCIM in Elaichi and shares the connection with a team, and nobody else on that team ever handles the Indeed credentials. Each teammate still signs in to Elaichi as themselves, so every change to an Indeed user in the audit log names the person who made it, not a shared account. ### Can I stop an agent from deleting or changing Indeed users? Yes. Restrictions in Elaichi work per action, so you can allow listing and looking up users through Indeed SCIM while blocking create, update, or delete. 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 an Indeed SCIM connection when someone leaves? When you offboard a person in Elaichi, their access to Indeed SCIM through every client ends at once. If they were using a connection someone else shared, that connection keeps working for everyone else on the team. If you want Indeed SCIM gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together. ## All 5 Indeed SCIM tools Every tool below is callable through https://api.elaichi.ai/mcp once Indeed SCIM is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Indeed SCIM users** (List). List Indeed SCIM users filtered by externalId or email. Returns a maximum of one user; an error is returned if multiple users match the filter. Returns: schemas, id, externalId, userName, name, displayName, emails, active, meta, urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg. Required: filter. - **Get single Indeed SCIM user by ID** (Get). Get a single Indeed SCIM user by encrypted account ID, including all associated employer organization data. Returns: schemas, id, externalId, userName, name, displayName, emails, active, meta, urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg. Required: id. - **Create a Indeed SCIM user** (Create). Create an Indeed SCIM user with optional employer organization membership. Returns: schemas, id, externalId, userName, name, displayName, emails, active, meta, urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg. Required: schemas, externalId, userName, userType, emails (one primary), name (givenName, familyName). - **Update a Indeed SCIM user by ID** (Update). Update an Indeed SCIM user by encrypted account ID. This is a full overwrite — every value on the account is replaced even when an attribute is empty or omitted, so include complete user data in the request body. Returns: schemas, id, externalId, userName, name, displayName, emails, active, meta, urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg. Required: id. - **Delete a Indeed SCIM user by ID** (Delete). Delete an Indeed SCIM user by encrypted account ID. The user is automatically removed from any employer organizations and the deletion process can take up to 30 minutes to complete. Returns an empty 204 response on success. Required: id.