# NICE CXone MCP connector

The NICE CXone connector brings your contact center's address books, agent configuration, active supervisors and activity audit into Elaichi, so Claude, ChatGPT, Cursor and Microsoft Copilot can read and update them inside each person's own access.

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

## Facts

| | |
| --- | --- |
| Application | NICE CXone |
| Category | Voice |
| AI tools | 609 |
| Authentication | Connects with an API key |
| 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 NICE CXone is connected

- Which supervisors are active in NICE CXone right now?
- Add the new escalation line to the support address book.
- List agents not yet assigned to the sales address book.

## Connect NICE CXone in Elaichi

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

1. Open Connections, choose Add connection, and pick NICE CXone.
2. Optionally set Share with, then press Connect.
3. Paste a NICE CXone API key. One person generates a token in NICE CXone and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which NICE CXone tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

## NICE CXone 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`.

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

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

## NICE CXone 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 NICE CXone 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 NICE CXone 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 NICE CXone through Elaichi

### Keep the transfer directory current

Contact center operations. Add a new vendor line or escalation number to a NICE CXone address book, or retire an entry that no longer answers, without opening the admin console.

### Find the right transfer number fast

Support. Ask for the warm transfer number for billing or the after hours line and get it straight from the live NICE CXone address book.

### Check an agent's setup before a shift

Workforce management. Pull up an agent's configuration and client data to confirm they are set up the way the schedule expects, and fix a batch of agents in one pass.

### See who is supervising right now

Team leads. List the active supervisors on the floor so an escalation goes to someone who is actually online.

### Review who changed what

Compliance. Read the NICE CXone activity audit to find who updated a setting or an address book and when, then summarize it for a quarterly review.

### Manage access keys without a spreadsheet

IT. List the NICE CXone access keys in use, create one for a new system, and delete keys that should have been retired months ago.

## Elaichi vs Zapier MCP vs Composio for NICE CXone

All three can connect NICE CXone 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 NICE CXone tools | Allow or restrict single NICE CXone 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 NICE CXone 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 NICE CXone to Claude?

Connect NICE CXone in Elaichi first, then paste the endpoint https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. NICE CXone connects with an API key, so the sign-in step is pasting the key from your NICE CXone account into Elaichi. There is no OAuth application to register and no client ID or secret to generate.

### Does NICE CXone work with ChatGPT and Cursor as well as Claude?

Yes. Once NICE CXone 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 NICE CXone once and every client sees it.

### What can an AI agent actually do with my NICE CXone data?

An agent can look up and update NICE CXone address books and their entries, see which agents are assigned to each book, read an agent's configuration and client data, list the supervisors who are active right now, read the activity audit, and manage access keys. Ask for one thing at a time, such as the escalation number for billing or the agents not yet assigned to the sales address book. Short concrete asks work better than long sentences.

### Does connecting NICE CXone give the AI access to everything in my contact center?

No. Every call to NICE CXone runs as the person who signed in, so an agent sees only the address books, agents and settings that person could already see in NICE CXone. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

### Can my team share one NICE CXone connection?

Yes. One person connects NICE CXone with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to an address book or agent setting.

### Can I stop an agent from deleting or changing things in NICE CXone?

Yes. Restrictions in Elaichi work per action, so you can allow reading NICE CXone address books while restricting deleting entries or updating agent configuration, and you can set that on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a NICE CXone connection when someone leaves?

Offboarding that person in Elaichi ends their access to NICE CXone through every client at once. A shared NICE CXone connection keeps working for everyone else on the team. If you ever want it gone entirely, disconnecting NICE CXone once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

Yes. NICE CXone 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 NICE CXone?

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

### How is Elaichi different from Composio for NICE CXone?

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

## All 609 NICE CXone tools

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

- **List all NICE CXone access keys** (List). Returns a list of access keys. This method will return a list of â€œaccessKeyIdsâ€ and the agentId who can use it.It can be filter by adding â€œagentIdâ€ or paging parameters to the request. Required: agentId.
- **Create a NICE CXone access key** (Create). Creates an accessKey. This method will create an accessKey for an agentId. Response will provide the public accessKeyId and the private accessKeySecret. Those parameters will can then be used to request a token.
- **Get single NICE CXone access key by ID** (Get). Returns the configuration of an accessKey. This method will return the configuration of an accessKey. NOTE: The Access Key APIs in this section are only to be used with Central. Required: id.
- **Update a NICE CXone access key by ID** (Update). Updates an accessKey by Id. This method updates an access keys configuration of â€œisActiveâ€ to true or false.AgentIds can only have 20 active or inactive accessKeys configured. Required: id.
- **Delete a NICE CXone access key by ID** (Delete). Deletes an accessKey. This method will delete an accessKey configured for an agent.The maximum number of configured access keys for and agentId is 20.That includes active and inactive access keys. Required: id.
- **List all NICE CXone activesupervisors** (List). Returns Active supervisors status. This method will return all active supervisors status based on Teamid selected.
- **List all NICE CXone activity audit** (List). New in 26.3: Retrieve activity audit events. Returns a paginated list of activity audit events for the authenticated tenant within the specified date range.
- **List all NICE CXone address book agents assigned** (List). Lists all assigned agents for an address book. This method returns assigned agents for an address book Required: address_book_id.
- **List all NICE CXone address book agents unassigned** (List). Lists all unassigned agents for an address book. This method returns unassigned agents for an address book Required: address_book_id.
- **List all NICE CXone address book dynamic entries** (List). Lists all dynamic address book entries for an address book. This method returns all of the entries in the Address Book identified by addressBookId.This method utilizes a set of parameters that allow you to paginate the results of… Required: address_book_id, fullLoad.
- **NICE CXone address book dynamic entries bulk update** (Update). Create or Update Dynamic Address Book Entries. This method allows you to create or update entries in a Dynamic Address Book identified by addressBookId. Required: address_book_id, fullLoad, addressBookEntries.
- **Delete a NICE CXone address book dynamic entry by ID** (Delete). Delete a Dynamic Address Book Entry. This method allows you to delete an entry identified by externalId in a Dynamic Address Book identified by addressBookId. Required: id, address_book_id.
- **List all NICE CXone address book entries** (List). Lists all standard address book entries for an address book. This method returns all of the entries in the Standard Address Book identified by addressBookId. Required: address_book_id.
- **Create a NICE CXone address book entry** (Create). Create Standard Address Book Entries. This method allows you to create new address book entries and associate them with a single address book identified by addressBookId. Required: address_book_id, addressBookEntries.
- **NICE CXone address book entries bulk update** (Update). Update Standard Address Book Entries. This method allows you to update existing address book entries associated with a single address book identified by addressBookId. Required: address_book_id, addressBookEntries.
- **Delete a NICE CXone address book entry by ID** (Delete). Delete a Standard Address Book Entry. This method allows you to delete a single address book entry from an address book using the addressBookId and addressBookEntryId. Required: id, address_book_id.
- **List all NICE CXone address books** (List). Returns a list of Address Books. This method returns a list of Address books for the Business Unit.
- **Create a NICE CXone address book** (Create). Create a new Address Book. This method allows you to create an Address Book. Required: addressBookName, addressBookType.
- **Delete a NICE CXone address book by ID** (Delete). Delete an existing Address Book. This method allows you to delete an existing Address Book specified by addressBookId. Required: id.
- **NICE CXone address books assign** (Assign). Assign Entities to an Address Book. This method allows you to assign an Address Book specified by addressBookId to one set of entities such as Agents, Teams, Skills or Campaigns exclusively, which means the Address Book can only… Required: address_book_id, entityType, addressBookAssignments.
- **List all NICE CXone agent address books** (List). Returns Address Books for an Agent. This method returns a list of Address Books currently assigned to the Agent identified by agentId. Address Books are assigned to Agents, Teams, Skills or Campaigns exclusively (i.e. Required: agent_id, includeEntries, addressBookType.
- **List all NICE CXone agent client data** (List). Gets a JSON object client data.
- **NICE CXone agent client data bulk update** (Update). Updates or inserts a clientData record.
- **List all NICE CXone agent configuration** (List). Returns agent configuration details for an agent with generic properties. This method returns agent configuration and settings related information. Required: agent_id.
- **List all NICE CXone agent groups** (List). Returns a list of groups an agent is assigned. This method returns a list of groups an agent is assigned. Required: agent_id.
- **List all NICE CXone agent indicators** (List). Returns an Agent Indicator List. This method will return all indicators currently queued for the agent specified by agentId. Required: agent_id.
- **List all NICE CXone agent interaction history** (List). Returns Contact history for all Agents. This method returns information on the contacts that the Agents were involved in between the dates specified, or since the ISO 8601 date/time provided in updatedSince parameter.
- **List all NICE CXone agent interaction history by agent** (List). Returns Contact history for an Agent. This method takes an agentId as input and will return back information on the contacts that Agent was involved in between the dates specified, or since the ISO 8601 date/time provided in… Required: agent_id, startDate, endDate, mediaTypeId.
- **List all NICE CXone agent interaction recent** (List). Returns info on Recent Contacts. This method returns information for all outbound phone contacts handled by the Agent identified by agentId over the reporting period specified by startDate and endDate. Required: agent_id, startDate, endDate.
- **List all NICE CXone agent login history** (List). Returns State duration for an Agent. This method will return the list of unique logins for the Agent identified by "agentId" within the period defined by "startDate" and "endDate" or return all of the logins if no reporting period… Required: agent_id, startDate, endDate.
- **Create a NICE CXone agent message** (Create). Create an Agent message. This method creates, configures and assigns agent messages. Required: agentMessages.
- **Get single NICE CXone agent message by ID** (Get). Lists agent group messages. This method returns agent group messages Required: id.
- **Delete a NICE CXone agent message by ID** (Delete). Delete agent message. This method deletes an Agent message. Required: id.
- **List all NICE CXone agent messages** (List). Returns an Agent Message List. This method will return all messages currently queued for the agent specified by agentId. Required: agent_id.
- **List all NICE CXone agent patterns** (List). Returns Agent Dialing patterns. This method will return a list of all possible Agent Dialing patterns that can be used for an Agent.
- **NICE CXone agent patterns transform phonenumbers** (Action). Transform Input Number. This Method takes Multiple Input Number and a dialing pattern set id which is a set of multiple dialing patterns. Required: agentpattern_id.
- **List all NICE CXone agent performance** (List). Returns a performance summary of all Agents. This method returns a per-agent summary for all Agents in the business unit over the time frame between "startDate" and "endDate".The date fields require quarter hour time stamps. Required: startDate, endDate.
- **List all NICE CXone agent performance by agent** (List). Returns performance summary for a specific agent. This method returns a summary for the Agent specified over the time frame between "startDate" and "endDate".The date fields require quarter hour time stamps. Required: agent_id, startDate, endDate.
- **List all NICE CXone agent profile configurations** (List). Returns Assignable Configurations for an Agent Profile. This method return agent profiles configurations which is a list of settings that you can see on agent profiles UI.
- **NICE CXone agent profile teams search** (Search). Returns all the team details. This method returns details of the teams for a particular tenant and their mapping to desktop profile if any.
- **List all NICE CXone agent profile teams** (List). Get Teams assigned to an Agent Profile. This method fetches the team details of teams assigned to desktop profile. Required: profile_id.
- **Create a NICE CXone agent profile team** (Create). Assigs team to an Agent Profile. This method assigns teams to DesktopProfiles based on the unique desktop profile id provided. Required: profile_id.
- **NICE CXone agent profile teams bulk delete** (Delete). Removes the assigned team(s) to an Agent Profile. This method removes the assigned teams to desktop profiles based on the unique desktop profile id provided Required: profile_id.
- **List all NICE CXone agent profiles** (List). Returns all Desktop Profiles. This method returns a list of desktop profiles for the tenant. This method also supports pagination parameters and gives the list as per the parameters provided.
- **Create a NICE CXone agent profile** (Create). To create a new agent profile. This method creates a new desktop profile with profile name, description and list of configurations and their values
- **NICE CXone agent profiles search** (Search). Returns all Agent Profiles for the search filters provided. This method returns a list of desktop profiles for the tenant.
- **NICE CXone agent profiles update status** (Update). To update the status of agent profile. This method updates status of existing desktop profile with new status for mentioned id.
- **Get single NICE CXone agent profile by ID** (Get). To get agent profile details by ID. This method returns details of a particular desktop profile for the tenant based on the unique agent profile id provided. Required: id.
- **Update a NICE CXone agent profile by ID** (Update). To update a agent profile. This method updates an existing desktop profile with profile name, description and list of configurations and their values for the desktop profile with mentioned id Required: id.
- **List all NICE CXone agent profiles assigned** (List). Returns agent profile details for CMA. This method returns a agent profile for the team to which the agent belongs.
- ...and 559 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
