home / skills / composiohq / awesome-claude-skills / btcpay-server-automation

btcpay-server-automation skill

safe

/btcpay-server-automation

This skill automates Btcpay Server tasks via Composio using Rube MCP, ensuring up-to-date tool schemas and validated connections before workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill btcpay-server-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: btcpay-server-automation
description: "Automate Btcpay Server tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Btcpay Server Automation via Rube MCP

Automate Btcpay Server operations through Composio's Btcpay Server toolkit via Rube MCP.

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

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Btcpay Server connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `btcpay_server`
- 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 `btcpay_server`
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: "Btcpay Server 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 Btcpay Server task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["btcpay_server"]
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 Btcpay Server-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `btcpay_server` |
| 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 Btcpay Server tasks by orchestrating Composio’s btcpay_server toolkit via a Rube MCP connection. It guides discovery of current tool schemas, manages the connection lifecycle, and executes toolkit operations reliably. The workflow focuses on always searching tools first and validating connection status before execution.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available tools, input schemas, and recommended execution plans. It verifies and manages the btcpay_server connection with RUBE_MANAGE_CONNECTIONS, then runs toolkit operations through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs). The skill enforces schema compliance, session reuse, and inclusion of the memory parameter to ensure consistent runs.

When to use it

Automating invoice creation, refund processing, or wallet tasks on a Btcpay Server
Running repeatable maintenance or bulk operations against Btcpay Server
Integrating Btcpay Server actions into larger agent workflows or CI pipelines
When tool schemas may change frequently and you need safe discovery-before-execution
When you need programmatic control of connection/auth flow for multiple servers

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas
Verify RUBE_MANAGE_CONNECTIONS returns ACTIVE for btcpay_server before running tools
Supply exact field names and types from the discovered schemas; do not hardcode arguments
Include a memory object (can be empty {}) in every RUBE_MULTI_EXECUTE_TOOL call
Reuse the same session_id within a workflow; generate a new session for new workflows
Check for pagination tokens in search responses and continue fetching until complete

Example use cases

Discover and run a tool to create a new invoice using schema-compliant arguments
Check connection status and open an auth link when a btcpay_server connection is not ACTIVE
Run bulk wallet or invoice operations via RUBE_REMOTE_WORKBENCH using run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS for advanced integrations or validation
Automate refund processing as part of an agent workflow that first confirms tool availability and connection

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.

What if a tool slug or schema changes?

Always call RUBE_SEARCH_TOOLS at the start of each workflow to get the current slugs and input schemas; never hardcode them.

What happens if the connection is not ACTIVE?

RUBE_MANAGE_CONNECTIONS returns an auth link or instructions—follow them to complete setup, then confirm the connection shows ACTIVE before executing tools.