Brex MCP Server
Official hosted Brex MCP for expenses, cards, banking, and travel in an AI client.
- Skill Road
- Brex MCP Server
Categories
Description
The Brex MCP Server is the official, Brex-operated remote server for the Model Context Protocol. Hosted at https://api.brex.com/mcp, it enables compatible AI clients such as Claude, Claude Desktop, Cursor, or Codex to interact directly with a Brex company account. According to the provider, the server is currently in beta, and the available toolset may change as development continues.
What the Brex MCP Server Covers
The server provides an extensive set of tools aligned with the typical financial operations of a business. According to the official developer documentation at developer.brex.com/docs/mcp, the current toolset spans the following areas:
User management: Query the current user, search for people by name or email, and list cost centers, departments, locations, legal entities, titles, and roles across the company.
Expenses and receipts: Filter expenses by various parameters, retrieve individual expenses by ID, analyze high-level company spend (admins only), update memos on multiple expenses in bulk, upload receipts from URLs, replace attendees for card expenses, and assign card expenses to spend limits.
Cards and limits: List cards with comprehensive filtering, retrieve a specific card by ID, and view all spend limits that apply to the authenticated user.
Banking and transactions: List business bank accounts, retrieve account details, and view banking transactions with filtering.
Bills and vendors: Filter bills, retrieve individual bills by ID, view vendor details, and list all company vendors.
Travel: List business trips with filtering and pagination, view bookings, and manage group events such as offsites or conferences.
Accounting integration: Retrieve the active accounting integration, view accounting records, and list general ledger accounts.
Miscellaneous: Check reward points and redemption eligibility, list merchants and expense categories, and submit feedback directly to the Brex product team.
Access, Permissions, and Beta Prerequisites
According to the provider, using the MCP server requires two steps performed by an account or card admin: accepting the Developer API agreement under Settings β Developer, and enabling beta access under Settings β Beta features β Brex in AI Assistants. Once done, all users in the company account can connect with their own credentials via OAuth.
Each tool is tied to the individual user's Brex capability. A user with general access can query their own expenses and user lists, but analyzing company-wide spend requires account or card admin status. Actions such as approvals and card management are currently not available via MCP, per the provider.
Connecting: OAuth and API Keys
The recommended approach is OAuth. MCP clients that support OAuth automatically initiate a browser-based authorization flow on first connection, with no manual token setup. The authorization server is at https://accounts-api.brex.com/oauth2/default, and the server supports Dynamic Client Registration (RFC 7591), so clients do not need to be pre-registered. Sessions remain active, so repeated authorization is not required.
For clients without OAuth support, or for programmatic access, account and card admins can generate a Brex API token and pass it as a Bearer token in the Authorization header. The documentation recommends creating tokens with minimal scopes, using the client's secret management features, and never storing tokens in repositories or shared configuration files.
Integration with Common AI Clients
For Claude Code, a single command suffices: claude mcp add --transport http brex https://api.brex.com/mcp. Claude Desktop supports adding the server through the Claude connectors catalog or manually via JSON configuration. Cursor uses Settings β MCP with type http and the server URL. Codex uses codex mcp add brex --url https://api.brex.com/mcp. Any client that supports MCP HTTP transport can connect directly.
Security Considerations and Data Path
The Brex MCP Server accesses financially sensitive company data, including expenses, card details, banking transactions, and vendors. This creates several important security considerations:
First, every tool response leaves Brex and travels to the connected AI client and its model provider. Prompts, tool calls, and results may appear in the client's logs, retention path, or model policy. Brex privacy terms, client policies, and model provider terms all apply simultaneously.
Second, for AI assistants capable of executing actions β such as updating memos, uploading receipts, or assigning expenses to limits β enabling human confirmation before actions is strongly recommended to prevent unintended writes.
Third, Brex recommends monitoring API logs in the dashboard to track MCP activity, and revoking sessions under Settings β Personal settings β Connected integrations if unexpected behavior occurs.
Since there is no public source repository, no GitHub star count is available. Brex operates the MCP Server as a hosted remote service with no published source code.
FAQ
Can everyone in the company use the MCP Server? Yes, once an admin has enabled the beta, all account users can connect with their own credentials. Permissions follow individual Brex roles.
Are write actions possible? Yes, for some operations: updating memos, uploading receipts, replacing attendees, and assigning expenses to limits. Approvals and card management are not yet available per the provider.
How do I set up the server? An admin must accept the Developer API agreement and enable beta access. After that, Claude Code requires a single command; other clients require manual URL configuration.
Requirements
Not recorded yet.
Installation instructions
This guide explains how to connect the official Brex MCP Server to compatible AI clients. The server is hosted by Brex at https://api.brex.com/mcp and supports both OAuth and API key authentication.
Step 1: Prerequisites
Before any user can connect to the server, an account or card admin must complete two steps in the Brex Dashboard:
Accept the Developer API agreement: Go to Settings β Developer and accept the agreement once.
Enable beta access: Go to Settings β Beta features β Brex in AI Assistants and enable the option.
Once both steps are complete, all users in the company account can connect with their own credentials. Admins do not need to pre-provision tokens for individual users.
Step 2: Connecting with Claude Code
For Claude Code, a single terminal command is enough:
claude mcp add --transport http brex https://api.brex.com/mcp
You can then verify the connection with claude /mcp. On the first call to a Brex tool, the OAuth flow starts automatically if the client supports OAuth.
claude /mcp
If you prefer an API key, pass it as a header:
claude mcp add --transport http brex https://api.brex.com/mcp \
--header "Authorization: Bearer YOUR_BREX_API_TOKEN"
Step 3: Connecting with Claude Desktop
Option 1 β Claude Connectors catalog: In Claude Desktop, go to Settings β Connectors, search for "Brex", and install the connector directly.
Option 2 β Manual configuration: Open the config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Add the following entry:
{
"mcpServers": {
"brex": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.brex.com/mcp"],
"env": {}
}
}
}
Restart Claude Desktop after saving. Node.js v20 or higher is required.
Step 4: Connecting with Cursor
In Cursor, open Settings β MCP and add a new server:
Name: brex
Type: http
URL: https://api.brex.com/mcp
Step 5: Connecting with Codex
codex mcp add brex --url https://api.brex.com/mcp
Step 6: Connecting with Other MCP Clients
Any client that supports MCP HTTP transport can connect directly to https://api.brex.com/mcp. Clients that support OAuth with Dynamic Client Registration (RFC 7591) receive the authorization flow automatically. For other clients, an API key is required.
Step 7: Authentication and Token Management
OAuth (recommended): The authorization server is at https://accounts-api.brex.com/oauth2/default. Sessions remain active; repeated login is generally not required. Active connections can be reviewed and revoked under Settings β Personal settings β Connected integrations in the Brex Dashboard.
API key: Create a new token under Settings β Developer with the minimum necessary scopes. Never store the key in repositories, prompts, or shared config files; use the client's secret management features instead. If you suspect a key has been compromised, revoke it immediately and generate a new one.
Security and Best Practices
Enable human confirmation: For tools that can write (memo updates, receipt uploads, limit assignments), enable a confirmation requirement in client settings.
Minimal scopes: When using API keys, grant only the permissions your use case actually requires.
Monitor activity: Check API Logs in the Brex Dashboard regularly to review which tools have been called.
Mind the data path: Tool responses leave Brex and reach the AI client and its model provider. Financially sensitive data (transaction details, expenses, employee data) should never be unnecessarily exposed in prompts or tool calls.
Available Tools at a Glance
After connecting, tools available include: filtering and analyzing expenses, uploading receipts, viewing cards, browsing banking transactions, managing bills and vendors, listing trips and bookings, and accessing accounting records and general ledger accounts. The complete and always-current tool list is in the official documentation at developer.brex.com/docs/mcp.
FAQ
Who needs to activate the MCP Server? An account or card admin must accept the Developer API agreement and enable beta access. After that, all users can connect independently.
Does using the MCP Server cost anything? According to the provider, the MCP Server is available at no extra cost for existing Brex accounts. Any costs depend on the Brex plan, not on MCP access itself.
What happens to my financial data in the AI client? Data returned by the MCP Server is transmitted to the connected client and its model provider. Brex, AI client, and model provider privacy policies all apply simultaneously. Do not embed unnecessary financial data in prompts.
Can I see who used the MCP Server? Yes, the API Logs in the Brex Dashboard allow you to track MCP activity.
Authentication
Not recorded yet.
Required access permissions
Not recorded yet.
Transmitted or stored data
Not recorded yet.
Security risks
Not recorded yet.
License and costs
- License
- Not recorded yet.
- Cost
- free
Alternatives
Not recorded yet.
At a glance
- Provider
- Brex
- Status
- Official server
- Deployment
- Remote
- Current version
- Not recorded yet.
- Last reviewed
- 08.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.
No related guides yet.