$ ~/registry/skill/composiohq-composio-skills-btcpay-server-automation

SKILL

btcpay-server-automation

Name: btcpay-server-automation
Author: Composio

Automate BTCPay Server payment and merchant operations through Rube MCP.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is essentially prompt/documentation for operating through Rube MCP, with no direct indication of local code execution, required secrets, or direct connections to unknown endpoints. The main caution is that it routes operations through a third-party MCP service to manage BTCPay connections, so actual data flows and permission boundaries should be verified on the Rube/Composio side.

CredentialsCaution

The material says 'No API keys needed', but it also requires creating an ACTIVE `btcpay_server` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, which implies BTCPay and/or third-party authorization credentials may still be involved, just not as local environment variables; the credential handling details are not described.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to discover tools, manage connections, and execute BTCPay operations; therefore user requests, session IDs, tool arguments, and possibly BTCPay business data may transit through that third-party service. No unrelated or obviously suspicious egress endpoint is stated, but third-party routing warrants caution.

Code executionLow risk

The system marks it as `prompt-only`, and the material itself is limited to workflow guidance and tool-calling patterns, with no described local binary execution, shell commands, or extra system privilege requests. Based on this skill material alone, it does not include local code execution capability.

Data accessCaution

The skill is intended to 'Automate Btcpay Server operations' and supports executing discovered BTCPay tools, bulk operations, and paginated retrieval, indicating indirect access to BTCPay account/store-related data and administrative actions. It does not state local file read/write or obvious overbroad host permissions, but it also does not detail the exact scope of accessible BTCPay resources.

Supply chainLow risk

The source is an open GitHub repository, the system marks it as `open-source`, and it has strong community trust (64.7k stars), all of which are significant risk-reducing factors. The current material is mainly README/skill description rather than an executable payload; gaps remain because the license is unspecified and maintenance status is unknown, so the upstream Rube/Composio components should be further checked before real use.

Recommendations

Before connecting, verify the privacy policy, log retention, and data handling of `rube.app/mcp`, including whether BTCPay data is proxied or stored by the third party.
Grant only the minimum required permissions to the `btcpay_server` connection, and test first in a low-sensitivity or sandbox store.
Review tool schemas and arguments manually before using `RUBE_MULTI_EXECUTE_TOOL`, especially to avoid bulk or destructive actions on production BTCPay resources.
Check the upstream Rube/Composio repositories, maintenance activity, and auth documentation to confirm where connection credentials are stored and how they can be revoked.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "btcpay-server-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/btcpay-server-automation/SKILL.md
2. Save it as ~/.claude/skills/btcpay-server-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Botstar workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_