BTCPay Server MCP vs MCP Server

A side-by-side look at the BTCPay Server MCP and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

BTCPay Server MCP logoBTCPay Server MCPFinance & Fintech · Local subprocess (stdio)21 tools for AI agents to manage BTCPay Server: invoices, payments, stores, webhooks, Lightning49FairAuth: not declaredMCP Server logoMCP ServerFinance & Fintech · Local subprocess (stdio)AllRatesToday currency exchange rates: real-time mid-market rates for 160+ currencies (Reuters/Refinitiv), historical data (1d/7d/30d/1y), currency list, and multi-target lookups. Free tier, no key needed for the simple-rate endpoint. Install: npx @allratestoday/mcp-server.65GreatAuth: api key required

Verdict: choose BTCPay Server MCP for finance & fintech work as a local process; choose MCP Server 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?

BTCPay Server MCP logoChoose 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.
Explore BTCPay Server MCP

MCP Server logoChoose MCP Server when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: ALLRATES_API_KEY.
  • You want tools like get_exchange_rate, get_historical_rates, get_rates_authenticated.
Explore MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBTCPay Server MCP logoBTCPay Server MCPMCP Server logoMCP Server
CategoryFinance & FintechFinance & Fintech
Quality signal49/100 · Fair65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFreemium
Required env varsBTCPAY_BASE_URLBTCPAY_API_KEYBTCPAY_STORE_IDALLRATES_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars04
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools214

Tools & capabilities

BTCPay Server MCP tools 21

  • get_server_infoBTCPay Server version, sync status, supported methods
  • list_storesList all stores accessible with the API key
  • get_store_infoStore configuration: currency, speed policy, checkout type
  • get_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, timing
  • list_invoicesList invoices with optional status filter
  • get_exchange_rateCurrent BTC/fiat exchange rate from BTCPay
  • list_pull_paymentsList pull payments (donations, subscriptions, payroll)
  • create_pull_paymentCreate pull payment for donations, subscriptions, or payroll
  • list_payoutsList actual payout transactions (claims against pull payments)
  • list_payment_requestsList payment requests (reusable payment links)
  • +9 more on the listing page

MCP Server tools 4

  • get_exchange_rateUse this when the user asks 'what is X in Y?', 'convert X to Y', 'current rate of EUR/USD', or any single fiat-to-fiat live exchange rate question. Returns the latest mid-market rate as a JSON object like { rate: 0.9234, source } meaning 1 source = 0.9234 target. Does NOT support cryptocurrencies, commodities, or arithmetic on amounts. For multiple targets in one call use get_rates_authenticated; for a past date or fixed lookback (7d/30d/1y) use get_historical_rates.
  • get_historical_ratesUse this for fixed-window time-series questions like 'how has EUR/USD moved this week', 'show me the last month of GBP/JPY', or 'chart 1-year history of AUD/USD'. Returns { source, target, period, data: [{ date, rate, timestamp }, ...] } — sampling is fixed per period (1d=hourly, 7d/30d=daily, 1y=weekly) and the window always ends NOW. For a specific past datetime use get_rates_authenticated with `time`. For a single live rate use get_exchange_rate.
  • get_rates_authenticatedUse this for (a) one source against multiple targets in a single call ('USD vs EUR, GBP, JPY'), or (b) the rate at a specific past datetime ('EUR/USD at 2025-03-14T12:00Z'), optionally bucketed by hour/day/week/month. Returns { rates: [{ rate, source, target, time }, ...] } — one row per target × time bucket. For a single live pair use get_exchange_rate. For fixed lookback windows (1d/7d/30d/1y ending now) use get_historical_rates.
  • list_currenciesCall this BEFORE other tools when you are unsure whether a currency code is supported, or when the user asks 'what currencies do you support?', 'is X a valid currency?', or 'what is the symbol for X?'. Returns { currencies: [{ code: 'USD', name: 'US Dollar', symbol: '$' }, ...], count } covering 150+ ISO 4217 fiat currencies. Does NOT include cryptocurrencies. Cheap to call (cached 24h upstream) — use it to validate user input and prevent downstream errors in get_exchange_rate / get_rates_authenticated / get_historical_rates.

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 (Claude Desktop / Cursor)
{
  "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 Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cahthuranag-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@allratestoday/mcp-server"
      ],
      "env": {
        "ALLRATES_API_KEY": "YOUR_ALLRATES_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

BTCPay Server MCP is categorized under Finance & Fintech and uses a local stdio subprocess. MCP Server belongs to Finance & Fintech and uses a local stdio subprocess. Pick BTCPay Server MCP for finance & fintech work and MCP Server 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 Server is listed as freemium — a free tier with paid plans. Auth: api key required. 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 cahthuranag-mcp-server 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 Server has 65/100 (Great) with 5 views, 0 installs and 4 GitHub stars.