home / skills / composiohq / awesome-claude-skills / brex-staging-automation

brex-staging-automation skill

/brex-staging-automation

This skill automates Brex Staging tasks via Rube MCP, ensuring current tool schemas are fetched before execution for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill brex-staging-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.9 KB
---
name: brex-staging-automation
description: "Automate Brex Staging tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Brex Staging Automation via Rube MCP

Automate Brex Staging operations through Composio's Brex Staging toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/brex_staging](https://composio.dev/toolkits/brex_staging)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Brex Staging connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brex_staging`
- Always call `RUBE_SEARCH_TOOLS` first 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brex_staging`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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 Staging 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 Staging task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["brex_staging"]
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_CONNECTIONS` shows ACTIVE status before executing tools
- **Schema compliance**: Use exact field names and types from the search results
- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, 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 Staging-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `brex_staging` |
| 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](https://composio.dev)*

Overview

This skill automates Brex Staging tasks through the Rube MCP using Composio's brex_staging toolkit. It provides a reliable workflow pattern for discovering tools, validating connections, and executing actions while enforcing schema compliance and session management. Always query the MCP for current tool schemas before running any operation.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available Brex Staging tool slugs, input schemas, and recommended plans. It then verifies the Brex Staging connection with RUBE_MANAGE_CONNECTIONS and ensures the connection is ACTIVE. Finally it runs chosen tools via RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk operations), always passing a memory object and a session_id and following the schema fields returned by the search.

When to use it

  • Automating Brex Staging workflows and repetitive staging operations
  • Before running any Brex Staging tool to ensure current schemas and slugs
  • When orchestrating multi-step staging processes that require consistent session state
  • Performing bulk or remote workbench operations against Brex Staging
  • Validating and troubleshooting connections to Brex Staging via Rube MCP

Best practices

  • Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas
  • Call RUBE_MANAGE_CONNECTIONS and confirm the toolkit connection shows ACTIVE before execution
  • Use exact field names and types from the returned schemas; do not hardcode arguments
  • Always include a memory object (can be empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session_id across steps in a single workflow; generate a new session_id for new workflows
  • Handle pagination tokens in search/execute responses and continue fetching until complete

Example use cases

  • Discover a payout simulation tool, then run it with schema-compliant inputs to validate staging payouts
  • Connect an environment, verify ACTIVE status, and run a sequence of tooling to seed test data
  • Run bulk account updates using RUBE_REMOTE_WORKBENCH with run_composio_tool() for high-volume staging changes
  • Automate recurring staging checks: search tools, validate schemas, execute health-check tools, and collect results

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as an MCP server in your client configuration and call the MCP endpoints.

What if a tool schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS before important steps. If a schema changes, update arguments to match the returned schema and restart or adapt the workflow.