Brex Automation via Rube MCP
SkillSearchbrex-automation lets your AI handle everyday Brex finance work for you, such as managing company cards and keeping expenses in order. Once added, your AI can carry out these tasks through the connected tools it uses, checking what is available first so each action is done the right way.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill, then ask your AI which Brex tasks it can take off your plate. It will check the connected tools first to see exactly what it can do before completing anything.
Then ask your AI: use the Brex Automation via Rube MCP skill
What your AI can do with it
- Manage your Brex cards on request
- Take care of expense tasks in Brex
- Automate routine Brex finance work instead of doing it by hand
- Check the current setup for each task before acting so it runs correctly
What this skill tells your AI
The instructions your AI receives, as published by composiohq/awesome-claude-skills in composio-skills/brex-automation/SKILL.md and read by ahel’s review.
Automate Brex operations through Composio's Brex toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/brex
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Brex connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbrex - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitbrex - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Brex operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Brex task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["brex"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Brex-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit brex |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Signals
- GitHub stars
- 75k
- Forks
- 9k
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
brex-automation- Source
- github.com/composiohq/awesome-claude-skills