Brex icon

CONNECT APP

Build with Brex

Payments, Deposits, Cards

Business Management

  • OAuth

MCP

Give your agent Brex tools

Every Brex action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Brex account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "brex",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run Cancel Card:
const result = await mcp.callTool({
  name: "brex-cancel-card",
  arguments: {
    cardId: "Card ID",
    reason: "Reason",
  },
})

API PROXY

Call the Brex API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Brex API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://platform.brexapis.com/v2/cards",
})

// Any allowed Brex endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run Brex actions from your backend

Connect a user's Brex account once, then run Cancel Card on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "brex-cancel-card",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    brex: { authProvisionId: "apn_xxxxxxx" },
    cardId: "Card ID",
    reason: "Reason",
  },
})

TOOLS

Brex actions

On-demand operations your product or agent can configure and run on behalf of a connected user.

REFERENCE

App details

Reference metadata for the Brex connector in the Pipedream registry.

App slug
brex
Authentication
OAuth
Categories
Business Management
Actions
21
Triggers
1
API proxy
Available

OAuth scopes

These are the scopes Pipedream's managed Brex OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.

  • openid
  • offline_access
  • users
  • cards
  • locations
  • departments
  • vendors
  • transactions.card.readonly
  • transactions.cash.readonly
  • accounts.cash.readonly
  • transfers
  • https://onboarding.brexapis.com/referrals
  • budgets