btcpayserver-mcp
This server provides a Model Context Protocol (MCP) interface for BTCPayServer, enabling AI assistants to interact with the complete BTCPayServer API ecosystem through a simplified toolset.
Core Capabilities:
Explore Services: Use
get_service_infoto discover available BTCPayServer services (invoices, payment requests, stores, users, webhooks, etc.)Understand Parameters: Use
get_method_infoto get detailed parameter requirements, descriptions, and examples for any service methodExecute Operations: Use
btcpay_requestto perform any BTCPayServer API operation, including:Payment Processing: Create and manage Bitcoin invoices, payment requests, and Lightning Network transactions
Store Management: Configure stores, payment methods, wallets, payout processors, email settings, and exchange rates
User Administration: Manage user accounts, permissions, API keys, and OAuth authorization
Integration & Automation: Handle webhooks, notifications, apps, and pull payments for real-time event handling
System Monitoring: Query server status, version, and configuration details
Key Features:
Compatible with BTCPayServer v1.7.0 and later
Works seamlessly with Claude Desktop and other MCP-compatible AI assistants
Robust error handling with clear messages for configuration, validation, and authentication issues
Follow a three-step workflow: discover services → understand parameters → execute operations
Provides comprehensive integration with BTCPayServer for Bitcoin payment processing, including invoice creation and management, payment request handling, Lightning Network operations, store management, webhook configuration, and user administration through BTCPayServer's complete API ecosystem.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@btcpayserver-mcp create a new invoice for $25.99"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BTCPayServer Model Context Protocol Server (Beta)
A comprehensive Model Context Protocol (MCP) server for BTCPayServer integration, providing tools for payment processing, store management, user administration, webhook handling and more with full API coverage.
Tool Reference
The BTCPayServer MCP Server provides a streamlined set of tools for interacting with BTCPayServer APIs:
Tool | Description | Primary Use |
| Discover methods available for a service | Exploration and discovery |
| Get detailed parameter requirements | Request preparation |
| Execute API calls to BTCPayServer | Performing operations |
Related MCP server: Square MCP Server
Integration with AI Assistants
Claude Desktop Integration
For Claude Desktop integration, add this configuration to your claude_desktop_config.json:
{
"mcpServers": {
"btcpayserver-mcp": {
"command": "node",
"args": ["path/to/btcpayserver-mcp/dist/index.js"],
"env": {
"BTCPAY_BASE_URL": "https://your-btcpay-instance.com",
"BTCPAY_API_KEY": "your_api_key_here",
"BTCPAY_STORE_ID": "your_default_store_id"
}
}
}
}Service Catalog
BTCPayServer MCP provides access to BTCPayServer's complete API ecosystem. Check out the BTCPayServer API Documentation for detailed information about each service:
Payment Services
Service | Description |
| Create, manage, and track Bitcoin invoices for payments |
| Create payment requests for donations or recurring billing |
| Manage internal Lightning Network operations |
| Store-level Lightning Network configurations |
| Lightning Address management and setup |
Store Management
Service | Description |
| Store creation, configuration, and management |
| Configure and manage store email settings and SMTP |
| Manage available payment methods for stores |
| Configure automated payout processing |
| Manage and process store payouts |
| Exchange rate configuration and management |
| Store user access and permissions management |
| Store wallet management and operations |
User & Access Management
Service | Description |
| User account management and administration |
| API key creation and permission management |
| OAuth and authorization flow management |
Integration & Automation
Service | Description |
| Real-time event notifications and webhook management |
| System notifications and alerts |
| BTCPayServer app integrations and plugins |
| Pull payment requests and refund management |
System
Service | Description |
| Server status, version, and configuration information |
Usage Pattern
For optimal interaction with the BTCPayServer API through MCP:
1. Discover: Use get_service_info to explore available methods
get_service_info(serviceName: "invoices")2. Understand: Use get_method_info to learn parameter requirements
get_method_info(serviceName: "invoices", methodName: "create")3. Execute: Use btcpay_request to perform the operation
btcpay_request(serviceName: "invoices", methodName: "create", parameters: {storeId: "your-store-id", amount: "10.00", currency: "USD"})Installation
Clone this repository:
git clone <repository-url>
cd btcpayserver-mcpInstall dependencies:
npm installBuild the project:
npm run buildConfiguration
The MCP server requires the following environment variables:
BTCPAY_BASE_URL- Your BTCPayServer instance URL (e.g.,https://btcpay.example.com)BTCPAY_API_KEY- Your BTCPayServer API keyBTCPAY_STORE_ID- (Optional) Default store ID for operations
Setting up BTCPayServer API Key
Log into your BTCPayServer instance
Go to Account → Manage Account → API Keys
Click Generate Key
Select the required permissions for your use case:
Store management:
btcpay.store.canmodifystoresettingsPayment requests:
btcpay.store.cancreateinvoiceUser management:
btcpay.user.canmodifyprofileWebhooks:
btcpay.store.webhooks.canmodifywebhooksetc..
Copy the generated API key
Environment Setup
Create a .env file in your project root:
BTCPAY_BASE_URL=https://your-btcpay-instance.com
BTCPAY_API_KEY=your_api_key_here
BTCPAY_STORE_ID=your_default_store_idOr set environment variables directly:
export BTCPAY_BASE_URL=https://your-btcpay-instance.com
export BTCPAY_API_KEY=your_api_key_here
export BTCPAY_STORE_ID=your_default_store_idUsage
Running the MCP Server
npm startFor development:
npm run devDevelopment and Debugging
Using MCP Inspector: The MCP Inspector provides a visual interface for testing:
# Build the project
npm run build
# Start the inspector with the BTCPayServer MCP Server
npx @modelcontextprotocol/inspector node dist/index.jsDevelopment Workflow:
Clone the repository
Install dependencies:
npm installStart development mode:
npm run buildRun the server:
node dist/index.jsTest your changes using the MCP Inspector
The MCP server provides comprehensive error handling:
Configuration Errors: Missing environment variables
API Errors: BTCPayServer API communication issues
Validation Errors: Invalid input parameters
Authentication Errors: Invalid or expired API keys
All errors are properly formatted and returned with descriptive messages.
Development
Project Structure
src/
├── index.ts # Main MCP server implementation
├── services/ # BTCPayServer service implementations
│ ├── base-service.ts # Base service class
│ ├── invoices.ts # Invoice management
│ ├── payment-requests.ts # Payment request handling
│ ├── stores.ts # Store management
│ ├── webhooks.ts # Webhook management
│ └── ... # Other service modules
├── utils/
│ └── btcpay-client.ts # BTCPayServer API client
└── types.ts # TypeScript type definitionsBuilding
npm run buildRunning in Development
npm run devSecurity Considerations
API Key Security: Never commit API keys to version control
Environment Variables: Use secure environment variable management
Webhook Secrets: Always use webhook secrets for verification
HTTPS: Ensure BTCPayServer instance uses HTTPS
Permissions: Use principle of least privilege for API key permissions
BTCPayServer Compatibility
This MCP server is compatible with BTCPayServer v1.7.0 and later. It uses the official BTCPayServer REST API v1.
Contributing
Fork the repository
Create a feature branch
Commit your changes
Push to the branch
Create a Pull Request
License
MIT License - see LICENSE file for details.
Support
For issues and questions:
Check the BTCPayServer documentation
Review the API reference
Open an issue in this repository
Help us improve this MCP
Note: Some methods might not be working properly. Please help us by reporting requirements and making pull requests to improve them. Also, to keep it up with the latest API version, we need to continue updating it.
Available Tools
3 toolsbtcpay_requestC
Execute a BTCPayServer API operation using the service-based approach.
Inputs: serviceName (required), methodName (required), parameters.
get_method_infoC
Get detailed parameter requirements and examples for a specific service method.
Inputs: serviceName (required), methodName (required).
get_service_infoB
Discover available BTCPayServer services and their methods. Use this to explore what operations are available.
Inputs: serviceName.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: btcpay_request executes API operations, get_method_info provides parameter details for specific methods, and get_service_info discovers available services. There is no overlap in functionality, and an agent can easily distinguish between them based on their descriptions.
The tool names follow a consistent verb_noun pattern throughout: btcpay_request, get_method_info, and get_service_info. All use snake_case with clear action-object naming, making them predictable and easy to understand.
With only 3 tools, the server feels thin for a BTCPayServer integration, which typically involves multiple operations like creating invoices, managing stores, or handling payments. While the tools provide a foundation for exploration and execution, the count is borderline low for the apparent scope of interacting with a payment processing platform.
The tool surface is significantly incomplete for a BTCPayServer domain. It lacks core operations such as creating invoices, retrieving payment details, managing stores, or handling webhooks. The tools focus on discovery and generic execution, but without direct methods for common workflows, agents will likely encounter dead ends or inefficiencies.
Maintenance
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Official BlindPay MCP server: stablecoin payouts, payins, quotes and customers for global payments.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseDqualityNot gradedmaintenanceA comprehensive MCP server that provides sophisticated tools for interacting with PocketBase databases. This server enables advanced database operations, schema management, and data manipulation through the Model Context Protocol (MCP).14671 npm70MIT
- AlicenseBqualityFmaintenanceA server that enables interaction with Square's API via Goose, supporting queries for locations, customers, and more with context preservation and MCP-compliant responses.124MIT
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- AlicenseAqualityDmaintenanceAn MCP server that enables AI agents to manage merchant payment processing through the BTCPay Server Greenfield REST API. It supports tools for creating invoices, managing stores, tracking payments, and performing Lightning Network operations.21MIT