Skip to main content
Glama
theYahia

@theyahia/cloudpayments-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @theyahia/cloudpayments-mcp

No user-submitted related servers found.

    Related Servers

    • Razorpay MCP Server

      hahahamid
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Razorpay payment gateway through natural language, allowing users to fetch payments, manage orders, issue refunds, and list settlements.
      7 npm
      MIT
    • SumUp MCP Server by sumup

      SumUp MCP Serverofficial

      sumup
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interactions with SumUp payment services and APIs, allowing users to manage their SumUp account, process payments, and access payment data through LLM-powered conversations.
      91 npm
      7
      Apache 2.0

    • Stripe MCP Server

      Lokesh-2025
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Stripe accounts to query customers, revenue, invoices, subscriptions, disputes, and issue refunds.
      29 npm
      1
      MIT

    • PayBridgeNP MCP Server

      paybridgenp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with PayBridgeNP payment gateway accounts through natural language. Provides read-only access to payments, refunds, analytics, and account data, with write capabilities planned for future versions.
      31 npm
      1
      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.8/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct payment or subscription action. Charge, auth, confirm, void, and refund are clearly separated by their lifecycle stage, and descriptions make the differences explicit.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern such as create_subscription, refund_payment, and list_transactions. The naming convention is uniform and easy to predict.

    Tool Count5/5

    12 tools is a well-scoped set for a payment gateway server covering payments, transactions, orders, and subscriptions. Each tool adds distinct value without unnecessary redundancy.

    Completeness4/5

    The core payment lifecycle is covered: charge, auth, confirm, void, refund, and transaction lookup. Subscription workflows also have create, update, cancel, and list. Minor gaps exist such as no direct get_subscription endpoint or webhook-related tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources