Brex

Provides access to Brex data (accounts, expenses, budgets, team) via MCP with receipt and expense tools.

typescript

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-crazyrabbitltc_mcp-brex-server": {
      "command": "node",
      "args": [
        "/path/to/brex-mcp-server/build/index.js"
      ],
      "env": {
        "PORT": "3000",
        "NODE_ENV": "development",
        "LOG_LEVEL": "info",
        "BREX_API_KEY": "YOUR_BREX_API_KEY",
        "BREX_API_URL": "https://platform.brexapis.com",
        "RATE_LIMIT_REQUESTS": "1000",
        "RATE_LIMIT_WINDOW_MS": "60000"
      }
    }
  }
}

You can bridge AI agents with the Brex financial platform through this MCP server. It exposes financial data and resources via standardized MCP handlers and tools, enabling secure, read-only access to accounts, expenses, budgets, and team information while providing convenient receipts and expense management capabilities.

How to use

You connect an MCP client to the Brex MCP server to retrieve account details, list and inspect expenses, view budgets and spend limits, and manage receipts. Use the provided tools to match and upload receipts, and to read or update non-sensitive expense details. All interactions are designed to be read-only for sensitive financial resources, with explicit tools available for querying and updating specific expense data.

How to install

Prerequisites: Node.js v18 or higher and a Brex API access token.

Clone the Brex MCP server repository and navigate into it.
Install dependencies.
Create a .env file with your Brex API token and connection details.
Build the server.

Additional configuration and runtime guidance

To run the Brex MCP server locally and integrate it with Claude Desktop, you configure an MCP entry that launches the server as a local process and passes environment variables. The server run command starts the Node process pointing at the built index file, with your Brex API credentials and runtime settings supplied via environment variables.

Security and usage notes

Access is designed to be read-only for sensitive financial resources where appropriate. No API credentials are stored in the codebase. Rate limiting and robust error handling help guard usage. Ensure you protect your API key and restrict client access to authorized workflows.

Available tools

match_receipt

Match a receipt with an existing expense to associate the receipt with the correct transaction.

upload_receipt

Upload a receipt image or file and attach it to a specific expense.

update_expense

Update details for a card expense, including memo and category.

get_all_expenses

Fetch all expenses with optional filters and expanded merchant/budget information.

get_all_card_expenses

Fetch all card expenses with optional filters and expanded merchant/budget information.

Built by

VeilStrat

AI signals for GTM teams