@theyahia/cloudpayments-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port for HTTP transport (optional, e.g., 3000) | |
| CLOUDPAYMENTS_PUBLIC_ID | Yes | Public ID (HTTP Basic username) | |
| CLOUDPAYMENTS_API_SECRET | Yes | API secret (HTTP Basic password) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| charge_paymentA | One-step payment (immediate charge). Pass card cryptogram from CloudPayments widget, amount, and payer IP. |
| auth_paymentA | Two-step payment (authorize/hold). Funds are blocked but not charged until confirmed. |
| confirm_paymentA | Confirm an authorized payment (charge the held amount). Can confirm a partial amount. |
| void_paymentA | Void an authorized payment (release the hold). Works only before confirmation. |
| get_transactionA | Find a transaction by ID. Returns status, amount, card info, and timestamps. |
| refund_paymentC | Refund a payment (full or partial) by transaction ID. |
| create_subscriptionA | Create a recurring subscription. Requires a token from a previous payment. Charges automatically on schedule. |
| update_subscriptionC | Update subscription parameters: amount, interval, period, description. |
| cancel_subscriptionA | Cancel an active subscription by ID. Stops all future charges. |
| list_subscriptionsA | List all subscriptions for a given user (AccountId). |
| create_orderA | Create a payment order (invoice link). Returns a URL the payer can open to pay. |
| list_transactionsA | List all transactions for a given date. Returns completed, authorized, and declined transactions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
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.
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.
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.
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.