Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Brex MCP Server for Claude

Manage your Brex corporate card and banking account from Claude — expenses, cards, transactions, users, bills, vendors, travel bookings, and spend analytics — with the official Brex remote MCP server.

by Brex·added 2026-06-18·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Each tool requires specific Brex user capabilities — access is constrained by your existing Brex account permissions and team policies.
  • This MCP server provides read and write access to financial data including expenses, cards, and transactions; confirm any write operations before approving.
  • API key auth should use a token scoped to the minimum required permissions; rotate keys regularly from Settings → Developer.

Privacy notes

  • Expense details, card data, banking transactions, user profiles, and vendor information from your Brex workspace are surfaced in Claude's context.
  • OAuth is the recommended authentication method — no API token is stored in your MCP configuration.

Prerequisites

  • A Brex account — authenticate via OAuth (recommended) when prompted, or generate a Bearer API key in Settings → Developer.
  • Permissions in your Brex workspace aligned with the data you need (expenses, cards, banking).
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "brex": {
      "type": "http",
      "url": "https://api.brex.com/mcp"
    }
  }
}

About this resource

Overview

The Brex MCP Server is the official remote Model Context Protocol server from Brex. It connects Claude directly to your Brex corporate card and banking account — expenses, cards, transactions, users, bills, vendors, travel, accounting, and spend analytics — through natural language.

Per Brex's documentation, the MCP server lets you "connect AI assistants like Claude Code, Codex, or Cursor directly to your Brex account" to ask questions like "What did the engineering team spend on SaaS last month?" without leaving your IDE.

Authentication uses OAuth (recommended) or a Brex API key. Tool access is governed by your existing Brex account permissions.

Key capabilities

  • Expense analysis — query expenses, filter by date/amount/merchant, identify missing receipts.
  • Card management — retrieve card details and spend limits.
  • Banking — monitor account balances and review banking transactions.
  • Vendor management — look up vendors, view bills and purchase orders.
  • Travel — access booking information and policy compliance details.
  • Accounting — check GL account integrations and accounting records.
  • Administration — search users, departments, and cost centers.
  • Reporting — generate and download account statements.

How it compares

Server Expense management Corporate cards Banking Travel Auth
Brex MCP Yes Yes Yes Yes OAuth / API key
Ramp MCP Yes Yes Yes Limited API key
Expensify MCP Yes No No No API key
QuickBooks MCP Yes (via ledger) No No No OAuth

Brex's MCP covers the full corporate spend stack (cards, expenses, banking, travel) in a single server, with OAuth support that requires no manual token management.

Installation

Claude Code (OAuth — recommended)

claude mcp add --transport http brex https://api.brex.com/mcp

Run /mcp in Claude Code to authenticate via OAuth.

Claude Code (API key)

claude mcp add --transport http brex https://api.brex.com/mcp \
  --header "Authorization: Bearer YOUR_BREX_API_KEY"

Generate an API key in Brex → Settings → Developer.

Claude Desktop

{
  "mcpServers": {
    "brex": {
      "type": "http",
      "url": "https://api.brex.com/mcp"
    }
  }
}

Requirements

  • A Brex account with appropriate team member permissions.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • OAuth authentication minimizes credential exposure — no API token required.
  • Tool access is bounded by your Brex account's existing roles and permissions.
  • API keys should be scoped to minimum permissions and rotated regularly.

Source Verification Notes

Verified on 2026-06-18:

  • Brex's MCP blog post at brex.com/journal/brex-mcp-connect-brex-to-ai-tools confirms the hosted endpoint at https://api.brex.com/mcp, OAuth + API key auth, and the expense/card/ banking/travel tool surface.
  • Brex's AI apps support page at brex.com/support/using-brex-in-ai-apps documents the MCP integration's 8 capability categories (expenses, cards, banking, vendors, travel, accounting, administration, reporting) and example natural-language queries.
  • Brex's product announcement at brex.com/product-announcements/access-brex-data-in-ai- assistants covers the Claude Code, Codex, and Cursor integration.
#brex#expense-management#corporate-cards#banking#finance#spend-analytics

Source citations

Add this badge to your README

