# Ivanti ITSM MCP connector

The Ivanti ITSM connector brings incidents, service requests, changes and problems into Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent, so each person can find, create and update tickets inside their own Ivanti ITSM access.

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

## Facts

| | |
| --- | --- |
| Application | Ivanti ITSM |
| Category | Ticketing |
| AI tools | 57 |
| 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 Ivanti ITSM is connected

- Show me open priority 1 incidents assigned to the network team
- Create a service request for a new laptop for Priya Shah
- Which changes are scheduled for this weekend's maintenance window?

## Connect Ivanti ITSM in Elaichi

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

1. Open Connections, choose Add connection, and pick Ivanti ITSM.
2. Optionally set Share with, then press Connect.
3. Paste an Ivanti ITSM API key. One person generates a token in Ivanti ITSM 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 Ivanti ITSM tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

## Ivanti ITSM 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`.

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

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

## Ivanti ITSM 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 Ivanti ITSM 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 Ivanti ITSM 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 Ivanti ITSM through Elaichi

### Log an incident while the caller is still talking

Service desk. Describe the problem in plain words and a new Ivanti ITSM incident is created with the right caller, category and priority. Catch the record up with notes after the call ends.

### Find what is already open before raising another

Service desk. Ask for open incidents from the same person or about the same service and see them in one list. Update the existing ticket instead of creating a duplicate.

### Draft a change request with the details in place

Change management. Turn a maintenance plan into an Ivanti ITSM change with the schedule, scope and affected services filled in. Update it as the approval moves along.

### Open a problem from a run of related incidents

Problem management. Pull the incidents that keep coming back about the same service and raise a problem record that links the pattern together.

### Submit onboarding requests without opening the portal

HR. Ask for a laptop, accounts and building access for a new starter and the service requests are created in Ivanti ITSM. Check their status by asking.

### Keep the queue honest at the end of the day

Facilities. List the service requests still waiting on your team, update the ones that are done and leave a note on the ones that are stuck.

## Elaichi vs Zapier MCP vs Composio for Ivanti ITSM

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

Connect Ivanti ITSM in Elaichi first by pasting in the API key from your Ivanti ITSM tenant, which is the whole sign-in step. 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 https://api.elaichi.ai/mcp as the endpoint. Claude signs you in to Elaichi and Ivanti ITSM is ready to use.

### Does Ivanti ITSM work with ChatGPT and Cursor as well as Claude?

Yes. Once Ivanti ITSM 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 Ivanti ITSM once and every client picks it up.

### What can an AI agent actually do with my Ivanti ITSM data?

It can list and look up incidents, service requests, changes and problems, create new ones, update the ones you point it at and, where allowed, delete incidents, service requests and changes. In practice that means asking for the open incidents on a service, logging a ticket from a description, or moving a change along after a decision. Short, concrete asks such as naming the ticket number and the field to update work better than long paragraphs.

### Does connecting Ivanti ITSM give the AI access to everything in my tenant?

No. Every call to Ivanti ITSM runs as the person who signed in to Elaichi, so an agent sees the incidents, requests, changes and problems that person can already see. Elaichi can narrow that access further with roles and restrictions, and it never widens it beyond what Ivanti ITSM already allows.

### Can my team share one Ivanti ITSM connection?

Yes. One person connects Ivanti ITSM in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created or changed each ticket.

### Can I stop an agent from deleting or changing things in Ivanti ITSM?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting incidents, closing changes or editing problems for a role or for one person while leaving lookups and creation available. A restricted Ivanti ITSM 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 Ivanti ITSM connection when someone leaves?

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

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

Yes. Ivanti ITSM 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 Ivanti ITSM?

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

### How is Elaichi different from Composio for Ivanti ITSM?

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

## All 57 Ivanti ITSM tools

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

