How to integrate Brex MCP with Codex

Framework Integration Gradient
Brex Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Brex MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Brex MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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.

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.

Conclusion

You've successfully integrated Brex with Codex using Composio's Rube MCP server. Now you can interact with Brex directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Brex operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Brex operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI 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 Codex?

Yes, you can. Codex 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.