Skip to content

HaloITSM MCP connector

Connecting HaloITSM to Elaichi lets Claude, ChatGPT, Cursor, or any MCP client look up tickets, assets, users, agents, and appointments in HaloITSM, add actions to them, and book work, all inside each person's own HaloITSM access with every call logged.

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

How to connect

How to connect HaloITSM to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect HaloITSM once

  1. Open Connections, choose Add connection, and pick HaloITSM.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste your HaloITSM app credentials. HaloITSM 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.

haloitsm
HaloITSM
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
2

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.

HaloITSM MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

HaloITSM MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

HaloITSM MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 HaloITSM to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 HaloITSM through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Service desk

    Catch a ticket up after a call

    Once the phone call ends, ask the assistant to add an action to the HaloITSM ticket with what was agreed, so the record is current before the next request comes in.

  • Support

    See who is on which team

    Ask which HaloITSM agents sit on the network team, or pull up a single agent's details, without leaving the chat where you are already planning the shift.

  • IT asset management

    Register a new laptop as an asset

    When kit arrives, describe the device in plain language and have it created as a HaloITSM asset, then look it up later by ID when a ticket mentions it.

  • Field services

    Book the site visit while talking

    Ask the assistant to create a HaloITSM appointment for the engineer, or list the appointments already in the diary for tomorrow, so double bookings are caught early.

  • People operations

    Set up a new starter in HaloITSM

    On day one, ask to create the new hire as a HaloITSM user and confirm which team they belong to, so their first request is not stuck on a missing account.

  • IT management

    Review the HaloITSM setup at a glance

    List all HaloITSM teams, agents, and users in one place to spot leavers still active, empty teams, or agents who need reassigning, then tidy up from the same conversation.

Try asking

  • “Show tickets opened this week by team.”
  • “Which HaloITSM agents have the most open actions?”
  • “List users added to the service desk team.”

See all 84 HaloITSM tools below

Compare

Elaichi vs Zapier MCP vs Composio for HaloITSM

All three can connect HaloITSM to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for HaloITSM, by what to check
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 HaloITSM tools Allow or restrict single HaloITSM 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 HaloITSM 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 $15 per user per month. 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.

AI tools

HaloITSM tools for your AI agents

84 tools are ready to call through Elaichi's MCP endpoint the moment you connect HaloITSM, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting HaloITSM gets you

6 screens from the product, each doing one job for your HaloITSM account.

The agent

Ask in plain language, read live HaloITSM.

Answers come from live HaloITSM tickets, actions, agents and teams, not stale exports.

  • tickets
  • actions
  • agents
  • users

Ask Elaichi to work across your apps.

Show tickets opened this week by team.

Which HaloITSM agents have the most open actions?

List users added to the service desk team.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach HaloITSM.

One governed org endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

84 HaloITSM tools ready to call.

Users, teams, agents and actions covered by name, with no custom code written.

  • List all HaloITSM users
  • Get single HaloITSM user by ID
  • Create a HaloITSM user
  • Delete a HaloITSM user by ID
ElaichiTools
Tool Action Description
List all HaloITSM users List List users in HaloITSM. Returns count and an array of user objects with key details such as name, email, and status.
Get single HaloITSM user by ID Get Get details of a specific user in HaloITSM using id. Returns fields such as id, name, emailaddress, site_name, department, and related contact information.
Create a HaloITSM user Create Create or update one or more users in HaloITSM. If id is included, the user record is updated; if not, a new user is created. Returns key user fields including id, name, emailaddress, site_name, department, and lastlogindate.
Delete a HaloITSM user by ID Delete Delete a user in HaloITSM using id. Also removes related objects associated with the specified user. Returns status 200 upon successful deletion.
List all HaloITSM teams List List teams in HaloITSM. Returns an array of teams with key details such as team name, type, and membership-related information.

Toolboxes

Every team gets its own HaloITSM toolbox.

Service desk, change and reporting each see the HaloITSM tools their work needs.

  • Service desk
  • Incident management
  • Change and release
  • Asset management