Show that Brex MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/brex-mcp-server.svg)](https://heyclau.de/entry/mcp/brex-mcp-server)

How it compares

Brex MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldBrex MCP Server for Claude

Manage your Brex corporate card and banking account from Claude — expenses, cards, transactions, users, bills, vendors, travel bookings, and spend analytics — with the official Brex remote MCP server.

Open dossier 		Axiom MCP Server for Claude

Query observability data, manage dashboards, and monitor your systems from Claude — run APL queries against datasets, list metrics, inspect monitors, and retrieve saved queries — with the official Axiom remote MCP server.

Open dossier 		GrowthBook MCP Server for Claude

Manage A/B experiments and feature flags in GrowthBook from Claude — list and create experiments, manage feature flags, check experiment results, and interact with your GrowthBook workspace — with the official GrowthBook MCP server.

Open dossier 		Mixpanel MCP Server for Claude

Query Mixpanel analytics data from Claude — run insights, funnels, flows, retention analysis, manage dashboards, explore events and properties, run experiments, and analyze session replays — with the official Mixpanel remote MCP server.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorBrexAxiom, Inc.GrowthBookMixpanel
Added2026-06-182026-06-182026-06-182026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Each tool requires specific Brex user capabilities — access is constrained by your existing Brex account permissions and team policies. This MCP server provides read and write access to financial data including expenses, cards, and transactions; confirm any write operations before approving. API key auth should use a token scoped to the minimum required permissions; rotate keys regularly from Settings → Developer.✓The MCP server includes dashboard management tools (create, update, delete) — review any write operations before confirming. APL queries run against live datasets; complex queries over large time windows may be slow or consume significant dataset quota.✓`create_experiment` and `create_feature` write to your GrowthBook workspace — capabilities are scoped by your API key/PAT permissions. Creating experiments or feature flags may immediately affect production if they are in a live environment — review before confirming.✓The server is hosted by Mixpanel and authenticated via OAuth — your existing Mixpanel project permissions are automatically applied. The MCP server grants read and write access to your Mixpanel project; it can create and modify dashboards, reports, and feature flags. Treat Service Account credentials as secrets; do not commit them to repositories.
Privacy notes✓Expense details, card data, banking transactions, user profiles, and vendor information from your Brex workspace are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration.✓Log data, traces, metrics, and monitor configurations from your Axiom datasets and organization are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration.✓Experiment configurations, feature flag definitions, targeting rules, and experiment results from your GrowthBook workspace are surfaced in Claude's context. Your `GB_API_KEY` is a secret — store it as an environment variable, not in version-controlled config files.✓Queries and analytics results (event data, user properties, funnel metrics) are sent through Mixpanel's hosted MCP infrastructure. Session replay summaries and user segment data may surface in Claude's context — treat these as sensitive product analytics.
Prerequisites
  • A Brex account — authenticate via OAuth (recommended) when prompted, or generate a Bearer API key in Settings → Developer.
  • Permissions in your Brex workspace aligned with the data you need (expenses, cards, banking).
  • An MCP client such as Claude Code or Claude Desktop.
  • An Axiom account — authenticate via OAuth when prompted in Claude Code, or generate an API token in Axiom settings.
  • An MCP client such as Claude Code or Claude Desktop.
  • A GrowthBook account (cloud at growthbook.io or self-hosted).
  • A GrowthBook API key (from API Keys settings or a Personal Access Token with appropriate permissions).
  • Your GrowthBook account email (used when creating experiments and feature flags).
  • Node.js with `npx` available.
  • A Mixpanel account — authenticate via OAuth when prompted on first tool use.
  • EU customers should use `https://mcp-eu.mixpanel.com/mcp`; India customers `https://mcp-in.mixpanel.com/mcp`.
  • Service Account credentials (Beta) are available for headless/CI use.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add --transport http brex https://api.brex.com/mcp
claude mcp add --transport http axiom https://mcp.axiom.co/mcp
claude mcp add growthbook -e GB_API_KEY=your-api-key -e GB_EMAIL=you@example.com -- npx @growthbook/growthbook-mcp
claude mcp add --transport http mixpanel https://mcp.mixpanel.com/mcp
Config
{
  "mcpServers": {
    "brex": {
      "type": "http",
      "url": "https://api.brex.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "axiom": {
      "type": "http",
      "url": "https://mcp.axiom.co/mcp"
    }
  }
}
{
  "mcpServers": {
    "growthbook": {
      "command": "npx",
      "args": ["@growthbook/growthbook-mcp"],
      "env": {
        "GB_API_KEY": "your-api-key",
        "GB_EMAIL": "you@example.com",
        "GB_API_URL": "https://api.growthbook.io",
        "GB_APP_ORIGIN": "https://app.growthbook.io"
      }
    }
  }
}
{
  "mcpServers": {
    "mixpanel": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.mixpanel.com/mcp"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.