Brex MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port number for the server | 3000 |
| NODE_ENV | No | The Node.js environment | development |
| LOG_LEVEL | No | The logging level | info |
| BREX_API_KEY | Yes | Your Brex API access token | |
| BREX_API_URL | No | The Brex API URL | https://platform.brexapis.com |
| RATE_LIMIT_REQUESTS | No | The maximum number of requests allowed within the rate limit window | 1000 |
| RATE_LIMIT_WINDOW_MS | No | The time window in milliseconds for rate limiting | 60000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transactionsC | Get transactions for a Brex account |
| get_expensesC | Get expenses from Brex |
| get_account_detailsC | Get detailed information about a Brex account |
| upload_receiptC | Upload a receipt image to match with expenses |
| match_receiptA | Create a pre-signed URL for uploading a receipt that will be automatically matched with existing expenses |
| update_expenseC | Update an existing card expense |
| get_all_accountsB | Get all Brex accounts with pagination support |
| get_all_expensesC | Get all Brex expenses with pagination and filtering support |
| get_all_card_expensesC | Get all Brex card expenses with pagination and filtering support |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_transactions | Summarize transactions for a Brex account |
| summarize_expenses | Summarize expenses by category and status |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Brex Accounts | List of all Brex accounts |
| Brex Card Accounts | List of all Brex card accounts |
| Brex Cash Accounts | List of all Brex cash accounts |
| Brex Primary Cash Account | Brex primary cash account details |
| Brex Card Transactions | List of all Brex card transactions |
| Brex Expenses | List of all Brex expenses |
| Brex Card Expenses | List of all Brex card expenses |
| Brex Budgets | List of all Brex budgets |
| Brex Spend Limits | List of all Brex spend limits |
| Brex Budget Programs | List of all Brex budget programs |
TDQS
Scored across 9 tools
The tools have some clear distinctions, such as between get_all_accounts and get_account_details, but there is significant overlap between get_all_expenses, get_all_card_expenses, and get_expenses, which could confuse an agent about which to use for expense retrieval. The match_receipt and upload_receipt tools also have related purposes, though their descriptions help differentiate them slightly.
Most tools follow a consistent verb_noun pattern (e.g., get_account_details, update_expense, upload_receipt), with clear verbs like 'get', 'match', 'update', and 'upload'. The only minor deviation is get_all_accounts vs. get_account_details, but overall the naming is predictable and readable across the set.
With 9 tools, the server is well-scoped for managing Brex accounts, expenses, and receipts. This count is appropriate for the financial domain, covering core operations without being overwhelming, and each tool appears to serve a distinct function in the workflow.
The tool set covers key areas like account retrieval, expense management, and receipt handling, with good CRUD-like operations (e.g., get, update). However, there are minor gaps, such as no tool for creating new expenses or deleting data, which might limit full lifecycle management, but agents can likely work around these for common tasks.