momo-xof-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOMO_ENV | No | Environment: sandbox (default) or production. | sandbox |
| MOMO_API_KEY | Yes | CinetPay API key. | |
| MOMO_TIMEOUT | No | Timeout in seconds, default 30. | 30 |
| MOMO_BASE_URL | No | Base URL. Defaults to the sandbox host. | |
| MOMO_FAILED_URL | Yes | Failed URL. Max 120 characters. | |
| MOMO_MAX_AMOUNT | No | Server-side ceiling in whole XOF, default 50000. | 50000 |
| MOMO_SUCCESS_URL | Yes | Success URL. Max 120 characters. | |
| MOMO_API_PASSWORD | Yes | CinetPay API password. Set it on the dashboard first — it is unset by default. | |
| MOMO_CALLBACK_URL | Yes | Callback URL. The aggregator rejects a payment without it. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| momo_list_operatorsA | List the countries of the West African CFA franc (XOF) zone and the mobile money services available in each. For every one of the eight UEMOA countries it returns the ISO code, international dialing code, national number length and E.164 format, then the payment services on offer, and finally optional prefix hints. Purely static: no network call, no credentials needed. Use it before initiating a payment to check that a country and a service are in scope and that a phone number has the expected shape. Payment services are unrelated to number prefixes: independent wallets such as Wave run on any national mobile number. Prefix hints, when present, map a prefix to a telecom network only, are defeated by number portability, and must never be used to route a payment. |
| momo_initiate_paymentA | Request a mobile money payment from a customer in the XOF zone. IMPORTANT: this REQUESTS a payment, it never confirms one. A successful call means the aggregator accepted the request and returned a payment link; the customer has not paid yet and no money has moved. The final outcome arrives asynchronously and must be checked separately. Returns a payment_url that the customer must open to complete the payment, plus the transaction identifiers needed to reconcile it. The caller must supply a unique reference for idempotency; it is never generated silently. Amounts are whole XOF: the franc has no decimals. A server-side ceiling rejects amounts above the configured maximum. |
| momo_check_payment_statusA | Check what became of a payment you requested earlier. Read-only: it never moves money and never changes anything. Accepts either the merchant reference you supplied when initiating, or the transaction_id returned then. Returns a stable status plus the aggregator's own status and code, and says whether the outcome is final. A payment that was requested but never completed by the customer ends up FAILED, which is final — it does not stay pending forever. The customer's phone number is returned masked, never in full. |
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 3 tools
The three tools occupy clearly separate phases of a payment flow: static coverage lookup, payment initiation, and status polling. Descriptions explicitly disambiguate initiation (request-only, returns a link) from status checking (read-only, resolves outcome), so an agent cannot easily confuse them.
All three follow the same pattern: a shared momo_ namespace prefix plus verb_noun (list_operators, initiate_payment, check_payment_status). No mixed casing or inconsistent verb styles.
Three tools is exactly the surface needed for a narrow mobile-money payment scope: discover coverage, start a payment, check its result. Each tool earns its place and nothing extraneous is exposed.
The core lifecycle (coverage discovery -> initiate -> async status) is fully covered, including idempotency references and finality of FAILED states. Gaps remain around refunds, cancellation, and listing past transactions, but agents can work around these for the stated request-and-reconcile purpose.