- **List all Ivanti ITSM business objects** (List). List records of any business object, including custom objects (GET /api/odata/businessobject/{business_object}). Supports OData filter, orderby, select and search. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only. Required: business_object.
- **Get single Ivanti ITSM business object by ID** (Get). Get one record of any business object by RecId (32-character record ID). Required: business_object, id.
- **Create a Ivanti ITSM business object** (Create). Create a record of any business object, including custom and group objects (e.g. Journal__Notess). Send the field values as the JSON body. Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: business_object.
- **Update a Ivanti ITSM business object by ID** (Update). Update fields of a record of any business object (HTTP PATCH; only sent fields change). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: business_object, id (RecId).
- **Delete a Ivanti ITSM business object by ID** (Delete). Delete a record of any business object by RecId. Permanent; returns 204. Required: business_object, id.
- **List all Ivanti ITSM business objects v 2** (List). List records of any business object with the Rest API V2 endpoint (/api/odatav2/businessobject/{business_object}), which adds nested filter groups with brackets, e.g. FirstName eq 'Allen' and (LastName eq 'Davis' or LastName eq 'Cope'). Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only. Required: business_object.
- **List all Ivanti ITSM incidents** (List). List incident records (ITSM object Incident, /api/odata/businessobject/incidents), optionally filtered, sorted, searched or trimmed to selected fields. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only.
- **Get single Ivanti ITSM incident by ID** (Get). Get one incident record by RecId (the 32-character record ID, not the incident number; find it with incidents.list and filter). Required: id.
- **Create a Ivanti ITSM incident** (Create). Create a incident record. Typical fields: Subject, Symptom, ProfileLink_RecID (customer employee RecId), Category, Service, Impact, Urgency, Source, Owner, OwnerTeam, Status (Logged). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Returns the created record with its RecId.
- **Update a Ivanti ITSM incident by ID** (Update). Update fields of a incident record (HTTP PATCH; only the fields sent are changed). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: id (RecId).
- **Delete a Ivanti ITSM incident by ID** (Delete). Delete a incident record by RecId. Permanent; returns 204. Required: id.
- **List all Ivanti ITSM service requests** (List). List service request records (ITSM object ServiceReq, /api/odata/businessobject/ServiceReqs), optionally filtered, sorted, searched or trimmed to selected fields. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only.
- **Get single Ivanti ITSM service request by ID** (Get). Get one service request record by RecId (the 32-character record ID, not the service request number; find it with service_requests.list and filter). Required: id.
- **Create a Ivanti ITSM service request** (Create). Create a service request record. Creating a ServiceReq record directly skips the Service Catalog form; to submit a catalog request with its parameters use service_request_submissions.create. Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Returns the created record with its RecId.
- **Update a Ivanti ITSM service request by ID** (Update). Update fields of a service request record (HTTP PATCH; only the fields sent are changed). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: id (RecId).
- **Delete a Ivanti ITSM service request by ID** (Delete). Delete a service request record by RecId. Permanent; returns 204. Required: id.
- **List all Ivanti ITSM changes** (List). List change records (ITSM object Change, /api/odata/businessobject/changes), optionally filtered, sorted, searched or trimmed to selected fields. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only.
- **Get single Ivanti ITSM change by ID** (Get). Get one change record by RecId (the 32-character record ID, not the change number; find it with changes.list and filter). Required: id.
- **Create a Ivanti ITSM change** (Create). Create a change record. Typical fields (official example): Subject, Description, Category, TypeOfChange (Minor), Status (Logged), RequestorLink_RecID, Owner, Owner_Valid, OwnerTeam, OwnerTeam_Valid, CreatedBy. Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Returns the created record with its RecId.
- **Update a Ivanti ITSM change by ID** (Update). Update fields of a change record (HTTP PATCH; only the fields sent are changed). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: id (RecId).
- **Delete a Ivanti ITSM change by ID** (Delete). Delete a change record by RecId. Permanent; returns 204. Required: id.
- **List all Ivanti ITSM problems** (List). List problem records (ITSM object Problem, /api/odata/businessobject/problems), optionally filtered, sorted, searched or trimmed to selected fields. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only.
- **Get single Ivanti ITSM problem by ID** (Get). Get one problem record by RecId (the 32-character record ID, not the problem number; find it with problems.list and filter). Required: id.
- **Create a Ivanti ITSM problem** (Create). Create a problem record. Typical fields: Subject, Description, Category, Service, Priority, Owner, OwnerTeam. Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Returns the created record with its RecId.
- **Update a Ivanti ITSM problem by ID** (Update). Update fields of a problem record (HTTP PATCH; only the fields sent are changed). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: id (RecId).
- **Delete a Ivanti ITSM problem by ID** (Delete). Delete a problem record by RecId. Permanent; returns 204. Required: id.
- **List all Ivanti ITSM tasks** (List). List task (assignment) records (ITSM object Task#Assignment, /api/odata/businessobject/tasks), optionally filtered, sorted, searched or trimmed to selected fields. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only.
- **Get single Ivanti ITSM task by ID** (Get). Get one task (assignment) record by RecId (the 32-character record ID, not the task (assignment) number; find it with tasks.list and filter). Required: id.
- **Create a Ivanti ITSM task** (Create). Create a task (assignment) record. Send the Task#Assignment fields (names from business_object_metadata.list with business_object tasks); most tasks are created and moved by quick actions (record_actions.create, e.g. Accept_Task). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Returns the created record with its RecId.
- **Update a Ivanti ITSM task by ID** (Update). Update fields of a task (assignment) record (HTTP PATCH; only the fields sent are changed). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: id (RecId).
- **Delete a Ivanti ITSM task by ID** (Delete). Delete a task (assignment) record by RecId. Permanent; returns 204. Required: id.
- **List all Ivanti ITSM employees** (List). List employee records (ITSM object Employee, /api/odata/businessobject/employees), optionally filtered, sorted, searched or trimmed to selected fields. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only.
- **Get single Ivanti ITSM employee by ID** (Get). Get one employee record by RecId (the 32-character record ID, not the employee number; find it with employees.list and filter). Required: id.
- **Create a Ivanti ITSM employee** (Create). Create a employee record. Send the Employee object's fields (names from business_object_metadata.list with business_object employees). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Returns the created record with its RecId.
- **Update a Ivanti ITSM employee by ID** (Update). Update fields of a employee record (HTTP PATCH; only the fields sent are changed). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: id (RecId).
- **Delete a Ivanti ITSM employee by ID** (Delete). Delete a employee record by RecId. Permanent; returns 204. Required: id.
- **List all Ivanti ITSM journal notes** (List). List journal note records (ITSM object Journal#Notes, /api/odata/businessobject/Journal__Notess), optionally filtered, sorted, searched or trimmed to selected fields. Pages with $top/$skip (default 25, maximum 100 records per page); the newest created or modified records come first. The response's @odata.count is the total number of matching records. Read-only.
- **Get single Ivanti ITSM journal note by ID** (Get). Get one journal note record by RecId (the 32-character record ID, not the journal note number; find it with journal_notes.list and filter). Required: id.
- **Create a Ivanti ITSM journal note** (Create). Create a journal note record. Typical fields: Subject, NotesBody, Category, Source. Link the note to a record with related_business_objects.create (e.g. relationship IncidentContainsJournal). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Returns the created record with its RecId.
- **Update a Ivanti ITSM journal note by ID** (Update). Update fields of a journal note record (HTTP PATCH; only the fields sent are changed). Validated list fields accept the display value (Status, Owner, OwnerTeam, ...) and optionally the matching &lt;Field&gt;_Valid RecId; field names are case-sensitive and must exist on the object (see business_object_metadata.list). Required: id (RecId).
- **Delete a Ivanti ITSM journal note by ID** (Delete). Delete a journal note record by RecId. Permanent; returns 204. Required: id.
- **List all Ivanti ITSM business object metadata** (List). Get the OData metadata (XML, EDMX) of a business object: its fields (Property), relationships (NavigationProperty — names to use with related_business_objects), templates and quick actions (Action — names and action IDs for record_actions.create) and saved searches (Function — names and IDs for saved_search_results.list). Read-only. Required: business_object.
- **List all Ivanti ITSM related business objects** (List). List records linked to a record through a relationship (e.g. the journals of an incident: business_object incidents, relationship IncidentContainsJournal). Read-only. Required: business_object, record_id, relationship.
- **Create a Ivanti ITSM related business object** (Create). Link an existing record to a record through a relationship (e.g. link journal 4F34... to incident 8716... via IncidentContainsJournal). Returns code ISM_2000 'Successfully Created the link'. Required: business_object, record_id, relationship, related_record_id.
- **Delete a Ivanti ITSM related business object by ID** (Delete). Unlink a related record from a record (removes the relationship link, not the record). Returns 204. Required: business_object, record_id, relationship, id (RecId of the linked record).
- **List all Ivanti ITSM saved search results** (List). Run a saved search on a business object and return its records (e.g. incidents saved search My_Active). Get saved search names and action IDs from business_object_metadata.list (Function elements). Read-only. Required: business_object, saved_search_name, action_id.
- **List all Ivanti ITSM fulltext search results** (List). Full-text keyword search in one business object type (POST /api/rest/search/fulltext). Returns matching records with their key fields and RecId. Read-only. Required: Text, ObjectType.
- **List all Ivanti ITSM search results** (List). Global keyword search across the business objects enabled in the tenant's search configuration (knowledge articles, incidents, service offerings, ...). Read-only. Required: Text.
- **Create a Ivanti ITSM record action** (Create). Run a quick action or apply a template on a record. Quick actions: e.g. Close_Incident or Assign_Incident on an incident, Accept_Task on a task. Templates fill fields from a saved template, e.g. Backup_Failure on an incident. Get the action or template name and its ActionId from business_object_metadata.list (Action elements). Required: business_object, record_id, action_name, ActionId.
- **Create a Ivanti ITSM attachment** (Create). Upload one or more files and attach them to a record (multipart form-data: ObjectID, ObjectType and file parts). MCP clients cannot send file parts; use the proxy API with multipart. Required: ObjectID, ObjectType.
- ...and 7 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
