# Boomi MCP connector

The Boomi connector brings your Boomi users and roles to Claude, ChatGPT, Cursor and any MCP client, so anyone signed in can ask who has a Boomi account and what each role allows.

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

## Facts

| | |
| --- | --- |
| Application | Boomi |
| Category | Application Development |
| AI tools | 3 |
| Authentication | Connects with an API key |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Boomi is connected

- List every Boomi role and who holds it.
- Which Boomi users have no role assigned?
- Show details for the Boomi administrator role.

## Connect Boomi in Elaichi

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

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

## Connect Boomi to 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.

## Connect Boomi to 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 today. The plugin directory lives at chatgpt.com/plugins.

## Connect Boomi to 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.

## Connect Boomi 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

Only Read is granted by default, which is not enough to call a Boomi tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Boomi through Elaichi

### Pull the full Boomi user list

IT. Ask for everyone who currently has a Boomi account before a quarterly access review, without logging into the admin console to export it.

### Check what a Boomi role grants

Security. Look up a single role and read exactly which privileges it carries before approving a request to assign it.

### Answer an auditor's access question fast

Compliance. When an auditor asks who can administer Boomi, get the list of users and roles in one question and paste the answer into the evidence file.

### Confirm a leaver is really gone

HR. After someone leaves, ask whether their name still appears among Boomi users and flag it to IT if it does.

### Match Boomi roles to job titles

Operations. Compare the people holding administrator roles in Boomi against the org chart and spot accounts that have more access than the job needs.

### Count Boomi seats before renewal

Finance. List active Boomi users ahead of the contract renewal to see how many accounts you are actually paying for.

## Frequently asked questions

### How do I connect Boomi to Claude?

Connect Boomi in Elaichi first, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. For the Boomi sign-in step you paste a Boomi API key into Elaichi, and that is all. There is no OAuth application to register and no client ID or secret to generate.

### Does Boomi work with ChatGPT and Cursor as well as Claude?

Yes. Once Boomi is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Boomi once and every client picks it up.

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

With this connector an agent can read your Boomi user list, read your list of Boomi roles, and look up one role to see what it grants. That covers questions like who has a Boomi account, who holds an administrator role, and what a given role lets someone do. It cannot create, edit or remove anything in Boomi.

### Does connecting Boomi give the AI access to my whole Boomi account?

No. Every request runs under the Boomi API key of the person who connected it, so the agent sees only the users and roles that key is allowed to see in Boomi. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Boomi itself grants.

### Can my team share one Boomi connection?

Yes. One person connects Boomi with their API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who asked for the Boomi user list or a role lookup.

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

This Boomi connector only reads users and roles, so nothing can be changed or deleted through it in the first place. If you want to narrow it further, restrictions in Elaichi work per action, and any action you block is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.

### What happens to a Boomi connection when someone leaves?

Offboarding that person in Elaichi ends their access to Boomi through every client at once. If they had shared the Boomi connection with a team, it keeps working for everyone else. When you want Boomi gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

## All 3 Boomi tools

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

- **List all Boomi users** (List). Use this endpoint to list all the users available in Boomi.

- **List all Boomi roles** (List). Use this endpoint to list all the roles available in Boomi.

- **Get single Boomi role by ID** (Get). Use this endpoint to retrieve details of a specific role in a Boomi account. Always requires the id to fetch.

