Indeed SCIM MCP connector

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.

Yes. Once Indeed 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 Indeed SCIM once and every client you use picks it up.

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.

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.

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.

Yes. Restrictions in Elaichi work per action, so you can allow listing and looking up users through Indeed SCIM while restricting create, update, or delete. 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.

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, Microsoft Copilot, and every other client together.

Yes. Indeed 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.

Yes. Both let Claude, ChatGPT or Cursor use Indeed 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 Indeed SCIM call.

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 Indeed SCIM: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.