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

Source: https://elaichi.ai/connectors/icims/

## Facts

| | |
| --- | --- |
| Application | ICIMS |
| Category | ATS |
| AI tools | 78 |
| 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 ICIMS is connected

- 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

## Connect ICIMS in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ICIMS.
2. Optionally set Share with, then press Connect.
3. Paste your ICIMS app credentials. ICIMS 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 ICIMS tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

## ICIMS 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 ICIMS 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 ICIMS 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 ICIMS through Elaichi

### Find a candidate by email after a referral

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

### Catch a candidate up after a phone screen

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

### Open a new job from a hiring brief

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

### See where a candidate sits in the process

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

### Keep client and vendor companies current

Recruiting ops. Look up a company in ICIMS by name or external ID and correct its address, contact or status when something changes, in one ask.

### Sort new hires into the right category

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

## 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. Endpoint: 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](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 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 my team share one ICIMS connection?

Yes. One person connects ICIMS in Elaichi and shares the connection with a team, so nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so every search and update in ICIMS is logged under their own name.

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

## All 78 ICIMS tools

Every tool below is callable through https://api.elaichi.ai/mcp once ICIMS is connected, subject to the toolbox it is in and the restrictions on the caller.

- **ICIMS customers get current** (Get). Get the connected iCIMS customer (platform) details: id, name, platform URL, customer type and build version.
- **Create a ICIMS person** (Create). Create a Person profile. Send folder plus the fields to set; the new profile URL (with its system ID) is returned in the Location header. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer.
- **Get single ICIMS person by ID** (Get). Get a Person profile by system ID. Only fields with values that the API user may see are returned. Required: id.
- **Update a ICIMS person by ID** (Update). Update a Person profile by system ID; send only the fields to change. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer. Required: id.
- **ICIMS people search** (Search). Search Person profiles and return matching system IDs (max 1,000 per call; page by adding an id &gt; last-id filter). Requires the Integration User group. Required: filters.
- **ICIMS people lookup by external ID** (Action). Find the system ID of a Person profile by exact external ID. Required: type, value.
- **ICIMS people get by email** (Get). Get a Person profile by email address. Required: email.
- **ICIMS people get workflows** (Get). List the workflow types (and links) a person profile is associated with, e.g. recruiting or onboarding workflows. Required: person_id.
- **Create a ICIMS job** (Create). Create a Job profile. Send folder plus the fields to set; the new profile URL (with its system ID) is returned in the Location header. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer.
- **Get single ICIMS job by ID** (Get). Get a Job profile by system ID. Only fields with values that the API user may see are returned. Required: id.
- **Update a ICIMS job by ID** (Update). Update a Job profile by system ID; send only the fields to change. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer. Required: id.
- **ICIMS jobs search** (Search). Search Job profiles and return matching system IDs (max 1,000 per call; page by adding an id &gt; last-id filter). Requires the Integration User group. Required: filters.
- **ICIMS jobs lookup by external ID** (Action). Find the system ID of a Job profile by exact external ID. Required: type, value.
- **Create a ICIMS company** (Create). Create a Location/Company profile. Send folder plus the fields to set; the new profile URL (with its system ID) is returned in the Location header. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer.
- **Get single ICIMS company by ID** (Get). Get a Location/Company profile by system ID. Only fields with values that the API user may see are returned. Required: id.
- **Update a ICIMS company by ID** (Update). Update a Location/Company profile by system ID; send only the fields to change. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer. Required: id.
- **ICIMS companies search** (Search). Search Location/Company profiles and return matching system IDs (max 1,000 per call; page by adding an id &gt; last-id filter). Requires the Integration User group. Required: filters.
- **ICIMS companies lookup by external ID** (Action). Find the system ID of a Location/Company profile by exact external ID. Required: type, value.
- **Create a ICIMS new hire category** (Create). Create a New Hire Category profile. Send folder plus the fields to set; the new profile URL (with its system ID) is returned in the Location header. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer.
- **Get single ICIMS new hire category by ID** (Get). Get a New Hire Category profile by system ID. Only fields with values that the API user may see are returned. Required: id.
- **Update a ICIMS new hire category by ID** (Update). Update a New Hire Category profile by system ID; send only the fields to change. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer. Required: id.
- **Create a ICIMS talent pool** (Create). Create a Talent Pool profile. Send folder plus the fields to set; the new profile URL (with its system ID) is returned in the Location header. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer.
- **Get single ICIMS talent pool by ID** (Get). Get a Talent Pool profile by system ID. Only fields with values that the API user may see are returned. Required: id.
- **Update a ICIMS talent pool by ID** (Update). Update a Talent Pool profile by system ID; send only the fields to change. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer. Required: id.
- **ICIMS talent pools search** (Search). Search Talent Pool profiles and return matching system IDs (max 1,000 per call; page by adding an id &gt; last-id filter). Requires the Integration User group. Required: filters.
- **Create a ICIMS room** (Create). Create a Room profile. Send folder plus the fields to set; the new profile URL (with its system ID) is returned in the Location header. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer.
- **Get single ICIMS room by ID** (Get). Get a Room profile by system ID. Only fields with values that the API user may see are returned. Required: id.
- **Update a ICIMS room by ID** (Update). Update a Room profile by system ID; send only the fields to change. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer. Required: id.
- **Create a ICIMS connect event** (Create). Create a Event profile. Send folder plus the fields to set; the new profile URL (with its system ID) is returned in the Location header. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer.
- **Get single ICIMS connect event by ID** (Get). Get a Event profile by system ID. Only fields with values that the API user may see are returned. Required: id.
- **Update a ICIMS connect event by ID** (Update). Update a Event profile by system ID; send only the fields to change. Custom fields are sent as field&lt;id&gt; (e.g. field17236); see schemas.get_profile_schema for the exact fields of this customer. Required: id.
- **Create a ICIMS applicant workflow** (Create). Create a Recruiting (applicant) workflow entry linking a base profile and an associated profile. Required: baseprofile, associatedprofile.
- **Get single ICIMS applicant workflow by ID** (Get). Get a Recruiting (applicant) workflow entry by workflow ID. Required: id.
- **Update a ICIMS applicant workflow by ID** (Update). Update a Recruiting (applicant) workflow entry (baseprofile and associatedprofile cannot change). Required: id.
- **Delete a ICIMS applicant workflow by ID** (Delete). Delete a Recruiting (applicant) workflow entry (unassociates the person from the job). Required: id.
- **ICIMS applicant workflows search** (Search). Search Recruiting (applicant) workflow entries and return matching workflow IDs (max 1,000 per call; page by id &gt; last-id). Required: filters.
- **ICIMS applicant workflows get by person and job** (Get). Get the recruiting workflow that links a person to a job. Required: person_id, job_id.
- **ICIMS applicant workflows update by person and job** (Update). Update the recruiting workflow that links a person to a job. Required: person_id, job_id.
- **Create a ICIMS source workflow** (Create). Create a Sourcing workflow entry linking a base profile and an associated profile. Required: baseprofile, associatedprofile.
- **Get single ICIMS source workflow by ID** (Get). Get a Sourcing workflow entry by workflow ID. Required: id.
- **Update a ICIMS source workflow by ID** (Update). Update a Sourcing workflow entry (baseprofile and associatedprofile cannot change). Required: id.
- **ICIMS source workflows search** (Search). Search Sourcing workflow entries and return matching workflow IDs (max 1,000 per call; page by id &gt; last-id). Required: filters.
- **Create a ICIMS onboard workflow** (Create). Create a Onboarding workflow entry linking a base profile and an associated profile. Required: baseprofile, associatedprofile.
- **Get single ICIMS onboard workflow by ID** (Get). Get a Onboarding workflow entry by workflow ID. Required: id.
- **Update a ICIMS onboard workflow by ID** (Update). Update a Onboarding workflow entry (baseprofile and associatedprofile cannot change). Required: id.
- **Create a ICIMS connect event workflow** (Create). Create a Event attendee workflow entry linking a base profile and an associated profile. Required: baseprofile, associatedprofile.
- **Get single ICIMS connect event workflow by ID** (Get). Get a Event attendee workflow entry by workflow ID. Required: id.
- **Update a ICIMS connect event workflow by ID** (Update). Update a Event attendee workflow entry (baseprofile and associatedprofile cannot change). Required: id.
- **ICIMS profile files download** (Download). Download the file stored in a File or Image field (e.g. a resume); returns the raw file. Required: profile_type, profile_id, field_id.
- **ICIMS profile files upload** (Upload). Upload or replace the file in a File field (multipart form part named after the field, e.g. resume). Required: profile_type, profile_id, field_id, file.
- ...and 28 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
