Helpdesk
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.
In Elaichi
Connect HaloITSM once
-
Open Connections, choose Add connection, and pick HaloITSM.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect HaloITSM to 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.
Connect HaloITSM to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect HaloITSM to 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.
Connect HaloITSM 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.
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.”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
HaloITSM
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 Michael Brennan
Approve Deny -
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
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%
Related connectors
More from the catalog
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 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.
Put HaloITSM in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.