What is this skill for?

It automates BTCPay Server tasks using the Rube MCP toolkit, always discovering current tool schemas before acting.

Do I need to hardcode tool slugs?

No. Always fetch schemas with RUBE_SEARCH_TOOLS to obtain up-to-date tool slugs and required arguments.

Why is memory required in executions?

Memory is required in RUBE_MULTI_EXECUTE_TOOL calls to preserve context and support multi-step workflows.

btcpay-server-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/btcpay-server-automation --openclaw

Files (1)

SKILL.md

2.9 KB

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

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit btcpay_server
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: "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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/btcpay-server-automation/SKILL.md

View on GitHub

Overview

This skill automates BTCPay Server operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first to avoid hardcoding slugs or arguments and to keep workflows up to date with tool changes.

How This Skill Works

Connect to Rube MCP and the BTCPay Server toolkit, then discover available tools with RUBE_SEARCH_TOOLS. Verify the connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the exact schema fields returned. Always include a memory object and reuse session IDs when appropriate.

When to Use It

When automating recurring BTCPay Server tasks and you need up-to-date tool schemas
When establishing a new BTCPay automation workflow and validating an ACTIVE connection
When executing a discovered BTCPay tool to perform a specific operation with schema-compliant arguments
When tool schemas change and you must refresh slugs/arguments before running workflows
When performing multi-step BTCPay tasks and ensuring session continuity across steps

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client; ensure RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit: ['btcpay_server']; complete auth if prompted
Step 3: Use the Core Workflow Pattern: discover tools with RUBE_SEARCH_TOOLS, confirm ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory: {} and your session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool slugs and schemas
Verify the BTCPay connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from the tool schemas; never hardcode slugs or args
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session_id within a workflow and regenerate only for new workflows; watch for pagination in tool listings

Example Use Cases

Create an invoice in BTCPay Server by discovering the invoice tool and executing with dynamic arguments
Poll BTCPay payments and automatically update a dashboard or CRM when statuses change
Run bulk BTCPay operations via RUBE_REMOTE_WORKBENCH using run_composio_tool() to process multiple tasks
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to ensure downstream workflows stay compatible
Establish and maintain an ACTIVE btcpay_server connection across a multi-step automation workflow

Frequently Asked Questions

Add this skill to your agents