Xental MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XENTAL_API_BASE | No | Base URL for the Xental API. Use https://api.staging.xental.online for sandbox. | https://api.xental.online |
| XENTAL_CLIENT_ID | Yes | Your Xental client ID from Settings -> Developers | |
| XENTAL_CLIENT_SECRET | Yes | Your Xental client secret from Settings -> Developers |
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_agent_guideA | Read the Xental agent orientation (llms.txt): auth, core flow, and differentiators. |
| list_virtual_accountsB | List the merchant's dedicated virtual accounts (NUBANs) with balances and payment state. |
| get_virtual_accountA | Get one virtual account by its reference, including balance and reconciliation state. |
| create_virtual_accountA | Provision a dedicated virtual account (NUBAN) for a customer. On test-mode keys this creates a sandbox account. Money is integer kobo (₦1 = 100 kobo). |
| delete_virtual_accountA | Delete a virtual account that has no payment activity. |
| list_transactionsB | List reconciled inflows/outflows for the merchant. |
| transactions_summaryA | Aggregate transaction totals and reconciliation breakdown. |
| get_transactionB | Get one transaction by its reference. |
| list_banksA | List supported banks for payouts (name + bank code). |
| lookup_bank_accountC | Resolve an account name from an account number + bank code (name enquiry). |
| initiate_transferA | Send a payout to a bank account. MOVES REAL MONEY on live keys. Idempotent on merchantTxRef. Amount in kobo. |
| list_transfersB | List outbound transfers (payouts). |
| simulate_depositA | Sandbox only (test-mode keys): drive a real reconciliation with no bank movement — create an account, simulate a payment, watch it reconcile end-to-end. Amount in kobo. |
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 13 tools
Each tool has a clearly distinct purpose. For example, get_transaction, list_transactions, and transactions_summary all serve different query scopes. The CRUD operations for virtual accounts and transfers are well-separated.
Most tools follow a verb_noun pattern (e.g., create_virtual_account, list_banks). The only deviation is transactions_summary, which uses noun_verb, causing a minor inconsistency.
13 tools is a reasonable count for a payment/virtual account server. Each tool covers a necessary operation without being overwhelming or too sparse.
Core operations are covered: CRUD on virtual accounts, transaction retrieval, transfer initiation, bank account lookup, and simulation. Minor gaps include no get_transfer tool to fetch a single transfer by reference.