Brex MCP connector
The Brex connector brings card expenses, receipts, memos, cost centers and spend analytics into Claude, ChatGPT, Cursor or the Elaichi Agent, so each person works with Brex inside their own access while every action is logged.
-
How it connects. Connects over OAuth. 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.
43 tools
How to connect
How to connect Brex to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Brex once
-
Open Connections, choose Add connection, and pick Brex.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Brex. Brex's own window opens. Whoever approves it decides what this connection can reach.
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.
Brex 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.
Brex 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.
Brex 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 Brex 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 Brex through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Find card expenses missing receipts before close
Ask for last week's Brex card expenses that still have no receipt, then attach the receipt from a link without leaving the conversation.
-
Accounting
Fix memos on card expenses after the fact
Catch up the memo on a Brex expense after a call with the cardholder so the expense category and purpose are clear at month end.
-
Sales
Add attendees to a client dinner charge
After a customer dinner, tell the agent who was at the table and it updates the attendees on the Brex card expense.
-
Operations
See spend by merchant and cost center
Query Brex expense analytics to see which merchants, cost centers and locations are driving spend this quarter, in plain language.
-
People
Check reimbursement payout dates for employees
Answer the question every new hire asks by looking up when a Brex reimbursement pays out, and check reward points while you are there.
-
Leadership
Pull an expense export for the board
Start a Brex expense download for the period you need and collect the result when it is ready, with no spreadsheet work in between.
Try asking
- “Which card expenses from last week are still missing receipts?”
- “Summarize travel spend by cost center for this quarter.”
- “When does my latest reimbursement pay out?”
Compare
Elaichi vs Zapier MCP vs Composio for Brex
All three can connect Brex 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 Brex tools | Allow or restrict single Brex 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 Brex 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
Brex tools for your AI agents
43 tools are ready to call through Elaichi's MCP endpoint the moment you connect Brex, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Brex builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Brex gets you
6 screens from the product, each doing one job for your Brex account.
The agent
Ask Brex about expenses in plain language.
Get answers from live expenses, merchants and cost centers without opening a report.
- expenses
- users
- cost centers
- merchants
Ask Elaichi to work across your apps.
Which card expenses from last week are still missing receipts?
Summarize travel spend by cost center for this quarter.
When does my latest reimbursement pay out?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One governed endpoint for Claude, ChatGPT and Cursor.
Connect Brex once and every MCP client works through it, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
43 Brex tools, ready without writing code.
Expenses, receipts, users, cost centers and analytics, covered without any custom code.
- Get user myself
- Get user by ID
- List users by name or email
- List users
ElaichiToolsToolboxes
Every team gets its own Brex toolbox.
Finance, accounting and operations each work from a toolbox scoped to their job.
- Finance
- Accounting
- Operations
- Sales
ElaichiToolboxesShared connections
Teammates use Brex without touching a credential.
One person connects Brex, shares it with teams, and members work through it as themselves.
- Finance
- Accounting
- Sales EMEA
- Operations
ElaichiConnectionsAudit log
Every Brex action lands in the log.
See who changed a memo, attached a receipt or ran an export, and when.
- 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
The weekly Brex expense digest runs itself.
A schedule fetches Brex expenses, groups them, drafts a digest, and a person approves before posting.
Brex digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch expenses
Brex
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
Brex
Queued
Collections and dashboards
Brex spend numbers, computed with no model.
Four metrics, 14 days of expenses created and a breakdown by team, refreshed on schedule.
Brex health
Refreshed 4 minutes ago · every 15 minutes · from the expenses collection
Expenses
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Expenses created
Last 14 days
By team
Share of activity
Finance 34%
Accounting 27%
Sales EMEA 21%
Operations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Brex to Claude?
Connect Brex in Elaichi first, where Brex asks you to sign in over OAuth and approve access, with no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can then work with your Brex expenses, receipts and cost centers as you.
Does Brex work with ChatGPT and Cursor as well as Claude?
Yes. Once Brex 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 Brex once and every client uses it.
What can an AI agent actually do with my Brex data?
It can list and look up Brex card expenses, update a memo, attach a receipt from a link, change the attendees on a charge, assign a limit to card expenses and query spend analytics by merchant, cost center or category. It can also look up users, departments, locations, legal entities, reward points and reimbursement payout dates, and start an expense export. Short, concrete asks such as "expenses over 500 dollars this month" work better than long sentences.
Does connecting Brex give the AI access to the whole company's spend?
No. The AI sees only what the person who signed in to Brex can see, so a cardholder sees their own expenses and a finance admin sees what their Brex role allows. Elaichi can narrow that access further for a team or a person, but it can never widen it beyond what Brex already grants.
Can I stop an agent from changing memos, receipts or limits in Brex?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Brex expenses while blocking memo updates, receipt uploads or limit changes. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
What happens to a Brex connection when someone leaves the company?
Offboarding that person in Elaichi ends their access to Brex through every client at once. A shared Brex connection keeps working for everyone else on the team. If you disconnect Brex once in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Brex MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Brex 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 Brex?
Yes. Both let Claude, ChatGPT or Cursor use Brex. 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 Brex call.
How is Elaichi different from Composio for Brex?
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 Brex: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Brex 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.