Skip to main content
Glama
Xental MCP Server

Xental MCP Server

Xental MCP server

A Model Context Protocol server that lets any MCP-capable agent (Claude Desktop, Claude Code, and others) operate a Xental merchant account through typed tools — provision virtual accounts, watch reconciled transactions, run payouts, and drive the sandbox, all in natural language.

Instead of an agent scraping the dashboard, it talks to Xental over the same public API you use. This is the "agent plane": your AI assistant becomes a first-class operator of your payments.

Tools

Tool

What it does

get_agent_guide

Reads /.well-known/llms.txt — auth, core flow, differentiators

list_virtual_accounts / get_virtual_account

List / fetch NUBANs with balance + reconciliation state

create_virtual_account

Provision a NUBAN for a customer (sandbox on test keys)

delete_virtual_account

Remove an account with no activity

list_transactions / get_transaction / transactions_summary

Reconciled inflows/outflows + totals

list_banks / lookup_bank_account

Payout bank list + name enquiry

initiate_transfer / list_transfers

Send a payout (idempotent) / list payouts

simulate_deposit

Sandbox: drive a real reconciliation with no bank movement

All money is integer kobo (₦1 = 100 kobo). Money-moving calls are idempotent on a caller-supplied reference.

Related MCP server: Brighty MCP Server

Install

git clone https://github.com/XENTAL-PayLibre/xental-mcp.git
cd xental-mcp
npm install
npm run build

This produces build/index.js — the executable server.

Credentials

Create an API key in the Xental dashboard (Settings → Developers) and copy the client id and client secret (the secret is shown once). Start with a test-mode key — it works immediately and moves zero real money; live keys require approved KYC/KYB.

Env var

Default

Notes

XENTAL_CLIENT_ID

—

required

XENTAL_CLIENT_SECRET

—

required

XENTAL_API_BASE

https://api.xental.online

use https://api.staging.xental.online for sandbox

Use with Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "xental": {
      "command": "node",
      "args": ["/absolute/path/to/xental-mcp/build/index.js"],
      "env": {
        "XENTAL_API_BASE": "https://api.staging.xental.online",
        "XENTAL_CLIENT_ID": "your-client-id",
        "XENTAL_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Restart Claude Desktop, then try:

"Create a test virtual account for Ada, simulate a ₦5,000 deposit, and show me the reconciliation."

Use with Claude Code

claude mcp add xental \
  --env XENTAL_API_BASE=https://api.staging.xental.online \
  --env XENTAL_CLIENT_ID=your-client-id \
  --env XENTAL_CLIENT_SECRET=your-client-secret \
  -- node /absolute/path/to/xental-mcp/build/index.js

How auth works

The server exchanges your client credentials at POST /api/v1/auth/token for a short-lived bearer token, caches it, and refreshes automatically on expiry or a 401. Your secret never leaves the machine the server runs on.

License

MIT

Available Tools

13 tools
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).

Inputs: name (required), email, phone, accountRef, +1 more.

delete_virtual_accountA

Delete a virtual account that has no payment activity.

Inputs: accountRef (required).

get_agent_guideA

Read the Xental agent orientation (llms.txt): auth, core flow, and differentiators.

Inputs: no named parameters.

get_transactionB

Get one transaction by its reference.

Inputs: reference (required).

get_virtual_accountA

Get one virtual account by its reference, including balance and reconciliation state.

Inputs: accountRef (required).

initiate_transferA

Send a payout to a bank account. MOVES REAL MONEY on live keys. Idempotent on merchantTxRef. Amount in kobo.

Inputs: bankCode (required), amountKobo (required), accountNumber (required), merchantTxRef (required), +1 more.

list_banksA

List supported banks for payouts (name + bank code).

Inputs: no named parameters.

list_transactionsB

List reconciled inflows/outflows for the merchant.

Inputs: no named parameters.

list_transfersB

List outbound transfers (payouts).

Inputs: no named parameters.

list_virtual_accountsB

List the merchant's dedicated virtual accounts (NUBANs) with balances and payment state.

Inputs: no named parameters.

lookup_bank_accountC

Resolve an account name from an account number + bank code (name enquiry).

Inputs: bankCode (required), accountNumber (required).

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.

Inputs: accountRef (required), amountKobo (required), reversal, senderName.

transactions_summaryA

Aggregate transaction totals and reconciliation breakdown.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    13 tools is a reasonable count for a payment/virtual account server. Each tool covers a necessary operation without being overwhelming or too sparse.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Banking infrastructure for AI agents: open accounts, issue cards, send SEPA/SWIFT payments, run mass payouts, and pay invoices via natural language.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to manage financial operations including balance checks, money transfers, invoicing, spending policies, and audit logs through the PayGent API.
      13
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to manage merchant accounts, process payments, handle wallets and payouts, and sell digital goods through the wata.pro payment system.
      90
      MIT