Connect Brex to Aurora in Finta

Direct answer: Finta's Aurora catalog includes Brex's beta MCP server at https://api.brex.com/mcp with dynamic OAuth. Brex documents read and selected write capabilities for expenses, transactions, cards, limits, banking, vendors, bills, travel, accounting, users, departments, reports, and statements, all constrained by Brex roles and credentials.

This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Brex remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.

Current connection note: Brex documents the same endpoint but currently labels MCP as early access and requires administrator enablement. The page states those prerequisites.

How the Brex connection works

Connection detail	Current Finta guidance
Classification	Catalog MCP
Configured endpoint	https://api.brex.com/mcp
Authentication and transport	Provider OAuth through Aurora; Streamable HTTP
Source of truth	Brex remains authoritative for provider records, permissions, and action results.
Human control	Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution.

What you can use it for

Query authorized expenses, transactions, reimbursements, cards, and spend limits.
Review supported bank balances, vendors, bills, travel, accounting, user, and department context when the role allows it.
Identify missing receipts, memos, policy context, or follow-up items in supported workflows.
Update only the specific expense fields or other resources Brex exposes to the authenticated user.
Use OAuth or appropriately scoped credentials and preserve Brex's role-based access controls.

These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.

Relationship intelligence workflows for Brex

Prepare spend and cash context for a board update

Outcome: Have finance approve the source-linked summary before distribution.

Define the Brex entity, period, currency, and approved questions.
Retrieve relevant balances, transactions, expenses, vendors, bills, or accounting records.
Document pending items, exclusions, policy exceptions, and reconciliation gaps.
Have finance approve the source-linked summary before distribution.

Human decision: Brex operational data does not replace reconciled accounting, audited statements, or finance sign-off.

Review fundraising-event and travel spend

Outcome: Make only an approved update that the connected Brex role permits.

Find the relevant card, trip, booking, expense, and spend-limit records.
Check policy context, receipts, memos, and outstanding review status.
Prepare a follow-up list for the responsible people.
Make only an approved update that the connected Brex role permits.

Human decision: Do not approve expenses, move money, issue cards, or change another person's transactions unless the documented tool and authorized human role explicitly allow it.

How to connect Brex to Aurora

Ask a Brex account admin or card admin to enable Brex in AI assistants under Early Access and accept the Developer API agreement.
In Aurora, open Apps and select Brex.
Authorize https://api.brex.com/mcp with the intended Brex identity and review requested permissions.
Confirm that the user's Brex role exposes only the required resources.
Run a read-only expense, card, or account lookup before any supported write.

Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.

Permissions and approval boundary

Brex MCP is beta and inherits Brex roles and credentials. Use the least access possible and require finance approval for expense edits, limits, cards, banking, bills, reimbursements, or other financial actions. Keep employee, card, banking, and transaction data restricted.

Limitations to understand

Brex MCP is beta or early access and requires Developer API access and admin enablement.
Available tools depend on the user's Brex role, credential scopes, and organization policy.
Brex documents both OAuth and API-token patterns, while the Finta catalog specifies dynamic OAuth.
Some actions, including certain approvals or changes to other users' transactions, remain dashboard-only.
Operational records may be pending or unreconciled and are not audited financial statements.

Verification checklist

Confirm Early Access, Developer API agreement, endpoint, OAuth flow, account, and Brex role.
Capture granted scopes and the exact Aurora-discovered tool inventory.
Run a safe read-only expense, card, or balance lookup and retain the receipt.
Test one permitted low-risk update only after approval and verify Brex's attribution or audit record.
Record beta status, dashboard-only actions, financial disclosure, and verification date.

Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.

Official provider sources

Related Finta guides

Use approved Brex context with Aurora