Skip to main content
Glama
theYahia

paymongo-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to paymongo-mcp

No user-submitted related servers found.

    Related Servers

    • vnpay-mcp

      theYahia
      A
      license
      B
      quality
      D
      maintenance
      MCP server for VNPay payment gateway (Vietnam). Supports payment URL generation, transaction queries, refunds, tokenized payments, and IPN verification with HMAC-SHA512 signing.
      8
      10 npm
      MIT

    • bog-ipay-mcp

      theYahia
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Bank of Georgia iPay payment gateway, enabling payment orders, refunds, recurring payments, and pre-authorization via OAuth 2.0 + JWT.
      8
      16 npm
      MIT

    • payme-mcp

      theYahia
      A
      license
      B
      quality
      F
      maintenance
      MCP server for Payme payment system (Uzbekistan). Supports transactions, statements, payment links, and balance queries via JSON-RPC 2.0.
      8
      8 npm
      MIT

    • maib-mcp

      theYahia
      A
      license
      A
      quality
      D
      maintenance
      MCP server for MAIB e-commerce payments (Moldova). Supports payments, refunds, recurring billing, one-click payments, and transaction status via OAuth 2.0.
      8
      13 npm
      MIT

    • zen-mcp

      krystiangw
      A
      license
      A
      quality
      B
      maintenance
      MCP server for ZEN.com Payment Gateway enabling payment links, transaction lookup, refunds, payouts, and reporting.
      14
      29 npm
      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

    A3.7/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools are mostly distinct, each targeting a specific resource and action. However, create_checkout, create_link, and create_source all initiate payment collection and could be confused by an agent; their descriptions partially mitigate this.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get_, create_, list_, update_, archive_, verify_). There are no mixed naming conventions or vague verbs.

    Tool Count4/5

    24 tools is on the heavier side but appropriate for a payment API covering multiple resources (payments, refunds, checkouts, links, webhooks, customers). Each tool serves a clear purpose within its resource.

    Completeness3/5

    Core payment flows are covered, including payment intents, sources, payments, refunds, and webhooks. However, there are notable gaps: no get_payment, no update/delete for customers, and payment intents lack attach/confirm operations, requiring workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources