Brex MCP Server
Connect Brex to your AI agents with the Brex MCP server.
Updated
What is Brex MCP?
The Brex MCP server is a Model Context Protocol server that connects Brex to AI agents and assistants as a set of tools. With it connected, an agent can work with Brex (corporate cards and spend management — expenses, budgets, and transactions) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Brex tools become available to the model.
Connect the Brex MCP server
Connect Brex MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Brex MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Brex tool to confirm the connection is live.
Connect Brex MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Brex
Provide the Brex MCP server URL or command and complete authentication.
- 3
Test
Reference Brex from chat to confirm Cursor can reach the tools.
Using Brex MCP with Gamut
On Gamut, the Brex MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Brex and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Brex MCP server?
It is a Model Context Protocol server that exposes Brex to AI agents as tools so they can work with it (corporate cards and spend management — expenses, budgets, and transactions).
How do I connect the Brex MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Brex MCP server URL and complete authentication (OAuth). See the official documentation for the exact URL and scopes.
Can I use Brex MCP with Gamut?
Yes — Gamut supports the Brex MCP server, so your agents can use it as a tool in automated, triggered workflows.