ElaichiToolboxes
Name Source template Tools Created

Service desk toolbox

HaloITSM · tickets and actions

HaloITSM starter 18 Mar 4, 2026

Incident management toolbox

HaloITSM · major incidents and escalations

— 9 Mar 2, 2026

Change and release toolbox

HaloITSM · change requests and approvals

— 24 Feb 27, 2026

Asset management toolbox

HaloITSM · assets and configuration items

HaloITSM starter 6 Feb 19, 2026

IT operations toolbox

HaloITSM · agents, teams and queues

— 31 Jan 30, 2026

Reporting toolbox

HaloITSM · SLA and volume reporting

— 12 Jan 22, 2026

Shared connections

Share a HaloITSM connection, never the credential.

See who connected each account and how many teams and members use it.

  • Service desk EMEA
  • Incident response
  • Change board
  • Asset team
ElaichiConnections
Connection Scope Status Access
HA

HaloITSM (Service desk EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
HA

HaloITSM (Incident response)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
HA

HaloITSM (Change board)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
HA

HaloITSM (Asset team)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
HA

HaloITSM (Field support)

Connected by Ryan Hayes

Personal • Active Not shared
HA

HaloITSM (Reporting)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Answer who touched which HaloITSM ticket.

Append-only rows record when, who, what happened, type and resource on every call.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

HaloITSM Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

HaloITSM Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

HaloITSM Tickets List Toolbox

Launching 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 fires, HaloITSM work gets done.

Fetch actions, group them, draft a digest, a person approves, post to HaloITSM.

HaloITSM digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch tickets

    HaloITSM

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    HaloITSM

    Queued

Collections and dashboards

HaloITSM health numbers arrive on schedule.

Four metrics, 14 days of tickets created, split by team, computed without a model.

HaloITSM health

Refreshed 4 minutes ago · every 15 minutes · from the tickets collection

Live

Tickets

1,284 ↓ 12%

Actions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Tickets created

Last 14 days

By team

Share of activity

Service desk EMEA 34%

Incident response 27%

Change board 21%

Asset team 18%

FAQ

Frequently asked questions

How do I connect HaloITSM to Claude?

Two steps. In Elaichi, choose HaloITSM and enter your HaloITSM app credentials when asked, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no client ID or secret to generate, and no OAuth application to register on the HaloITSM side.

Does HaloITSM work with ChatGPT and Cursor as well as Claude?

Yes. Once HaloITSM is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect HaloITSM once and use it from whichever client you happen to be in.

What can an AI agent actually do with my HaloITSM data?

With HaloITSM connected, an assistant can look up users, agents, teams, assets, appointments, and actions in HaloITSM by name or ID, list them, and create new ones, such as adding an action to a ticket, booking an appointment for an engineer, or registering a new asset. It can also remove records where your HaloITSM access allows it. Because HaloITSM offers a lot of options, short concrete asks like "list open appointments for tomorrow" work better than long paragraphs.

Does connecting HaloITSM give the AI everything in my helpdesk?

No. Every request runs as the person who signed in to HaloITSM, so the assistant sees only the tickets, assets, and users that person can already see in HaloITSM. Elaichi can narrow that further for a team or a role, but it never grants anything HaloITSM itself would not allow.

Can my team share one HaloITSM connection?

Yes. One person connects HaloITSM in Elaichi and shares it with a team, and nobody else has to handle the HaloITSM app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every HaloITSM lookup or change.

Can I stop an agent from deleting or changing things in HaloITSM?

Yes. In Elaichi you can restrict individual HaloITSM actions, for example allowing lookups of assets and appointments while blocking deletion of users or agents. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt, however worded, can reach it.

What happens to a HaloITSM connection when someone leaves?

Offboarding a person in Elaichi ends their access to HaloITSM through every client at once. If they had shared a HaloITSM connection with the team, it keeps working for everyone else. Disconnecting HaloITSM once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.

Does the HaloITSM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. HaloITSM 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, 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 HaloITSM?

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

How is Elaichi different from Composio for HaloITSM?

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

Put HaloITSM in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.