How to connect BTCPay Server to Hermes Agent
Connect BTCPay Server to Hermes 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, Hermes Agent can read and act on BTCPay Server from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent BTCPay Server access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical BTCPay Server setup: pair once in the browser and your always-on Hermes agent can act on BTCPay Server for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to BTCPay Server.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect BTCPay Server
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with BTCPay Server?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect BTCPay Server in the ClawLink dashboard — paste your BTCPay Server API key once.
Verify the connection by asking Hermes:
Pull the relevant data from BTCPay Server, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes 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 Hermes
Looking for a BTCPay Server MCP server for Hermes Agent? ClawLink connects BTCPay Server to Hermes Agent and exposes 16 BTCPay Server tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw BTCPay Server integration works the same way.
What the Hermes Agent BTCPay Server integration can do
16 BTCPay Server tools are ready for Hermes Agent 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 Hermes
| 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 Hermes 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 Hermes Agent. 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 Hermes Agent 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
Hermes paired but still can't use BTCPay Server
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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 Hermes Agent BTCPay Server integration?
Yes. ClawLink is the fastest way to connect Hermes to BTCPay Server: link your BTCPay Server account once in the browser and Hermes Agent can call the BTCPay Server API through 16 ready-made tools — no custom code or token handling.
How do I connect BTCPay Server to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect BTCPay Server in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to BTCPay Server in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want BTCPay Server working from chat.
Hermes paired but still can't use BTCPay Server
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
