MCP / Finance

BTCPay Server MCP: financial workflows

BTCPay Server is a free, open-source, self-hosted Bitcoin payment processor that enables merchants to accept Bitcoin payments without intermediaries. Connect it to Claude, Codex, Cursor or any MCP client through one FlyMy.AI MCP.

Connect BTCPay ServerWhat it can do
Your own API key17 actionsFinance

$ YOUR NEXT RUN

Claude CodeCodexCursorAny agent

Use BTCPay Server MCP in your assistant

Paste this prompt into Claude Code, Codex, Cursor or any agent. It reads the guide and helps you connect.

Read https://flymy.ai/skill.md and https://flymy.ai/mcp/btcpay-server.md. Help me connect BTCPay Server MCP to this assistant. Then help me run this task: Use BTCPay Server to create payment request. Ask me for the required inputs first and show the result.
Open FlyMy.AIDownload brief

What BTCPay Server MCP can do

17 actions in the FlyMy.AI catalog, the most used first. Your agent finds them through search_tools and calls the one the task needs.

ActionWhat it does
# BTCPAY_SERVER_CREATE_PAYMENT_REQUESTCreate a new payment request for a store.
# BTCPAY_SERVER_CREATE_STORECreate a new store in btcpay server.
# BTCPAY_SERVER_CREATE_USERCreate a new btcpay server user.
# BTCPAY_SERVER_CREATE_WEBHOOKRegister a new webhook.
# BTCPAY_SERVER_DELETE_API_KEYRevoke a specific api key.
# BTCPAY_SERVER_DELETE_PAYMENT_REQUESTDelete a specific payment request.
# BTCPAY_SERVER_DELETE_PAYOUTDelete a specific payout from a store.
# BTCPAY_SERVER_GET_API_KEYRetrieve the current api key.
# BTCPAY_SERVER_GET_API_KEYSList api keys.
# BTCPAY_SERVER_GET_PAYMENT_REQUESTSList all payment requests for a specific store.
# BTCPAY_SERVER_GET_SERVER_INFORetrieve information about the btcpay server instance.
# BTCPAY_SERVER_GET_STORERetrieve information about a specific store.
Show all 17 actions
ActionWhat it does
# BTCPAY_SERVER_GET_USERRetrieve information about a specific user.
# BTCPAY_SERVER_GET_WEBHOOKRetrieve details of a specific webhook.
# BTCPAY_SERVER_GET_WEBHOOKSList all webhooks registered for a store.
# BTCPAY_SERVER_LIST_APPSList all apps associated with a specific store.
# BTCPAY_SERVER_UPDATE_USERUpdate current user information.

Ask your agent

Requests to paste as they are. Each one runs on the actions named under it.

“Use BTCPay Server to create payment request. Ask me for the required inputs first and show the result.”uses BTCPAY_SERVER_CREATE_PAYMENT_REQUEST
“Use BTCPay Server to create store. Ask me for the required inputs first and show the result.”uses BTCPAY_SERVER_CREATE_STORE
“Use BTCPay Server to create user. Ask me for the required inputs first and show the result.”uses BTCPAY_SERVER_CREATE_USER

Connect BTCPay Server in a minute

One MCP for every integration. Add it once, then every MCP in the catalog is a request away.

  1. 01

    Add FlyMy.AI

    Add the FlyMy.AI MCP to your assistant with one of the commands below and sign in. No key to copy.

  2. 02

    Add your BTCPay Server URL

    Paste it into the BTCPay Server connection settings once; it stays with FlyMy.AI, never in a prompt or a chat.

    • BTCPay Server URL - The base URL of your BTCPay Server instance, e.g., 'mainnet.demo.btcpayserver.org'. (Do not include protocol) Get API key →
  3. 03

    Ask

    Paste a request from this page. Every run shows what it cost.

Claude Code
claude mcp add --transport http flymyai https://mcp-agents.flymy.ai/mcp

Then run /mcp in Claude Code and sign in.

Codex
codex mcp add flymy --url https://mcp-agents.flymy.ai/mcp

Then run codex mcp login flymy to sign in.

claude.ai and Claude Desktop
https://mcp-agents.flymy.ai/mcp

Settings, Connectors, Add custom connector: paste this URL.

Pay per run

FlyMy.AI bills the run: the model and the tool's seconds. Calls go to your own BTCPay Server account, under its plan and limits. No seats and no minimum.

See usage pricing →

Go to the source

BTCPay Server in the docs →BTCPay Server connection settings →BTCPay Server website →Every MCP in the catalog →Usage pricing →

From the FlyMy.AI platform catalog of 2026-11-03: name, description, actions and setup as the platform lists them. Examples are requests to paste, not recorded runs.