Resources · Claude connector

Claude Brex connectorWhat Claude can do in your Brex account.

The Claude Brex connector exposes 10 tools. 7 read your spend data, 0 write to it on the directory sheet, and 3 are documented nowhere. Below: what Claude can look up, what it cannot touch, the admin step first, and where Brex says more than the sheet.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes for an employee with a Brex card

No more logging into the dashboard to answer the same three questions: how much is left on the limit, which receipts are missing, when the reimbursement lands. You ask Claude, it reads your own Brex data and answers in the chat. Card numbers never show up, and what your role hides stays hidden.

Close your expense report faster. list_my_expenses pulls your recent spend, filtered by date, amount or merchant, and flags the lines still missing a receipt. get_expense_policy answers the policy question you were about to email finance about.

Know what you can still spend. list_my_limits gives each limit, its remaining balance and its period; list_my_cards shows the cards you can use and their status, without their numbers.

Stop chasing reimbursements. get_reimbursement_payout_date returns the expected payout date of an approved reimbursement.

What it will not do: the directory sheet lists no tool that changes anything, and Brex points to its dashboard or mobile app to create reimbursements, approve or reject expenses, or edit a team's transactions. Brex's article does describe edits to your own memos and receipts, a gap covered in the limits below. Nothing runs by itself either; for scheduled exports, the Brex Make integration answers another need, and the Integrations hub lists the rest.

Vocabulary

The vocabulary in one minute

Five words you will meet while plugging Brex into Claude.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory sheet lists them by name.
Authorization
Brex's own sign-in and permission request, where you hand Claude its access. Granted once per person, revocable the same way.
Approval
The confirmation Claude waits for before it goes ahead with a change to an account, shown in the conversation when it matters.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Brex.
Connect

Connect Brex to Claude in three steps

  1. 01

    Find Brex in Claude

    Open Claude's settings, go to Customize then Connectors, and look for Brex. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before members can sign in to it.

  2. 02

    Start the connection

    Click Connect on Brex's row, then sign in with the email tied to your Brex account, through single sign-on if your company uses it. If the link breaks, use Disconnect and connect again.

  3. 03

    Approve the permission request

    Read Brex's permission request before you accept: it belongs to Brex, not to Claude, and it sets what the access covers. Access can be revoked later from the Brex dashboard, under Settings, Personal settings, Connected Integrations.

Tools

The 10 tools, sorted by what they do

Brex gives Claude 10 tools: 7 that read your account, 0 that change something in it, and 3 no official source describes.

Two groups on the directory sheet: what Claude reads, and what no official source describes. Tool names stay exactly as Claude shows them.

  • 7 read
  • 3 not documented

What Claude reads (7)

7 tools

Seven tools that look up your spending data without touching it.

get_card_by_id

Retrieves the details of one Brex card, including its limits and status, according to Brex's description of its server. Card numbers are not part of what Claude gets.

When it helps
a card was declined at checkout and you want to see its status before calling anyone.

Sourcebrex.com · September 30, 2026 ↗

get_expense_policy

Gives Claude your company's expense policy, so it can answer policy questions and guide how you word a memo, as the directory sheet describes.

When it helps
you are about to book a client dinner and want to know what the policy allows before paying.

Sourceclaude.com · September 30, 2026 ↗

get_reimbursement_payout_date

Looks up the expected payout date of a reimbursement that has already been approved.

When it helps
you advanced a conference fee and want to know when the money comes back.
Watch out
no date shows if the reimbursement is not approved yet or no payout has been scheduled, Brex notes.

Sourcebrex.com · September 30, 2026 ↗

list_my_cards

Shows the cards you are allowed to use and whether each one is active, without ever displaying a card number.

When it helps
you have a travel card and a software card and forgot which one covers a given purchase.

Sourcebrex.com · September 30, 2026 ↗

list_my_expenses

Pulls your recent expenses, which Claude can filter by date, amount or merchant, and points out those still missing a receipt.

When it helps
month-end is tomorrow and you want the list of receipts to dig out of your inbox.
Watch out
a narrower query helps if results look incomplete.

Sourcebrex.com · September 30, 2026 ↗

list_my_limits

Reads your spend limits with the amount left on each and the period it covers.

When it helps
before a trip, you check how much remains on your travel and entertainment limit this month.
Watch out
if a limit seems to be missing, Brex says your role may not give access to that data.

Sourcebrex.com · September 30, 2026 ↗

list_users_by_name_or_email

Searches the people in your Brex account by name or email, which Brex frames as useful for admins running audits or onboarding.

When it helps
an account admin wants to check whether a new hire already exists in Brex before issuing anything.

Sourcebrex.com · September 30, 2026 ↗

Not documented (3)

3 tools

