moolre-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X-API-KEY | No | Private API key (used by account/transfer/payment/list_transactions endpoints) | |
| X-API-USER | No | Your Moolre username (used by every endpoint) | |
| X-API-PUBKEY | No | Public API key (used by create_payment_id, create_bank_account_number, generate_payment_link, payment_status) | |
| accountnumber | No | Your Moolre wallet account number (used by most endpoints except create_account, SMS/WhatsApp endpoints) | |
| X-API-VASKEY-SMS | No | VASKEY for SMS endpoints (used by send_sms, send_sms_get, sms_status, create_sender_id, sender_id_status, list_sender_ids, approve_sender_id, sms_account_status) | |
| X-API-VASKEY-WHATSAPP | No | VASKEY for WhatsApp endpoints (used by get_whatsapp_templates, send_whatsapp_message, whatsapp_message_status) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_accountC | Create a new Moolre business wallet/account. |
| update_accountB | Update a Moolre business wallet/account's details and settlement settings. |
| account_statusB | Check a Moolre wallet's balance and status. |
| list_transactionsC | This returns a list of transactions linked with a specific account. |
| validate_nameA | Confirm the name of a Mobile Money or Bank Account holder before initiating a transfer. |
| initiate_transferC | Send money to a Mobile Money or Bank Account instantly. |
| transfer_statusA | Check the final status of a previously initiated transfer. |
| initiate_paymentC | Send a USSD payment request to a payer's phone number for approval. |
| internal_transferC | Initiate an internal transfer using your Moolre account. |
| create_payment_idB | Generate a unique permanent payment ID for use in making payments (dial 203paymentid#). |
| create_bank_account_numberC | Generate a permanent virtual bank account number linked to your wallet/account for secure payments. |
| generate_payment_linkB | Create a hosted Moolre Web POS payment page URL for collecting payments. |
| payment_statusA | Check the final status of a previously initiated payment collection. |
| send_smsC | POST https://api.moolre.com/open/sms/send — Send bulk or single SMS messages. Requires X-API-VASKEY. |
| send_sms_getB | GET https://api.moolre.com/open/sms/send — Send a single SMS via query parameters. Requires X-API-VASKEY. |
| sms_statusB | POST https://api.moolre.com/open/sms/status (type 5) — Check SMS delivery status by reference. Requires X-API-VASKEY. |
| create_sender_idB | POST https://api.moolre.com/open/sms/query (type 3) — Request a new Sender ID. Requires X-API-VASKEY. |
| sender_id_statusB | POST https://api.moolre.com/open/sms/status (type 1) — Check Sender ID approval status. Requires X-API-VASKEY. |
| list_sender_idsB | POST https://api.moolre.com/open/sms/status (type 7) — List all registered Sender IDs. Requires X-API-VASKEY. |
| approve_sender_idA | POST https://api.moolre.com/open/sms/status (type 6) — Approve or reject Sender IDs (admin). Requires X-API-VASKEY. |
| sms_account_statusC | POST https://api.moolre.com/open/sms/status (type 2) — Check SMS credit balance. Requires X-API-VASKEY. |
| get_whatsapp_templatesB | GET https://api.moolre.com/open/whatsapp/template — Fetch WhatsApp message templates. Requires X-API-VASKEY. |
| send_whatsapp_messageA | POST https://api.moolre.com/open/whatsapp/send — Send batch WhatsApp template messages. Requires X-API-VASKEY. |
| whatsapp_message_statusB | POST https://api.moolre.com/open/whatsapp/status — Track WhatsApp message delivery by reference. Requires X-API-VASKEY. |
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 24 tools
Most tools have distinct purposes, especially between payments, SMS, and WhatsApp. However, there is potential ambiguity among SMS-related tools (e.g., sender_id_status vs list_sender_ids, and send_sms vs send_sms_get) which could cause confusion. Descriptions help but still could be clearer.
Tool names predominantly follow a verb_noun pattern (e.g., create_account, send_sms), but a few like account_status and sender_id_status use noun_status instead of a verb. This minor inconsistency lowers the score slightly.
With 24 tools covering payments, SMS, and WhatsApp, the count is slightly high but justified by the breadth of functionality. It remains manageable and each tool has a defined role.
Core operations are covered (create, read, update for accounts; send and check for SMS/WhatsApp), but there are notable gaps: no tool to update or delete sender IDs, no cancellation for transfers, and no listing of generated payment IDs or bank accounts. This may cause agent failures in some workflows.