Skip to main content
Glama
cinetpay-mcp

cinetpay-mcp

Official
by cinetpay

cinetpay-mcp

MCP Server for CinetPay — integrate mobile money payments into Claude, Cursor, and any MCP-compatible AI assistant.

What it does

This MCP server connects your AI assistant to the CinetPay API, enabling natural language interactions with mobile money payments across Africa.

Ask your assistant:

  • "What's the balance on the CI account?"

  • "Check the status of payment ORDER-12345"

  • "Initialize a payment of 5000 XOF for customer jean@email.com"

  • "Send 1000 XOF to +2250707000001 via Orange Money"

  • "What payment methods are available in Senegal?"

Related MCP server: PayLink MCP Server

Available Tools

Tool

Description

get_balance

Get account balance for a country

check_payment_status

Check payment status by ID

initialize_payment

Create a new payment (returns payment URL)

create_transfer

Send money to a phone number

check_transfer_status

Check transfer status by ID

list_payment_methods

List operators for a country

list_configured_countries

Show configured countries

Installation

Claude Code

claude mcp add cinetpay -- npx cinetpay-mcp

Then set your environment variables in .claude/settings.json:

{
  "mcpServers": {
    "cinetpay": {
      "command": "npx",
      "args": ["cinetpay-mcp"],
      "env": {
        "CINETPAY_API_KEY_CI": "sk_test_...",
        "CINETPAY_API_PASSWORD_CI": "your_password"
      }
    }
  }
}

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "cinetpay": {
      "command": "npx",
      "args": ["cinetpay-mcp"],
      "env": {
        "CINETPAY_API_KEY_CI": "sk_test_...",
        "CINETPAY_API_PASSWORD_CI": "your_password"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "cinetpay": {
      "command": "npx",
      "args": ["cinetpay-mcp"],
      "env": {
        "CINETPAY_API_KEY_CI": "sk_test_...",
        "CINETPAY_API_PASSWORD_CI": "your_password"
      }
    }
  }
}

Configuration

Environment Variables

Set credentials per country using the pattern CINETPAY_API_KEY_{COUNTRY} / CINETPAY_API_PASSWORD_{COUNTRY}:

# Côte d'Ivoire
CINETPAY_API_KEY_CI=sk_test_...
CINETPAY_API_PASSWORD_CI=your_password

# Sénégal
CINETPAY_API_KEY_SN=sk_test_...
CINETPAY_API_PASSWORD_SN=your_password

# Cameroun
CINETPAY_API_KEY_CM=sk_live_...
CINETPAY_API_PASSWORD_CM=your_password

Single country

CINETPAY_API_KEY=sk_test_...
CINETPAY_API_PASSWORD=your_password
CINETPAY_COUNTRY=CI  # Default: CI

Optional

CINETPAY_BASE_URL=https://api.cinetpay.co  # Default: auto-detected from key prefix
CINETPAY_FORCE_IPV4=true                    # Force IPv4 DNS resolution

Environments

Key prefix

API URL

Environment

sk_test_...

https://api.cinetpay.net

Sandbox

sk_live_...

https://api.cinetpay.co

Production

The server auto-detects the environment from your API key prefix.

Supported Countries

Country

Code

Operators

Côte d'Ivoire

CI

Orange Money, Moov, MTN, Wave

Sénégal

SN

Orange Money, Free, Expresso, Wave

Cameroun

CM

Orange Money, MTN

Burkina Faso

BF

Orange Money, Moov, Wave

Mali

ML

Orange Money, Moov

Togo

TG

Moov, TMoney

Guinée

GN

Orange Money, MTN

Bénin

BJ

Moov, MTN

RD Congo

CD

Orange Money, Airtel, M-Pesa, Africell

Niger

NE

Airtel, Moov, Zamani

Security

  • API credentials are read from environment variables only — never hardcoded

  • The server uses the cinetpay-js SDK with all its security features:

    • HTTPS enforcement

    • Credential sanitization in logs

    • ES2022 private fields

    • Environment mismatch detection

  • Each user runs their own MCP server instance with their own credentials

Support

For CinetPay API questions: support@cinetpay.com

License

MIT

Available Tools

7 tools
check_payment_statusB

Check the status of a CinetPay payment by transaction ID or merchant transaction ID

Inputs: country (required), identifier (required).

check_transfer_statusB

Check the status of a CinetPay money transfer

Inputs: country (required), transaction_id (required).

create_transferC

Send money to a mobile money phone number via CinetPay

Inputs: amount (required), reason (required), country (required), currency (required), +4 more.

get_balanceA

Get the available balance of a CinetPay merchant account for a specific country

Inputs: country (required).

initialize_paymentB

Initialize a new CinetPay web payment. Returns a payment URL to redirect the customer to.

Inputs: amount (required), country (required), currency (required), failed_url (required), +8 more.

list_configured_countriesA

List countries configured with API credentials in this MCP server

Inputs: no named parameters.

list_payment_methodsA

List available mobile money payment methods (operators) for a given country

Inputs: country (required).

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 7 tools

    Disambiguation5/5

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

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Flutterwave payment services, providing tools for transaction management, payment link generation, and automated customer support.
      82 npm
      4
      TypeScript
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Open-source MCP server that streamlines payment integration for AI agents and financial apps in Africa, providing unified tools for providers like M-Pesa.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for Mobile Money in Francophone West Africa that enables AI agents to make payments via MTN MoMo (sandbox) using tools like request_payment, check_payment_status, and disburse_payment.
      1
      MIT