BMC Helix MCP connector
The BMC Helix connector brings incidents, companies, worklogs, support groups and tasks into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can read and update them as the person who signed in.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me open incidents for Acme assigned to the network support group
Working in BMC Helix with Elaichi
-
List all BMC Helix incident
-
Get single BMC Helix incident by ID
-
List all BMC Helix company
How to connect BMC Helix to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
BMC Helix MCP connector for 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.
BMC Helix MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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.
BMC Helix MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
BMC Helix MCP connector for 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.
BMC Helix MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect BMC Helix 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.
What teams do with BMC Helix through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in BMC Helix is logged.
-
Service desk
Log an incident while the caller is on the line
Describe the problem in plain words and a new BMC Helix incident is created with the company, the summary and the right support group filled in before the call ends.
-
IT operations
Catch the incident up after the fix
Once the server is back, ask for the incident to be updated and a worklog added with what was done, without opening BMC Helix and clicking through the form.
-
Support
See every open incident for one customer
Before a review call, pull the list of open BMC Helix incidents for that company, who owns each one and how long it has been sitting.
-
Service desk
Add a worklog in one sentence
Type the update you would have written in the ticket and it lands as a worklog on the right incident, with the timestamp and your name.
-
IT operations
Keep support groups current
Create a new support group when a team is formed, or update the existing one when it is renamed, and check which groups exist today.
-
Facilities
Check what tasks are still outstanding
Ask which tasks on an incident are still open, then mark the one you finished as done so the incident can be closed.
Try asking
- “Show me open incidents for Acme assigned to the network support group”
- “Add a worklog to incident INC0042 saying the server was rebooted”
- “Which tasks on the email outage incident are still open?”
What connecting BMC Helix gets you
6 screens from Elaichi, each doing one job for your BMC Helix account.
Ask Elaichi to work across your apps.
Show me open incidents for Acme assigned to the network support group
Add a worklog to incident INC0042 saying the server was rebooted
Which tasks on the email outage incident are still open?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about incidents in plain language.
Ask the Elaichi Agent about open BMC Helix incidents, worklogs and tasks, and get live answers.
Copy the endpoint
AI apps
One endpoint for every client you use.
Claude, ChatGPT and Cursor reach BMC Helix through one governed endpoint, no SDK, no shared key.
Tool catalog
67 BMC Helix tools, no code needed.
Incidents, companies, worklogs, support groups and tasks, ready the moment you connect.
Toolboxes
Every team gets its own toolbox.
Scope a toolbox to the service desk, another to IT operations, each with what they need.
Shared connections
Share the connection, never the API key.
One person connects BMC Helix, teams work through it, and nobody else sees a credential.
Audit log
Know who changed which incident, and when.
Every BMC Helix call lands in an append-only log with who, what and which record.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
BMC Helix digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch incidents
BMC Helix
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 Jake Morgan
Approve Deny -
Post the digest
BMC Helix
Queued
Workflows
A schedule starts the work, you approve it.
Open incidents are fetched, grouped, drafted into a digest, approved, then posted to BMC Helix.
BMC Helix health
Refreshed 4 minutes ago · every 15 minutes · from the incidents collection
Incidents
1,284 ↓ 12%
Companies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Incidents created
Last 14 days
By team
Share of activity
Service desk 34%
IT operations 27%
Support EMEA 21%
Support Americas 18%
Collections and dashboards
Incident numbers, computed, without asking anyone.
Four metrics, a 14 day chart of incidents created, broken down by team, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for BMC Helix
All three can connect BMC Helix 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over BMC Helix tools | Allow or restrict single BMC Helix 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 BMC Helix 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
BMC Helix tools for your AI agents
67 tools are ready to call through Elaichi's MCP endpoint the moment you connect BMC Helix, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect BMC Helix to Claude?
Connect BMC Helix in Elaichi by pasting in your BMC Helix API key; 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 in https://api.elaichi.ai/mcp. Sign in to Elaichi as yourself and BMC Helix is ready to use in Claude.
Does BMC Helix work with ChatGPT and Cursor as well as Claude?
Yes. The same endpoint, https://api.elaichi.ai/mcp, serves Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. Connect BMC Helix once in Elaichi and every client you add gets it.
What can an AI agent actually do with my BMC Helix data?
It can list, read, create, update and delete BMC Helix incidents, companies, worklogs and support groups, and list, read and update tasks. In practice that means logging an incident from a call, adding a worklog after a fix, checking open tasks on an outage, or pulling every open incident for a customer. Short, concrete asks such as "add a worklog to the printer incident saying the toner was replaced" work better than long paragraphs.
Does connecting BMC Helix give the AI everything in my instance?
No. The connection runs inside the BMC Helix access of the API key that was entered, so it can only reach the incidents, companies, worklogs, support groups and tasks that access already allows. Elaichi can narrow that further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in BMC Helix?
Yes. Restrictions in Elaichi apply per action, so you can restrict deleting BMC Helix incidents or companies, or updating support groups, for a role or for 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 BMC Helix connection when someone leaves?
Offboarding that person in Elaichi ends their access to BMC Helix at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent. A shared BMC Helix connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting BMC Helix once in Elaichi removes it from every client.
Does the BMC Helix MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. BMC Helix 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 BMC Helix?
Yes. Both let Claude, ChatGPT or Cursor use BMC Helix. 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 BMC Helix call.
How is Elaichi different from Composio for BMC Helix?
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 BMC Helix: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put BMC Helix in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot