Brex

@brex show me all active cards and their spending limits for the engineering department

Based on your Brex account, the engineering department currently has 8 active cards. Here's a summary: 5 employee cards with individual $5,000 monthly limits (assigned to Sarah Chen, Marcus Rodriguez, Priya Patel, James Kim, and Alex Thompson), 2 vendor cards for AWS ($50,000/month) and GitHub ($2,000/month), and 1 team card for miscellaneous tools ($3,000/month). Total allocated monthly spend capacity for engineering is $77,000. All cards are within their current billing cycle limits.

This read-heavy example demonstrates Brex's card management visibility. Requires OAuth scopes for reading card and department data. The actual response structure depends on your account's organizational hierarchy and card configuration—teams with hundreds of cards may want to filter by user or date range.

@brex create a new vendor card for Vercel with a $10,000 monthly limit and assign it to the infrastructure budget

I've created a new vendor card in your Brex account with the following details: Card name 'Vercel', monthly spending limit $10,000, assigned to the Infrastructure budget category. The virtual card number has been generated and is ready for use. The card will automatically decline transactions that would exceed the monthly limit, and all charges will appear in your Brex dashboard under Infrastructure expenses. You can share the card details with your team through Brex's secure sharing features.

This write example shows Brex's programmatic card provisioning—useful for quickly spinning up vendor accounts without manual dashboard work. Requires OAuth scopes for creating cards and modifying budgets. Be aware this creates a real, active card in your account; the MCP cannot reverse this action, so verify limits before confirming.

@brex analyze our Q4 expenses by department and suggest three budget adjustments for next quarter based on spending patterns

Reviewing your Q4 Brex expenses across all departments: Engineering spent 94% of budget ($282k of $300k allocated), primarily on cloud infrastructure. Marketing spent 67% ($100k of $150k), with significant underspend in events. Operations exceeded budget by 12% ($112k of $100k), driven by unexpected software renewals. Suggested adjustments: (1) Increase engineering budget to $320k to accommodate growth in AWS costs, (2) Reallocate $30k from marketing events to operations software category, (3) Create a $15k contingency budget for mid-year software renewals to prevent future overages.

This synthesis example pairs Brex's expense data with AI reasoning to surface actionable insights. The AI interprets spending patterns but cannot directly modify budgets—you'll need to approve and execute changes. Most valuable when you have 2+ months of transaction history; newer accounts may lack sufficient data for meaningful pattern analysis.

When Brex MCP beats manual card provisioning for contractors

An 8-person startup hires three contractors for a 90-day design sprint. The founder needs to issue cards, set spend limits, and create budget buckets without logging into Brex's dashboard between Slack pings. The Brex MCP wins here because it exposes Create Card, Create Budget, and Create User in one OAuth flow—your AI can provision a contractor's $2k/month card and tie it to the 'Q1 Design' budget in a single prompt. The trade-off: if you're only onboarding one person per quarter, the OAuth setup (which requires a Brex admin to authorize scopes) takes longer than clicking through the web UI. But at two or more hires per month, the MCP pays for itself by letting non-finance teammates request cards through Switchy without waiting on the CFO.

Why Brex MCP matters when your team spans four locations

A 15-person agency has offices in Austin, Denver, Portland, and remote. Finance closes the books on the 5th of each month and needs to reconcile expenses by location and department. The Brex MCP's Create Location and Create Department tools let the ops lead build a location-tagged expense view inside Switchy without exporting CSVs or writing Zapier glue. The AI can pull expenses, group by location, and flag outliers (like a $900 software charge in the Portland bucket when that office has no eng headcount). This works cleanly up to about 50 expenses per location per month; beyond that, you're better off using Brex's native reporting or a BI tool. If your reconciliation is mostly 'did we stay under budget,' the MCP is the fastest path from question to answer.

When Create Vendor Card replaces spreadsheet-based SaaS tracking

A 12-person product team subscribes to 22 SaaS tools (Figma, Linear, Vercel, etc.). The finance lead wants each vendor on its own virtual card so charges are auto-categorized and easy to audit. The Brex MCP's Create Vendor Card tool lets you spin up a card-per-vendor in Switchy by naming the vendor and setting a monthly limit—no need to open Brex, no need to remember which card is Figma vs. Framer. The AI can also create the expense record when a charge posts, tagging it to the right department. The boundary: if you have fewer than 10 vendors, manual card creation is fine. If you have more than 50, you probably want Brex's Vendor Management feature instead of MCP automation. Between 10 and 50, the MCP is the sweet spot for teams who want SaaS spend visible in their AI workspace without building a custom integration.