Africa Payments

Unified MCP server that connects M-Pesa, Paystack, MTN MoMo, and more via natural language with an open, developer-first design.

javascript

0

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "kenyaclaw-africa-payments-mcp": {
      "command": "africa-payments-mcp",
      "args": [],
      "env": {
        "MPESA_CONSUMER_KEY": "your_mpesa_key",
        "PAYSTACK_SECRET_KEY": "your_paystack_secret"
      }
    }
  }
}

You can manage payments across multiple providers in Africa using a single MCP server that translates natural language requests into actions like sending money, requesting payments, or checking statuses. This simplifies integration, speeds up development, and lets you interact with M-Pesa, Paystack, MTN MoMo, and more through a consistent interface.

How to use

Ask in plain language to perform common payment tasks. For example, say or type: "Send KES 5,000 to Mary via M-Pesa" to initiate a payment, or "Check if that MTN MoMo payment came through" to verify a transfer. The server parses your request and routes it to the appropriate provider adapters, returning results you can act on in your MCP client.

How to install

Prerequisites: you need Node.js and npm installed on your machine. Ensure you have a supported MCP client to connect to the server.

# One-line installer (recommended)
curl -fsSL https://raw.githubusercontent.com/kenyaclaw/africa-payments-mcp/main/scripts/install.sh | bash

# Or with wget
wget -qO- https://raw.githubusercontent.com/kenyaclaw/africa-payments-mcp/main/scripts/install.sh | bash

Manual installation steps you should follow after you have Node.js and npm ready:

npm install -g @kenyaclaw/africa-payments-mcp

Configure the server using the interactive wizard or credential auto-detection, then connect to your MCP client by adding a server entry in your MCP configuration.

#africa-payments-mcp interactive setup
africa-payments-mcp init

#africa-payments-mcp detect --output config.json
africa-payments-mcp detect --output config.json

Additional configuration and usage notes

You can customize how your MCP client connects by adding the server configuration to your MCP clients. The example below shows the shape of a local runtime configuration that uses the Africa Payments MCP server and required credentials.

{
  "mcpServers": {
    "africa-payments": {
      "command": "africa-payments-mcp",
      "env": {
        "MPESA_CONSUMER_KEY": "your_key",
        "PAYSTACK_SECRET_KEY": "your_key"
      }
    }
  }
}

Security and best practices

Keep API keys and secrets out of your codebase. Use environment variables or a secrets manager, and rotate credentials periodically. Restrict access to the MCP server to trusted clients, and monitor activity for anomalous requests.

Examples of common actions

Send money, request payments, check payment status, process refunds, and handle collections or disbursements across providers with a single natural language interface.

Troubleshooting tips

If you encounter errors, verify that credentials for each provider are correctly set and that your MCP client is configured to reach the Africa Payments MCP server. Check provider status flags and ensure the MCP server has network access to the providers.

Notes

The server is designed to be AI-native and developer-friendly, enabling quick ship cycles and AI agent compatibility for payments across Africa.

Available tools

send_money

Send funds to a recipient via a selected African provider using natural language commands.

request_payment

Request a payment from a customer or partner through the MCP interface.

check_payment_status

Check the status of a previously initiated payment.

process_refund

Process refunds for orders or transactions across providers.