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

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

## Facts

| | |
| --- | --- |
| Application | BMC Helix |
| Category | Application Development |
| AI tools | 67 |
| 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 BMC Helix is connected

- 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?

## Connect BMC Helix in Elaichi

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

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

## BMC Helix 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.

## BMC Helix 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`.

## BMC Helix 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.

## BMC Helix 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.

## BMC Helix 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 BMC Helix 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 BMC Helix 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 BMC Helix through Elaichi

### Log an incident while the caller is on the line

Service desk. 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.

### Catch the incident up after the fix

IT operations. 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.

### See every open incident for one customer

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

### Add a worklog in one sentence

Service desk. 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.

### Keep support groups current

IT operations. 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.

### Check what tasks are still outstanding

Facilities. Ask which tasks on an incident are still open, then mark the one you finished as done so the incident can be closed.

## 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. Endpoint: 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](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 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 my team share one BMC Helix connection?

Yes. One person connects BMC Helix with the API key and shares the connection with a team, and nobody else ever handles or sees the key. Each teammate still signs in to Elaichi as themselves, so every incident update or worklog in the audit log carries their own name.

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

## All 67 BMC Helix tools

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

- **List all BMC Helix incident** (List). List incident entries from the BMC Helix ITSM HPD:Help Desk form. Filter with an AR qualification in q, choose fields with fields, page with offset and limit. Returns entries with their field values.
- **Get single BMC Helix incident by ID** (Get). Get one incident entry from the HPD:Help Desk form by entry ID. Required: id. Returns the entry's field values.
- **Create a BMC Helix incident** (Create). Create an incident through the HPD:IncidentInterface_Create form. Required: values with First_Name, Last_Name, Description, Impact, Urgency, Status, Reported Source and Service_Type (z1D_Action is CREATE). Returns the new Incident Number.
- **Update a BMC Helix incident by ID** (Update). Update a incident entry in the HPD:Help Desk form. Send only the fields to change inside values. Required: id, values. Returns no content (204) on success.
- **Delete a BMC Helix incident by ID** (Delete). Delete a incident entry from the HPD:Help Desk form by entry ID. Requires delete permission on the form, which most ITSM forms restrict. Required: id. Returns no content on success.
- **List all BMC Helix company** (List). List company entries from the BMC Helix ITSM COM:Company form. Filter with an AR qualification in q, choose fields with fields, page with offset and limit. Returns entries with their field values.
- **Get single BMC Helix company by ID** (Get). Get one company entry from the COM:Company form by entry ID. Required: id. Returns the entry's field values.
- **Update a BMC Helix company by ID** (Update). Update a company entry in the COM:Company form. Send only the fields to change inside values. Required: id, values. Returns no content (204) on success.
- **Delete a BMC Helix company by ID** (Delete). Delete a company entry from the COM:Company form by entry ID. Requires delete permission on the form, which most ITSM forms restrict. Required: id. Returns no content on success.
- **Create a BMC Helix company** (Create). Create a company entry in the COM:Company form. Required: values with Company, Company Type, Status. Returns 201 with the new entry's URL in the Location header, or field values when fields is set.
- **List all BMC Helix worklogs** (List). List incident work log entries from the BMC Helix ITSM HPD:WorkLog form. Filter with an AR qualification in q, choose fields with fields, page with offset and limit. Returns entries with their field values.
- **Create a BMC Helix worklog** (Create). Create a incident work log entry in the HPD:WorkLog form. Required: values with Incident Number, Work Log Type, Detailed Description. Returns 201 with the new entry's URL in the Location header, or field values when fields is set.
- **Get single BMC Helix worklog by ID** (Get). Get one incident work log entry from the HPD:WorkLog form by entry ID. Required: id. Returns the entry's field values.
- **Update a BMC Helix worklog by ID** (Update). Update a incident work log entry in the HPD:WorkLog form. Send only the fields to change inside values. Required: id, values. Returns no content (204) on success.
- **Delete a BMC Helix worklog by ID** (Delete). Delete a incident work log entry from the HPD:WorkLog form by entry ID. Requires delete permission on the form, which most ITSM forms restrict. Required: id. Returns no content on success.
- **BMC Helix worklogs download** (Download). Download a work log attachment as a file. Take the attachment href from a work log entry (z2AF Work Log01–03 field), split it into base (scheme and host) and path, and pass both. Required: base, path.
- **List all BMC Helix support group** (List). List support group entries from the BMC Helix ITSM CTM:Support Group form. Filter with an AR qualification in q, choose fields with fields, page with offset and limit. Returns entries with their field values.
- **Get single BMC Helix support group by ID** (Get). Get one support group entry from the CTM:Support Group form by entry ID. Required: id. Returns the entry's field values.
- **Create a BMC Helix support group** (Create). Create a support group entry in the CTM:Support Group form. Required: values with Support Group Name, Support Organization, Company, Support Group Role, Status. Returns 201 with the new entry's URL in the Location header, or field values when fields is set.
- **Update a BMC Helix support group by ID** (Update). Update a support group entry in the CTM:Support Group form. Send only the fields to change inside values. Required: id, values. Returns no content (204) on success.
- **Delete a BMC Helix support group by ID** (Delete). Delete a support group entry from the CTM:Support Group form by entry ID. Requires delete permission on the form, which most ITSM forms restrict. Required: id. Returns no content on success.
- **List all BMC Helix tasks** (List). List task entries from the BMC Helix ITSM TMS:Task form. Filter with an AR qualification in q, choose fields with fields, page with offset and limit. Returns entries with their field values.
- **Get single BMC Helix task by ID** (Get). Get one task entry from the TMS:Task form by entry ID. Required: id. Returns the entry's field values.
- **Update a BMC Helix task by ID** (Update). Update a task entry in the TMS:Task form. Send only the fields to change inside values. Required: id, values. Returns no content (204) on success.
- **Delete a BMC Helix task by ID** (Delete). Delete a task entry from the TMS:Task form by entry ID. Requires delete permission on the form, which most ITSM forms restrict. Required: id. Returns no content on success.
- **Create a BMC Helix task** (Create). Create a task entry in the TMS:Task form. Required: values with TaskName, Summary, Status, RootRequestID, RootRequestFormName. Returns 201 with the new entry's URL in the Location header, or field values when fields is set.
- **List all BMC Helix people** (List). List person (people record) entries from the BMC Helix ITSM CTM:People form. Filter with an AR qualification in q, choose fields with fields, page with offset and limit. Returns entries with their field values.
- **Get single BMC Helix person by ID** (Get). Get one person (people record) entry from the CTM:People form by entry ID. Required: id. Returns the entry's field values.
- **Create a BMC Helix person** (Create). Create a person (people record) entry in the CTM:People form. Required: values with First Name, Last Name, Company, Profile Status, Client Type, Support Staff. Returns 201 with the new entry's URL in the Location header, or field values when fields is set.
- **Update a BMC Helix person by ID** (Update). Update a person (people record) entry in the CTM:People form. Send only the fields to change inside values. Required: id, values. Returns no content (204) on success.
- **Delete a BMC Helix person by ID** (Delete). Delete a person (people record) entry from the CTM:People form by entry ID. Requires delete permission on the form, which most ITSM forms restrict. Required: id. Returns no content on success.
- **Create a BMC Helix authentication login request** (Create). Log in to BMC Helix with the connected account's username and password and get a session token (AR-JWT) in the Set-Cookie header. Used internally to refresh authentication; takes no input.
- **List all BMC Helix incident interface** (List). List incidents through the HPD:IncidentInterface form. Filter with an AR qualification in q, choose fields, sort and page with offset/limit.
- **Get single BMC Helix incident interface by ID** (Get). Get one incidents entry from the HPD:IncidentInterface form by entry ID. Required: id.
- **Update a BMC Helix incident interface by ID** (Update). Update a incidents entry through the HPD:IncidentInterface form. Send only the fields to change inside values (set z1D_Action to MODIFY). Required: id, values. Returns no content (204).
- **Create a BMC Helix change** (Create). Create a change request through CHG:ChangeInterface_Create. Required: values with Description, Impact, Urgency, Company, First Name, Last Name and z1D_Action CREATE. Returns the new Infrastructure Change Id (CRQ…).
- **List all BMC Helix changes** (List). List change requests through the CHG:ChangeInterface form. Filter with an AR qualification in q, choose fields, sort and page with offset/limit.
- **Get single BMC Helix change by ID** (Get). Get one change requests entry from the CHG:ChangeInterface form by entry ID. Required: id.
- **Update a BMC Helix change by ID** (Update). Update a change requests entry through the CHG:ChangeInterface form. Send only the fields to change inside values (set z1D_Action to MODIFY). Required: id, values. Returns no content (204).
- **List all BMC Helix change worklogs** (List). List change work info entries through the CHG:WorkLog form. Filter with an AR qualification in q, choose fields, sort and page with offset/limit.
- **Get single BMC Helix change worklog by ID** (Get). Get one change work info entries entry from the CHG:WorkLog form by entry ID. Required: id.
- **Create a BMC Helix change worklog** (Create). Add a work info note to a change request in CHG:WorkLog. Required: values with Infrastructure Change ID, Work Log Type and Detailed Description. Returns 201 with the entry URL in the Location header.
- **Update a BMC Helix change worklog by ID** (Update). Update a change work info entries entry through the CHG:WorkLog form. Send only the fields to change inside values (set z1D_Action to MODIFY). Required: id, values. Returns no content (204).
- **List all BMC Helix change associations** (List). List change associations (links between a change and CIs or other records) through the CHG:Associations form. Filter with an AR qualification in q, choose fields, sort and page with offset/limit.
- **Create a BMC Helix change association** (Create). Associate a configuration item or another record with a change request in CHG:Associations. Required: values with Request ID01, Request ID02, Form Name01, Form Name02 and Association Type01. Returns 201 with the entry URL in the Location header.
- **Create a BMC Helix problem** (Create). Create a problem investigation, known error or solution through PBM:ProblemInterface_Create (z1D_Action PROBLEM, KNOWNERROR or SOLUTION). Required: values with Description, Impact, Urgency, Company, Assigned Support Company, Assigned Support Organization, Assigned Group and z1D_Action. Returns the new ID.
- **List all BMC Helix problems** (List). List problem investigations through the PBM:ProblemInterface form. Filter with an AR qualification in q, choose fields, sort and page with offset/limit.
- **Get single BMC Helix problem by ID** (Get). Get one problem investigations entry from the PBM:ProblemInterface form by entry ID. Required: id.
- **Update a BMC Helix problem by ID** (Update). Update a problem investigations entry through the PBM:ProblemInterface form. Send only the fields to change inside values (set z1D_Action to MODIFY). Required: id, values. Returns no content (204).
- **Create a BMC Helix service request** (Create). Create a service request from a Service Request Definition through SRM:RequestInterface_Create. Required: values with TitleInstanceID, Login ID, Source Keyword and z1D_Action CREATE. Returns the new Request Number (REQ…).
- ...and 17 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
