Application Development
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.
-
How it connects. Connects with an API key. 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.
3 tools
How to connect
How to connect Boomi to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Boomi once
-
Open Connections, choose Add connection, and pick Boomi.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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 Boomi 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 Boomi 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 Boomi 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 Boomi 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 Boomi through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Pull the full Boomi user list
Ask for everyone who currently has a Boomi account before a quarterly access review, without logging into the admin console to export it.
-
Security
Check what a Boomi role grants
Look up a single role and read exactly which privileges it carries before approving a request to assign it.
-
Compliance
Answer an auditor's access question fast
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.
-
HR
Confirm a leaver is really gone
After someone leaves, ask whether their name still appears among Boomi users and flag it to IT if it does.
-
Operations
Match Boomi roles to job titles
Compare the people holding administrator roles in Boomi against the org chart and spot accounts that have more access than the job needs.
-
Finance
Count Boomi seats before renewal
List active Boomi users ahead of the contract renewal to see how many accounts you are actually paying for.
Try asking
- “List every Boomi role and who holds it.”
- “Which Boomi users have no role assigned?”
- “Show details for the Boomi administrator role.”
AI tools
Boomi tools for your AI agents
3 tools are ready to call through Elaichi's MCP endpoint the moment you connect Boomi, 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 Boomi gets you
6 screens from the product, each doing one job for your Boomi account.
The agent
Ask about Boomi users and roles.
Type a question in plain language and get answers from live Boomi records.
- users
- roles
- role privileges
- accounts
Ask Elaichi to work across your apps.
List every Boomi role and who holds it.
Which Boomi users have no role assigned?
Show details for the Boomi administrator role.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Boomi endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
3 Boomi tools ready without custom code.
Browse Boomi users, roles and role lookups by name, resource and method.
- List all Boomi users
- List all Boomi roles
- Get single Boomi role by ID
ElaichiToolsToolboxes
Every team gets its own Boomi toolbox.
Platform, integration and security teams each see only the Boomi tools they need.
- Platform engineering
- Integration delivery
- Security and compliance
- IT operations
ElaichiToolboxesShared connections
Share a Boomi account, never the credential.
See who connected each Boomi account and how many teams and members use it.
- Platform prod
- Integration sandbox
- Security review
- IT operations
ElaichiConnectionsAudit log
Answer who read which Boomi role.
Every call records when, who, what happened, the type and the Boomi resource.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 turns Boomi roles into a digest.
Six steps fetch Boomi users and roles, group them, draft, get approval, post back.
Boomi digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
Boomi
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
Boomi
Queued
Collections and dashboards
Boomi user and role numbers, computed nightly.
Four metrics, 14 days of records created and a team breakdown, no model involved.
Boomi health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Roles
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Platform prod 34%
Integration sandbox 27%
Security review 21%
IT operations 18%
FAQ
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 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.
Put Boomi in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.