How to integrate Brex MCP with Claude Code

Framework Integration Gradient
Brex Logo
Claude Code Logo
divider

Introduction

Manage your Brex directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Brex to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Brex.

Rube connected successfully

Supported Tools & Triggers

Tools
Create BudgetCreate a new budget for departments or projects.
Create CardCreate a new card and assign it to a user.
Create DepartmentCreate a new department.
Create ExpenseCreate a new expense.
Create LocationCreate a new location.
Create Job TitleCreate a new job title.
Create UserCreate a new user in the brex account.
Create Vendor CardCreate a new vendor card.
Get Account DetailsGet details about the current brex account.
Get Account StatementsGet account statements.
Get Budget DetailsGet detailed information about a specific budget.
Get Budget TransactionsGet transactions for a specific budget.
Get Card DetailsGet detailed information about a specific card.
Get Card TransactionsGet card transactions for a date range.
Get Company Cash AccountsGet company cash accounts.
Get Expense DetailsGet details of a specific expense.
Get ExpensesGet expenses for a date range.
Get Spend LimitsGet spend limits configuration.
Get Transaction by IDGet details of a specific transaction by id.
Get TransactionsGet transactions for a date range.
Get Transactions by Amount RangeGet transactions filtered by amount range.
Get Transactions by DescriptionGet transactions filtered by description text.
Get User ProfileGet user profile information for current or specified user.
List BudgetsList all budgets and show available amounts across all cards.
List CardsList all cards associated with the account.
List DepartmentsList all departments in the organization.
List LocationsList all locations in the organization.
List Job TitlesList all job titles in the organization.
List UsersList all users in the brex account.
List VendorsList all vendors.
Transfer CardTransfer a card to a different user.
Update BudgetUpdate budget details.
Update Card LimitsUpdate spending limits and controls for a card.
Update Card StatusUpdate the status of a card (activate/deactivate/terminate).
Update UserUpdate user details.

What is the Brex MCP server, and what's possible with it?

The Brex MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Brex account. It provides structured and secure access to your company's financial tools, so your agent can perform actions like managing cards, tracking expenses, creating budgets, and retrieving account details on your behalf.

  • Card creation and management: Instantly issue new cards, assign them to users or vendors, and control spending limits via your agent.
  • Automated expense tracking: Let your agent create and log expenses, helping you keep company finances organized and up to date.
  • Budget and department setup: Quickly create budgets for teams or projects and set up new departments without manual effort.
  • Account and statement retrieval: Fetch detailed account information and download statements whenever you need financial insights or records.
  • User and location management: Add new users or locations to your Brex account, making it easy to scale as your business grows.

Connecting Brex via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Brex) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Brex account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["brex"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http brex-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Brex. This URL will be used to connect Claude Code to Brex.

What's happening:

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Brex
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Brex MCP to Claude Code

bash
claude mcp add --transport http brex-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (brex-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Brex MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your brex-composio entry in the list
  • This confirms that Claude Code can now access Brex tools

If everything is wired up, you should see your brex-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Brex

The first time you try to use Brex tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Brex
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Brex authorization flow
  • Return to the terminal and start using Brex through Claude Code

Once authenticated, you can ask Claude Code to perform Brex operations in natural language. For example:

  • "Create a new card for our intern"
  • "Get the latest account statement PDF"
  • "Add an expense for last week's conference"

Complete Code

Here's the complete code to get you started with Brex and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["brex"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http brex-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Brex with Claude Code using Composio's MCP server. Now you can interact with Brex directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Brex operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Brex operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Brex MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Brex MCP?

With a standalone Brex MCP server, the agents and LLMs can only access a fixed set of Brex tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Brex and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Brex tools.

Can I manage the permissions and scopes for Brex while using Tool Router?

Yes, absolutely. You can configure which Brex scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Brex data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.