Independent review. Unpaid; no partnership with Brex. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Corporate cards, expense management, bill pay and business-account services. Brex MCP (beta) can query spend and update selected expense fields under the user's permissions. Approvals and card management are not available through MCP; review write actions before execution.
The Ion perspective
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
Value
Corporate cards, expense management, bill pay and business-account services. Brex MCP (beta) can query spend and update selected expense fields under the user's permissions. Approvals and card management are not available through MCP; review write actions before execution.
Differentiation
Documented fit: Startups that want cards and expense policy in one tool; Asking an AI assistant about spend without exporting data. Uniqueness is not established.
Replaceability and switching
Compare Ramp, Mercury. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Approving expenses or managing cards from an AI assistant (not yet available via Brex MCP). Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
IonBin provides general information and software comparisons, not tax, legal, accounting or financial advice. Tax and legal rules vary by situation and jurisdiction; consult a qualified professional (CPA, enrolled agent or attorney) before acting.
AI tools can make mistakes. Verify every figure against the original documents and official IRS or state guidance before filing or signing.
Redact Social Security numbers, account numbers and EINs before uploading documents to any AI assistant, and check its data-retention settings. Upload originals only to the filing or signing software.
Best for
Startups that want cards and expense policy in one tool
Asking an AI assistant about spend without exporting data
Not for
Approving expenses or managing cards from an AI assistant (not yet available via Brex MCP)
Top use cases
Ask an AI assistant about expenses, cards and bills through Brex MCP source ↗
Download filtered expenses as CSV for month-end review source ↗
In depth
Plans
Brex advertises Essentials at $0/user/month with API access, Premium at $12/user/month, and custom Enterprise and Smart Card pricing. The retrieved page does not specify an annual-versus-monthly commitment for the $12 rate. Eligibility and other product fees still apply; confirm the applicable terms. source ↗
MCP setup
An account or card admin accepts the Developer API agreement and enables the AI-assistant beta. Users can then authorize via OAuth using their own Brex permissions; an API-token route is also documented. MCP includes some writes, such as expense memos and receipt uploads, but not approvals or card management. source ↗
How to use it with AI
How Brex connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
Not documentedOfficial Brex MCP setup; beta enablement and user capabilities apply. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup.Brex named integration docs ↗Claude (incl. Claude Code) MCP docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Brex's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route.Brex file docs ↗Claude (incl. Claude Code) file docs ↗
Not documentedOfficial Brex MCP setup; beta enablement and user capabilities apply. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup.Brex named integration docs ↗OpenAI Codex MCP docs ↗
Not documentedOpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Brex publishes an API, but this pairing still needs network, authentication and execution-scope checks.Brex API ↗OpenAI Codex docs ↗
InferredOnly in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Brex is a web app; the pairing itself is not documented.OpenAI Codex browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Brex's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route.Brex file docs ↗OpenAI Codex file docs ↗
InferredThe /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Brex is a web app; the pairing itself is not documented.Google Antigravity browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Brex's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route.Brex file docs ↗Google Antigravity file docs ↗
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
Agent compatibility
MCPAPI/CLIFile import
Level
Status
Detail / source
Native connector / MCP
Yes
Official docs ↗ (beta; an admin accepts the Developer API agreement and enables the beta)
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Corporate cards, expenses and bill pay with spend controls. Its MCP server lets assistants query spend and act on supported approvals, reimbursements and cards within user permissions. A separate developer API is documented.
Business banking for startups. Mercury MCP (in beta) connects AI tools over OAuth to read accounts and transactions and to request payments or transfers, which still need approval in Mercury; an API is also documented.