cinetpay-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CINETPAY_API_KEY | No | API key for single country mode | |
| CINETPAY_COUNTRY | No | Country code for single country mode (e.g., CI, SN, CM) | CI |
| CINETPAY_BASE_URL | No | Base URL, auto-detected from key prefix | |
| CINETPAY_API_KEY_CI | No | API key for Côte d'Ivoire (multi-country mode) | |
| CINETPAY_API_KEY_SN | No | API key for Sénégal (multi-country mode) | |
| CINETPAY_FORCE_IPV4 | No | Force IPv4 DNS resolution (e.g., 'true') | |
| CINETPAY_API_PASSWORD | No | API password for single country mode | |
| CINETPAY_API_PASSWORD_CI | No | API password for Côte d'Ivoire (multi-country mode) | |
| CINETPAY_API_PASSWORD_SN | No | API password for Sénégal (multi-country mode) |
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 |
|---|---|
| get_balanceA | Get the available balance of a CinetPay merchant account for a specific country |
| check_payment_statusB | Check the status of a CinetPay payment by transaction ID or merchant transaction ID |
| initialize_paymentB | Initialize a new CinetPay web payment. Returns a payment URL to redirect the customer to. |
| create_transferC | Send money to a mobile money phone number via CinetPay |
| check_transfer_statusB | Check the status of a CinetPay money transfer |
| list_payment_methodsA | List available mobile money payment methods (operators) for a given country |
| list_configured_countriesA | List countries configured with API credentials in this MCP server |
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 7 tools
Each tool targets a distinct resource and action: balance, transfer status, payment status, payment initialization, transfer creation, and listing operations. The two status-checking tools are clearly separated by transaction type (payment vs transfer).
All tool names follow a consistent verb_noun snake_case pattern: get_, check_, initialize_, create_, list_. The verbs and nouns are predictable and match the operation performed.
Seven tools is well-scoped for a payment-focused MCP server. Each tool covers a necessary aspect of the payment/transfer lifecycle without bloat or redundancy.
The core lifecycle is covered: initialize payment, check payment status, create transfer, check transfer status, get balance, and list required configuration/methods. Minor gaps exist such as refund/cancel operations, but agents can likely complete typical payment flows.