# How to connect Brex to Hermes Agent (paste one key, 84 tools) > Connect Brex to Hermes 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/hermes/brex Most guides for giving Hermes Agent Brex access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Brex setup: pair once in the browser and your always-on Hermes agent can act on Brex for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Brex. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Brex** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Brex in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Brex API key once. Verify the connection by asking Hermes: > Pull the relevant data from Brex, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes 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 Hermes Looking for a Brex MCP server for Hermes Agent? ClawLink connects Brex to Hermes Agent 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 OpenClaw instead? The [OpenClaw Brex integration](https://claw-link.dev/openclaw/brex) works the same way. ## What the Hermes Agent Brex integration can do 84 Brex tools are ready for Hermes Agent 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 Hermes | 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 Hermes Agent. 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 Hermes Agent 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. ### Hermes paired but still can't use Brex Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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 Hermes Agent Brex integration? Yes. ClawLink is the fastest way to connect Hermes to Brex: link your Brex account once in the browser and Hermes Agent can call the Brex API through 84 ready-made tools — no custom code or token handling. ### How do I connect Brex to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Brex in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Brex in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Brex working from chat. ### Hermes paired but still can't use Brex Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Stripe tools](https://claw-link.dev/hermes/stripe) — Manage payments, customers, and invoices - [Zoho Books](https://claw-link.dev/hermes/zoho-books) — Organize finances, invoices, bills, and accounting - [Connect Ramp](https://claw-link.dev/hermes/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts