MCP server for Bitnovo Pay integration with AI agents. Provides cryptocurrency payment capabilities through Bitnovo Pay API. Features include payment
Bitnovo Pay MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for Bitnovo Pay integration with AI agents. Provides cryptocurrency payment capabilities through Bitnovo Pay API. Features include payment creation, status checking, QR code generation, and webhook management with support for.
A Model Context Protocol (MCP) server that provides AI agents with cryptocurrency payment capabilities through Bitnovo Pay API integration. This server enables AI models to create payments, check payment status, manage QR codes, and access cryptocurrency catalogs.
Once Bitnovo Pay is connected, these are the calls the assistant has available:
create_payment_onchain — Creates a cryptocurrency payment with a specific address for direct transactionscreate_payment_link — Creates a web-based payment URL where customers can choose their cryptocurrencyget_payment_status — The get_payment_status tool exposed by this serverlist_currencies_catalog — Gets available cryptocurrencies with optional amount-based filteringgenerate_payment_qr — Creates custom QR codes for existing payments with high-quality outputget_webhook_events — Query webhook events received in real-time from Bitnovo Pay APIget_webhook_url — Get public webhook URL with configuration instructions for Bitnovo panelget_tunnel_status — The get_tunnel_status tool exposed by this serverArchitecture — The Architecture tool exposed by this serverYou will need 8 environment variables: BITNOVO_DEVICE_ID, BITNOVO_BASE_URL, BITNOVO_DEVICE_SECRET, WEBHOOK_ENABLED, TUNNEL_ENABLED, TUNNEL_PROVIDER, NGROK_AUTHTOKEN, NGROK_DOMAIN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
@bitnovopay/mcp-bitnovo-pay on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Bitnovo Pay's toolset — create_payment_onchain, create_payment_link, get_payment_status and 6 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_payment_onchain | Creates a cryptocurrency payment with a specific address for direct transactions. |
| create_payment_link | Creates a web-based payment URL where customers can choose their cryptocurrency. |
| get_payment_status | The get_payment_status tool exposed by this server. |
| list_currencies_catalog | Gets available cryptocurrencies with optional amount-based filtering. |
| generate_payment_qr | Creates custom QR codes for existing payments with high-quality output. |
| get_webhook_events | Query webhook events received in real-time from Bitnovo Pay API. |
| get_webhook_url | Get public webhook URL with configuration instructions for Bitnovo panel. |
| get_tunnel_status | The get_tunnel_status tool exposed by this server. |
| Architecture | The Architecture tool exposed by this server. |
{
"mcpServers": {
"bitnovo-pay": {
"command": "npx",
"args": ["-y", "@bitnovopay/mcp-bitnovo-pay"],
"env": {
"BITNOVO_DEVICE_ID": "your_device_id_here",
"BITNOVO_BASE_URL": "https://pos.bitnovo.com"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BITNOVO_DEVICE_ID | Configuration value read at startup. | Optional |
| BITNOVO_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| BITNOVO_DEVICE_SECRET | Credential the server authenticates with. | Yes |
| WEBHOOK_ENABLED | Configuration value read at startup. | Optional |
| TUNNEL_ENABLED | Configuration value read at startup. | Optional |
| TUNNEL_PROVIDER | Configuration value read at startup. | Optional |
| NGROK_AUTHTOKEN | Credential the server authenticates with. | Yes |
| NGROK_DOMAIN | Configuration value read at startup. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.