How to connect BTCPay Server to OpenClaw
Connect BTCPay Server to OpenClaw with ClawLink: paste your BTCPay Server key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.
BTCPay ServerAPI KEYMCPBTCPay Server is a free, open-source, self-hosted Bitcoin payment processor that enables merchants to accept Bitcoin payments without intermediaries.. Once connected, OpenClaw can read and act on BTCPay Server from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to BTCPay Server access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical BTCPay Server setup: install one ClawHub skill, connect BTCPay Server in the browser, and OpenClaw can call real BTCPay Server actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to BTCPay Server.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect BTCPay Server
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with BTCPay Server?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect BTCPay Server in the ClawLink dashboard — paste your BTCPay Server API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from BTCPay Server, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once BTCPay Server is connected in the dashboard, that agent calls the same 16 BTCPay Server tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
BTCPay Server MCP for OpenClaw
Looking for a BTCPay Server MCP server for OpenClaw? ClawLink connects BTCPay Server to OpenClaw and exposes 16 BTCPay Server tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes BTCPay Server integration works the same way.
What the OpenClaw BTCPay Server integration can do
16 BTCPay Server tools are ready for OpenClaw once the account is connected. The 13 below are the ones people reach for most; your agent can call all 16.
13 of 16 BTCPay Server tools for OpenClaw
| Tool | What it does |
|---|---|
Get API keys btcpay_server_get_api_keys | Retrieve information about the current API key |
Get payment requests btcpay_server_get_payment_requests | List all payment requests for a specific store |
Get server info btcpay_server_get_server_info | Retrieve information about the BTCPay Server instance |
Get store btcpay_server_get_store | Retrieves complete configuration and settings for a specific BTCPay Server store by its ID |
Get user btcpay_server_get_user | Retrieve information about a BTCPay Server user by ID or email |
Get webhook btcpay_server_get_webhook | Retrieves detailed configuration of a specific webhook registered for a BTCPay store, including |
Get webhooks btcpay_server_get_webhooks | Lists all webhooks registered for a BTCPay Server store |
List apps btcpay_server_list_apps | Retrieve all apps (Point of Sale, Crowdfund, etc.) associated with a specific BTCPay Server |
Create payment request btcpay_server_create_payment_request | Creates a new payment request in a BTCPay Server store |
Create store btcpay_server_create_store | Create a new store in BTCPay Server |
Create user btcpay_server_create_user | Create a new BTCPay Server user |
Create webhook btcpay_server_create_webhook | Registers a new webhook for a BTCPay store to receive real-time notifications when store events |
Update user btcpay_server_update_user | Update the profile of the currently authenticated BTCPay Server user |
Try it: find the BTCPay Server tool you need
Browse the 13 BTCPay Server tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from BTCPay Server, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from BTCPay Server, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from BTCPay Server, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from BTCPay Server, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want BTCPay Server working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the BTCPay Server API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BTCPay Server account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for BTCPay Server. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right BTCPay Server actions to the runtime in a format your agent can reliably use. | 16 tools for BTCPay Server are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes BTCPay Server to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect BTCPay Server in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the BTCPay Server key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the BTCPay Server skill but can't call the tools
The ClawHub skill teaches OpenClaw about BTCPay Server, but the calls run through the ClawLink plugin and your connected account. Make sure BTCPay Server is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect BTCPay Server from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling BTCPay Server tools
BTCPay Server tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every BTCPay Server call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
BTCPay Server returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for BTCPay Server has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw BTCPay Server integration?
Yes. ClawLink is the fastest way to connect OpenClaw to BTCPay Server: link your BTCPay Server account once in the browser and OpenClaw can call the BTCPay Server API through 16 ready-made tools — no custom code or token handling.
How do I add BTCPay Server to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BTCPay Server skill from ClawHub, then you click Connect in the dashboard to authorize BTCPay Server. OpenClaw calls the tools from the next message — no config files, and the BTCPay Server key you paste is stored server-side instead of in your environment.
How long does it take to connect BTCPay Server to OpenClaw?
About two minutes. Sign in, click Connect next to BTCPay Server in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring BTCPay Server up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want BTCPay Server working from chat.
OpenClaw installed the BTCPay Server skill but can't call the tools
The ClawHub skill teaches OpenClaw about BTCPay Server, but the calls run through the ClawLink plugin and your connected account. Make sure BTCPay Server is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
