# How to connect Brex to OpenClaw (paste one key, 84 tools) > Connect Brex to OpenClaw with ClawLink: paste your Brex key once and 84 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/brex The usual route to Brex access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Brex setup: install one ClawHub skill, connect Brex in the browser, and OpenClaw can call real Brex actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Brex. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Brex** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect brex # connect Brex (browser OAuth) npx -y @useclawlink/cli actions brex # list available actions npx -y @useclawlink/cli run brex --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Brex in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Brex API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Brex, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Brex is connected in the dashboard, that agent calls the same 84 Brex tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Brex MCP for OpenClaw Looking for a Brex MCP server for OpenClaw? ClawLink connects Brex to OpenClaw and exposes 84 Brex tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Brex integration](https://claw-link.dev/hermes/brex) works the same way. ## What the OpenClaw Brex integration can do 84 Brex tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 84. ### 30 of 84 Brex tools for OpenClaw | Tool | What it does | |---|---| | **Get account statements** `brex_get_account_statements` | Get finalized statements for the primary cash account | | **Get budget details** `brex_get_budget_details` | Get detailed information about a specific budget | | **Get card details** `brex_get_card_details` | Get detailed information about a specific card | | **Get card expense** `brex_get_card_expense` | Retrieve detailed information about a specific card expense by its ID | | **Get card number** `brex_get_card_number` | Get card number, CVV, and expiration date for a specific card | | **Get card transactions** `brex_get_card_transactions` | Get settled card transactions for the primary card account | | **Get company cash accounts** `brex_get_company_cash_accounts` | Retrieve all cash (deposit) accounts for the company | | **Get company details** `brex_get_company_details` | Get company information associated with the OAuth2 access token | | **Get department by ID** `brex_get_department_by_id` | Get detailed information about a specific department by ID | | **Get expense** `brex_get_expense` | Get details of a specific expense by ID | | **Get field by ID** `brex_get_field_by_id` | Retrieve a custom field by its Brex ID | | **Get field value by ID** `brex_get_field_value_by_id` | Retrieve a specific field value by field ID and field value ID | | **Get legal entity** `brex_get_legal_entity` | Retrieve a legal entity by its ID from Brex | | **Get location by ID** `brex_get_location_by_id` | Get detailed information about a specific location by ID | | **Get referral** `brex_get_referral` | Retrieve a specific referral by its ID from Brex | | **Get spend limit by ID** `brex_get_spend_limit_by_id` | Get detailed information about a specific spend limit by its ID | | **Get spend limits** `brex_get_spend_limits` | Get spend limits configuration | | **Get title by ID** `brex_get_title_by_id` | Get detailed information about a specific job title by ID | | **Get transaction by ID** `brex_get_transaction_by_id` | Get details of a specific transaction by ID | | **Get transactions** `brex_get_transactions` | Get card transactions from the primary Brex account | | **Get transactions by amount range** `brex_get_transactions_by_amount_range` | Get card transactions filtered by amount range and date period | | **Get transactions by description** `brex_get_transactions_by_description` | Search and filter card transactions by description text | | **Get user limit** `brex_get_user_limit` | Retrieves the monthly spending limit and available balance for a specific Brex user | | **Get user profile** `brex_get_user_profile` | Get user profile information from Brex Team API | | **Get vendor by ID** `brex_get_vendor_by_id` | Get vendor details by ID | | **Get webhook group** `brex_get_webhook_group` | Retrieve details of a specific webhook group by ID | | **Get webhook subscription** `brex_get_webhook_subscription` | Retrieve details of a specific webhook subscription by ID | | **List budget programs** `brex_list_budget_programs` | List all budget programs in the organization | | **List budgets** `brex_list_budgets` | List all budgets and show available amounts across all cards | | **List card accounts** `brex_list_card_accounts` | List all card accounts for the company | ## Example prompts **Get Account Statements** > Pull the relevant data from Brex, summarize it in plain English, and point out anything that needs attention. **Get Budget Details** > Pull the relevant data from Brex, summarize it in plain English, and point out anything that needs attention. **Get Card Details** > Pull the relevant data from Brex, summarize it in plain English, and point out anything that needs attention. **Get Card Expense** > Pull the relevant data from Brex, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Brex working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Brex API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Brex account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Brex. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Brex actions to the runtime in a format your agent can reliably use. | 84 tools for Brex are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Brex to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Brex in the browser, and the 84 tools above work from chat. There is no SDK and no config file, and the Brex key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Brex skill but can't call the tools The ClawHub skill teaches OpenClaw about Brex, but the calls run through the ClawLink plugin and your connected account. Make sure Brex is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Brex from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Brex tools Brex tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Brex call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Brex returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Brex has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Brex integration? Yes. ClawLink is the fastest way to connect OpenClaw to Brex: link your Brex account once in the browser and OpenClaw can call the Brex API through 84 ready-made tools — no custom code or token handling. ### How do I add Brex to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Brex skill from ClawHub, then you click Connect in the dashboard to authorize Brex. OpenClaw calls the tools from the next message — no config files, and the Brex key you paste is stored server-side instead of in your environment. ### How long does it take to connect Brex to OpenClaw? About two minutes. Sign in, click Connect next to Brex in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Brex up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Brex working from chat. ### OpenClaw installed the Brex skill but can't call the tools The ClawHub skill teaches OpenClaw about Brex, but the calls run through the ClawLink plugin and your connected account. Make sure Brex is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Stripe tools](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices - [Zoho Books](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [Ramp](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts