Skip to main content
Glama
ThomsenDrake

btcpay-mcp

by ThomsenDrake
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Related Servers

Alternatives to btcpay-mcp

No user-submitted related servers found.

    Related Servers

    • satsrail-mcp by SatsRail

      satsrail-mcpofficial

      SatsRail
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to accept Bitcoin Lightning payments. It allows agents to create orders, generate invoices, check payment status, and manage the full SatsRail merchant API through natural language.
      MIT

    • btc-mcp-srv

      lightphon
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to send and receive Bitcoin over the Lightning Network using NWC or LND backends.
      MIT

    • btcpayserver-mcp

      Abhijay007
      A
      license
      B
      quality
      F
      maintenance
      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.
      3
      59 npm
      3
      MIT

    • bitcoin-mcp

      spcpza
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server giving AI agents Bitcoin and Lightning superpowers for price checks, mempool inspection, Lightning payments, and more.
      MIT

    • Lightning Enable MCP

      refined-element
      A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI agents to make autonomous Bitcoin Lightning Network payments using the L402 protocol. Agents can pay for API access, purchase resources, and complete transactions without human intervention — invoice comes in, sats go out, done.
      17
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct BTCPay resource or operation (invoices vs. payment requests vs. pull payments are clearly differentiated). No functional overlap exists between the 21 tools, and descriptions clarify domain-specific terminology.

    Naming Consistency5/5

    Strict adherence to verb_noun snake_case convention throughout (create_invoice, get_invoice, list_invoices). Pluralization is consistent (list_* for collections, get_* for single items), with no mixing of naming styles.

    Tool Count4/5

    At 21 tools, this exceeds the typical ideal range but remains reasonable for a comprehensive payment processor API covering on-chain, Lightning, webhooks, and store management. Each tool serves a distinct purpose without redundancy.

    Completeness4/5

    Core payment acceptance workflows are fully covered (invoice lifecycle, payment requests, webhooks, refunds). Minor gaps exist in resource management operations (missing update/delete for webhooks and payment requests, no create_payout for arbitrary sends).

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources