Orum MCP connector
The Orum connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent look up, create, and update the people, businesses, bank accounts, and cards you pay through Orum, with every action tied to the person who signed in and recorded in an audit log.
-
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 Orum to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Orum once
-
Open Connections, choose Add connection, and pick Orum.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Orum app credentials. Orum 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.
Orum 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.
Orum 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 today. The plugin directory lives at chatgpt.com/plugins.
Orum 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.
Connect Orum 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 Orum through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Add a new payee before the first payout
When a contractor or vendor is ready to be paid, create the person or business in Orum and attach their bank account in one ask, instead of clicking through the dashboard field by field.
-
Operations
Fix a payee's bank details after a bounce
When a payout fails because an account number changed, find the payee in Orum, correct the external account, and confirm the update landed, all from the chat you are already in.
-
Support
Answer 'where is my payment' without switching tabs
Pull up a customer's Orum record, see which bank accounts and cards are on file, and tell them exactly which one their money is headed to.
-
Compliance
Review who is set up to receive money
List every person and business in Orum, check the details against your own records, and flag anything that looks incomplete or out of date.
-
Payments operations
Update many payee records at once
When a batch of vendors moves to a new legal entity or address, apply the change across all the affected Orum businesses in a single request rather than one at a time.
-
Onboarding
Check a new customer is fully set up
Before their first payout, confirm the Orum person exists, has at least one bank account or card linked, and that nothing is missing from the record.
Try asking
- “Which deliver businesses had failed payments this week?”
- “List deliver persons added in the last 30 days.”
- “Show total transfers processed by deliver business this month.”
Compare
Elaichi vs Zapier MCP vs Composio for Orum
All three can connect Orum 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 Orum tools | Allow or restrict single Orum 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 Orum 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 | $15 per user per month. | 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.
AI tools
Orum tools for your AI agents
70 tools are ready to call through Elaichi's MCP endpoint the moment you connect Orum, 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 Orum gets you
6 screens from the product, each doing one job for your Orum account.
The agent
Ask Orum payment questions, get instant answers.
Type a question about deliver persons or businesses and get answers from live records.
- deliver persons
- deliver businesses
- payments
- transfers
Ask Elaichi to work across your apps.
Which deliver businesses had failed payments this week?
List deliver persons added in the last 30 days.
Show total transfers processed by deliver business this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects every MCP client to Orum.
Claude, ChatGPT and Cursor reach Orum through one governed endpoint, no SDK or shared key needed.
Copy the endpoint
Tool catalog
70 Orum tools, no custom code required.
Browse all 70 Orum tools, resources and methods in one catalog.
- List all Orum deliver persons
- Create a Orum deliver person
- Orum deliver persons bulk update
- Get single Orum deliver person by ID
Toolboxes
Every team gets its own Orum toolbox.
Sales, finance and support each work from a toolbox scoped to their role.
- Finance
- Payments Ops
- Engineering
- Support
Shared connections
Teammates use Orum without ever seeing credentials.
See who connected each Orum account and how many teams and members share it.
- Payments Ops
- Finance
- Compliance
- Support
Audit log
Every Orum action is logged and traceable.
Track who did what in Orum, when it happened, and which resource it touched.
- 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 triggers real work in Orum.
A trigger fetches Orum records, drafts a digest, waits for approval, then posts back.
Orum digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch deliver persons
Orum
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
Orum
Queued
Collections and dashboards
Orum health, tracked automatically, refreshed on schedule.
Four metrics and a 14 day chart show deliver activity across teams, no model involved.
Orum health
Refreshed 4 minutes ago · every 15 minutes · from the deliver persons collection
Deliver persons
1,284 ↓ 12%
Deliver businesses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Deliver persons created
Last 14 days
By team
Share of activity
Payments Ops 34%
Finance 27%
Compliance 21%
Support 18%
FAQ
Frequently asked questions
How do I connect Orum to Claude?
Connecting Orum to Claude takes two steps. First, connect Orum in Elaichi by pasting the app credentials from your Orum dashboard; 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 the Elaichi endpoint https://api.elaichi.ai/mcp. Claude signs you in as yourself and Orum is ready to use.
Does Orum work with ChatGPT and Cursor as well as Claude?
Yes. Once Orum 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 Orum once and every client you use picks it up.
What can an AI agent actually do with my Orum data?
With Orum connected, an agent can find a payee by name, create a new person or business to pay, add or correct their bank account, see which cards are on file, and update many records in one go. Orum has a lot of actions available, so the agent searches for the right one as you ask; short concrete requests like 'update the bank account for Acme Ltd' work better than long paragraphs.
Does connecting Orum give the AI access to everything in my Orum account?
No. The AI acts inside the access of the person who signed in, so it can only see and change the Orum payees, bank accounts, and cards that person could already reach. Elaichi can narrow that further by blocking specific actions for a team, but it can never grant more than the signed-in person already has in Orum.
Can I stop an agent from deleting or changing things in Orum?
Yes. Restrictions in Elaichi work per action, so you can allow looking up Orum payees while blocking deleting a person, a business, or a bank account. 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 an Orum connection when someone leaves the company?
When you offboard someone in Elaichi, their access to Orum through every AI client ends at once. If they had shared an Orum connection with a team, it keeps working for everyone else. If you ever want Orum gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Does the Orum MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Orum 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, 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 Orum?
Yes. Both let Claude, ChatGPT or Cursor use Orum. 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 Orum call.
How is Elaichi different from Composio for Orum?
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 Orum: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Orum in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.