Skip to main content
Glama
MCP-Mirror
by MCP-Mirror

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoThe port number for the server3000
NODE_ENVNoThe Node.js environmentdevelopment
LOG_LEVELNoThe logging levelinfo
BREX_API_KEYYesYour Brex API access token
BREX_API_URLNoThe Brex API URLhttps://platform.brexapis.com
RATE_LIMIT_REQUESTSNoThe maximum number of requests allowed within the rate limit window1000
RATE_LIMIT_WINDOW_MSNoThe time window in milliseconds for rate limiting60000

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

NameDescription
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

NameDescription
summarize_transactionsSummarize transactions for a Brex account
summarize_expensesSummarize expenses by category and status

Resources

Contextual data attached and managed by the client

NameDescription
Brex AccountsList of all Brex accounts
Brex Card AccountsList of all Brex card accounts
Brex Cash AccountsList of all Brex cash accounts
Brex Primary Cash AccountBrex primary cash account details
Brex Card TransactionsList of all Brex card transactions
Brex ExpensesList of all Brex expenses
Brex Card ExpensesList of all Brex card expenses
Brex BudgetsList of all Brex budgets
Brex Spend LimitsList of all Brex spend limits
Brex Budget ProgramsList of all Brex budget programs

TDQS

B3.1/5.0

Scored across 9 tools

Disambiguation3/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.