The directory publishes these three names and nothing more. No official text says what they do, and this page will not guess from a name.

get_user_by_id

This name appears on the directory's tool list, and that is all anyone publishes about it. Brex's article does not describe it and no Claude page does either, so this page goes no further.

Watch out
whatever it does, the general approval rule covers it.

get_user_myself

Listed by name on the directory sheet with no official description, neither from Brex nor from Anthropic. Reading a role into the name would be making it up.

Watch out
it falls under the same general approval rule as every other tool.

list_users

No source explains this one: Brex's help article describes searching users, not this tool, and Claude's documentation has no Brex page. Only its name is public, nothing about what it returns.

Watch out
the approval rules below apply to it like to the rest.
Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. On this sheet every documented tool only reads, and no source says whether a lookup triggers that prompt.

On a Team or Enterprise workspace, owners decide whether members may let some actions through without being asked each time. They can also cap what a connector may do for the whole organisation, keeping reads and closing writes, and nobody overrides that from their own account. Brex adds its own layer: the connector respects your role-based permissions, so Claude only sees what your Brex user is allowed to see. Card and account admins can ask broader company spend questions.

Plans

Which plans this works on

None of the 819 sheets in the official directory shows plan availability. The per-connector answer is published nowhere, and that is a real gap in the catalogue.

The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organisation before each member can sign in. Brex tells its users the same thing. For the current state of this one, check the Brex sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a card is swiped or a receipt goes missing.

Only Brex documents this connector, and flags it as early access; neither Claude's help centre nor Anthropic's developer docs have a page on it. By default, its sheet only exposes reading, which is an observed floor, not a guarantee: an administrator may open actions no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not guarantee how a publisher's tools behave. Your questions and Claude's answers are processed by Anthropic under your organisation's Claude agreement, Brex notes.

Two official sources disagree

Can the Brex connector change anything in Brex from Claude?

What this page followsThey describe different tool lists. Brex announces edits and whole areas that none of the 10 tools on the sheet carries, and itself says a tools refresh is needed to get the full suite. This page sticks to the sheet and states the gap: after refreshing, the list Claude shows you is the one that counts.

Need help

Need help connecting Brex to Claude?

A person reads every message.

FAQ

FAQ about the Claude Brex connector

01What can Claude do with the Claude Brex connector?
Claude can answer questions about your own Brex spending from a conversation. The seven documented tools read your recent expenses and the ones missing receipts, your spend limits and what remains on them, the cards you can use and their status, the details of one card, the payout date of an approved reimbursement, your company's expense policy, and a search of users by name or email. Three more tools appear on the directory sheet with no official description at all.
02Can Claude change or submit anything in Brex?
Not with the tools on the directory sheet: all seven documented ones only read, and three are undocumented. Brex's help article says otherwise, describing edits to memos, receipts, attendees and spend limits on your own transactions, and asks users to refresh the tools list to get them. Either way, creating reimbursements, approving or rejecting expenses and changing a team's transactions stay in the Brex dashboard or mobile app, according to Brex itself.
03Does Claude ask before acting in Brex?
Claude's default is to ask for confirmation before any action it takes on an account for you. No source describes a confirmation specific to a Brex tool, and the documented tools only read; no source says whether a lookup triggers a prompt. On a Team or Enterprise workspace, owners decide whether members can let some actions pass without being asked, and they can close writing for the whole organisation if that suits a finance team better.
04Which plans is the Brex connector available on?
No official source publishes availability per plan, connector by connector, and no directory sheet shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner must switch the connector on before members can sign in. The publisher repeats this in its own setup steps. The connector's sheet in the official directory is the only place that shows its current state for your account.
05Does Claude see all of my company's Brex data?
No, only what your own Brex user can see. Brex says its server respects the role-based permissions already set up in your account: an employee sees their own cards, limits and expenses, while card admins and account admins can ask high-level questions about company spend. Card numbers are never shown. Every action through the connector is recorded as the connector acting for the signed-in user, and access can be revoked from the Brex dashboard at any time.
06Why does the Brex connector not work after I connected it?
Most often because the Brex side is not switched on. Brex requires a one-time admin step: an account or card admin opens Settings in the Brex dashboard, goes to Early access and turns on Brex MCP access. On a Team or Enterprise Claude workspace, an admin also has to add the connector to the organisation first. If results look incomplete instead, Brex points to your role's access, then suggests adding a date range, merchant or amount to the question.
07Claude or an automation tool for Brex?
They answer different needs, so it depends on the job. Claude works inside a conversation: you ask about a limit, a missing receipt or a payout, it looks it up and answers, and nothing happens once you stop typing. It does not react on its own when a card is used or an expense is filed. Anything that must run on a schedule or on an event belongs to an automation tool. For quick answers about your own spending, the connector is the better fit.