ICIMS MCP connector
The ICIMS connector lets Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client find, create and update candidates, jobs, companies and talent pools in ICIMS, with each person signed in as themselves and every call logged.
- App credentials
- Free 14-day trial
- No credit card
Find every open engineering job in ICIMS posted this month
Working in ICIMS with Elaichi
-
ICIMS customers get current
-
Get single ICIMS person by ID
-
ICIMS people search
How to connect ICIMS to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ICIMS MCP connector for 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.
ICIMS MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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.
ICIMS MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
ICIMS MCP connector for 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.
ICIMS MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect ICIMS 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.
What teams do with ICIMS through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ICIMS is logged.
-
Recruiting
Find a candidate by email after a referral
A colleague forwards a referral and you ask for the person in ICIMS by their email address. You get the record, their current applications and where each one stands, without opening a browser tab.
-
Recruiting
Catch a candidate up after a phone screen
Finish the call, type what changed, and the candidate's record in ICIMS is updated with the new phone number, location or notes you dictated.
-
Talent acquisition
Open a new job from a hiring brief
Paste the hiring manager's brief and have the job created in ICIMS with the title, location and details filled in, ready for review before it goes live.
-
Hiring managers
See where a candidate sits in the process
Ask which stage a candidate has reached for your opening and get their workflow from ICIMS in plain words, so you know whether to chase or wait.
-
Recruiting ops
Keep client and vendor companies current
Look up a company in ICIMS by name or external ID and correct its address, contact or status when something changes, in one ask.
-
Onboarding
Sort new hires into the right category
Set up a new hire category in ICIMS for the next intake and move accepted candidates into the right talent pool, so onboarding starts from a clean list.
Try asking
- “Find every open engineering job in ICIMS posted this month”
- “Which candidates for the account executive role are in interview stage?”
- “Add Maria Chen to the sales talent pool and update her email”
What connecting ICIMS gets you
6 screens from Elaichi, each doing one job for your ICIMS account.
Ask Elaichi to work across your apps.
Find every open engineering job in ICIMS posted this month
Which candidates for the account executive role are in interview stage?
Add Maria Chen to the sales talent pool and update her email
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask ICIMS a question, get a real answer.
Candidates, jobs and talent pools answered from live ICIMS records in plain language.
Copy the endpoint
AI apps
One endpoint for every client, no shared key.
Claude, ChatGPT and Cursor reach ICIMS through one governed endpoint, each person signed in.
Tool catalog
78 ICIMS tools ready, no code to write.
People, jobs, companies, talent pools and new hire categories, covered without custom code.
Toolboxes
Every team gets its own ICIMS toolbox.
Recruiters, hiring managers and onboarding each work from a toolbox scoped to them.
Shared connections
Share an ICIMS connection, never a credential.
One person connects ICIMS, teams work through it, nobody else sees the app credentials.
Audit log
Know who changed which ICIMS record, and when.
Every candidate update, job edit and search lands in an append-only log with a name.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
ICIMS digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
ICIMS
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 Jake Morgan
Approve Deny -
Post the digest
ICIMS
Queued
Workflows
A schedule starts the work, a person approves.
New ICIMS candidates are fetched, grouped, drafted into a digest, approved, then posted back to ICIMS.
ICIMS health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
Recruiting US 34%
Recruiting EMEA 27%
Talent acquisition 21%
Hiring managers 18%
Collections and dashboards
ICIMS hiring numbers, computed with no model involved.
Candidates and jobs created over 14 days, broken down by team, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ICIMS
All three can connect ICIMS 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ICIMS tools | Allow or restrict single ICIMS 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 ICIMS 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
ICIMS tools for your AI agents
78 tools are ready to call through Elaichi's MCP endpoint the moment you connect ICIMS, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect ICIMS to Claude?
Connect ICIMS in Elaichi first: enter the app credentials your ICIMS administrator gives you and the connection is live. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and ICIMS is available inside Claude.
Does ICIMS work with ChatGPT and Cursor as well as Claude?
Yes. Once ICIMS 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 ICIMS once and every client sees it.
What can an AI agent actually do with my ICIMS data?
An agent can find candidates in ICIMS by name, email or external ID, see which stage their applications are at, and update their records after a call. It can create and edit jobs, keep company records current, and set up new hire categories and talent pools. Short, concrete asks such as "find the ICIMS candidate with this email" work better than long paragraphs.
Does connecting ICIMS give the AI every candidate and job in our system?
No. Each person signs in to ICIMS as themselves, so an agent only sees the candidates, jobs and companies that person can already see in ICIMS. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in ICIMS?
Yes. Restrictions in Elaichi work per action, so you can allow searching candidates in ICIMS while restricting updates to jobs or companies, on a role or on one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an ICIMS connection when someone leaves?
Offboarding a person in Elaichi ends their access to ICIMS through every client at once. A shared ICIMS connection keeps working for everyone else on the team. If you ever want ICIMS gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the ICIMS MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ICIMS 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 ICIMS?
Yes. Both let Claude, ChatGPT or Cursor use ICIMS. 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 ICIMS call.
How is Elaichi different from Composio for ICIMS?
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 ICIMS: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ICIMS in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot