HRIS
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.
-
How it connects. App credentials. 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.
5 tools
How to connect
How to connect Indeed SCIM to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Indeed SCIM once
-
Open Connections, choose Add connection, and pick Indeed SCIM.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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 Indeed 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 Indeed 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 Indeed 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 Indeed 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 Indeed SCIM through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Set up a new recruiter's Indeed account
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.
-
HR
Check who still holds an Indeed seat
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.
-
Recruiting
Fix a name or email after a change
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.
-
Security
Remove Indeed access on the last day
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.
-
People operations
Look up one person's Indeed account details
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.
-
Talent acquisition
Audit hiring team access before a campaign
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.
Try asking
- “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?”
AI tools
Indeed SCIM tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Indeed 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 Indeed SCIM gets you
6 screens from the product, each doing one job for your Indeed SCIM account.
The agent
Ask about Indeed SCIM users in plain language.
Starter prompts return answers from live Indeed SCIM user records, no query syntax.
- users
- user profiles
- user accounts
- user records
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach the same endpoint.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
5 Indeed SCIM tools ready to call.
List, read, create, update and delete users with no custom code written.
- List all Indeed SCIM users
- Get single Indeed SCIM user by ID
- Create a Indeed SCIM user
- Update a Indeed SCIM user by ID
ElaichiToolsToolboxes
Every team gets its own Indeed SCIM toolbox.
Toolboxes are scoped per team, so HR and IT see different tools.
- HR Operations
- IT Helpdesk
- Identity and Access
- Talent Acquisition
ElaichiToolboxesShared connections
Teammates use Indeed SCIM without seeing credentials.
Each connection shows who connected it and how many teams and members share it.
- HR EMEA
- IT Helpdesk
- Identity and Access
- Talent Acquisition
ElaichiConnectionsAudit log
Every Indeed SCIM user change is on the record.
When, who, what happened, type and resource for each call, append only.
- 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 runs the whole joiner digest.
Fetch Indeed SCIM users, group them, draft a digest, approve, post back.
Indeed SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
Indeed 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
Indeed SCIM
Queued
Collections and dashboards
Indeed SCIM user numbers, counted not guessed.
Four metrics, 14 days of users created and a team breakdown, refreshed on schedule.
Indeed SCIM health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
User profiles
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
HR EMEA 34%
IT Helpdesk 27%
Identity and Access 21%
Talent Acquisition 18%
Related connectors
More from the catalog
FAQ
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 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.
Put Indeed SCIM in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.