# Indeed SCIM MCP connector

The Indeed SCIM connector brings your Indeed employer user accounts into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot, 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 |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## 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.

## Indeed SCIM MCP connector for 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.

## Indeed SCIM MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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`.

## Indeed SCIM MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.

## Indeed SCIM MCP connector for 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.

## Indeed SCIM MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## 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

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Indeed SCIM tool needs "Use your connected apps". 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. Think hard before granting Use your connected apps, which can also delete in 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.

## Elaichi vs Zapier MCP vs Composio for Indeed SCIM

All three can connect Indeed 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. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Indeed SCIM tools | Allow or restrict single Indeed 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 Indeed 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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, Microsoft Copilot, 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 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.

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

### Does the Indeed SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

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.

### Is Elaichi an alternative to Zapier MCP for Indeed SCIM?

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.

### How is Elaichi different from Composio for Indeed 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 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.

## 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.
