BTCPay Server MCP vs MCP Ap2
A side-by-side look at the BTCPay Server MCP and MCP Ap2 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BTCPay Server MCP for finance & fintech work as a local process; choose MCP Ap2 for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose BTCPay Server MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BTCPAY_BASE_URL, BTCPAY_API_KEY, BTCPAY_STORE_ID. - You want tools like
get_server_info, list_stores, get_store_info.
Choose MCP Ap2 when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_oauth_token, send_pix, create_pix_qr.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 49/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | BTCPAY_BASE_URLBTCPAY_API_KEYBTCPAY_STORE_ID | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 274 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 21 | 22 |
| Full listing | View BTCPay Server MCP | View MCP Ap2 |
Tools & capabilities
BTCPay Server MCP tools 21
get_server_infoBTCPay Server version, sync status, supported methodslist_storesList all stores accessible with the API keyget_store_infoStore configuration: currency, speed policy, checkout typeget_store_payment_methodsEnabled payment methods: on-chain, Lightning, etc.create_invoiceCreate a new invoice (amount, currency, order ID, description)get_invoiceInvoice status, payments received, metadata, timinglist_invoicesList invoices with optional status filterget_exchange_rateCurrent BTC/fiat exchange rate from BTCPaylist_pull_paymentsList pull payments (donations, subscriptions, payroll)create_pull_paymentCreate pull payment for donations, subscriptions, or payrolllist_payoutsList actual payout transactions (claims against pull payments)list_payment_requestsList payment requests (reusable payment links)- +9 more on the listing page
MCP Ap2 tools 22
get_oauth_tokenMint or return a cached OAuth2 client_credentials bearer token for the Itaú Developer Portal. Exposed so agents can inspect token freshness; normal tool calls obtain tokens implicitly.send_pixInitiate an outbound Pix payment from the merchant's Itaú account. Amount in BRL major units (e.g. '10.50').create_pix_qrCreate a dynamic Pix charge with QR code (cob). Returns the txid, copy-paste EMV payload, and location URL.get_pixRetrieve a Pix transaction by its BCB endToEndId (E<ispb><yyyymmddhhmm><sequence>).resolve_dict_keyResolve a DICT key (CPF, CNPJ, email, phone, EVP) to the owner's account data before sending a Pix. Subject to BCB rate limits per consenting payer.refund_pixRefund (devolução) a previously received Pix. Must reference the original endToEndId and a merchant-side refund id.create_boletoIssue a boleto via Itaú Cobrança. Returns nosso_numero, linha_digitável, barcode, and PDF URL.get_boletoRetrieve a boleto by its Itaú identifier (id or nosso_numero).cancel_boletoCancel (baixa) an outstanding boleto before payment.get_statementRetrieve account statement transactions for a given period. Paginated.arrecadacao_payPay a utility, tax, or concessionária bill via Itaú Arrecadação. Works with barcode (código de barras) or linha digitável.create_pix_cobvCreate a Pix charge with due date (cobv) — used for boleto-like Pix where the payer can pay at or after a due date with optional fine/interest. Returns txid, copy-paste EMV payload, and location URL.- +10 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
BTCPay Server MCP
{
"mcpServers": {
"btcpay-server-mcp": {
"command": "uvx",
"args": [
"btcpay-mcp"
],
"env": {
"BTCPAY_BASE_URL": "YOUR_BTCPAY_BASE_URL_HERE",
"BTCPAY_API_KEY": "YOUR_BTCPAY_API_KEY_HERE",
"BTCPAY_STORE_ID": "YOUR_BTCPAY_STORE_ID_HERE"
}
}
}
}
MCP Ap2
{
"mcpServers": {
"mcp-ap2": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-itau@alpha"
]
}
}
}
Frequently asked questions
BTCPay Server MCP is categorized under Finance & Fintech and uses a local stdio subprocess. MCP Ap2 belongs to Finance & Fintech and uses a local stdio subprocess. Pick BTCPay Server MCP for finance & fintech work and MCP Ap2 for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
BTCPay Server MCP has no declared pricing — check the project's own site. MCP Ap2 has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add btcpay-server-mcp and mcp-ap2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BTCPay Server MCP has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Ap2 has 67/100 (Great) with 0 views, 0 installs and 274 GitHub stars.