Kenya Payments (Flutterwave — M-Pesa)

Official6 tools

by junter1989k-ai · JavaScript

Kenya payments for AI agents — M-Pesa via Flutterwave. Never holds funds.

This MCP server provides Kenya payments for AI agents using M-Pesa via Flutterwave. It enables agents to accept payments in Kenya and is described as never holding funds. Tooling count is 6, and it is exposed over an HTTP MCP endpoint.

🛠️ Key Features

M-Pesa payments via Flutterwave
HTTP-based MCP endpoint (https://mcp-ke.wishpool.app/mcp)
Does not hold funds
Uses request-time HTTP headers for credentials (not stored)

🚀 Use Cases

Accepting Kenya payments for AI agents
MCP client integration with any MCP-capable agent (e.g., Claude Desktop, Cursor, Windsurf)

⚡ Developer Benefits

“Nothing to install” per the readme excerpt
Credentials passed via HTTP headers on each request
Includes a referenced threat model at https://mcp.wishpool.app/trust

⚠️ Limitations

Run instructions are cut off in the provided excerpt, so self-hosting details are not fully specified

Topics

ai-agentclaudeflutterwavekenyamcpmcp-serverpaymentswishpool

Captured live from the server via tools/list.

create_payment_link

Create a payment link in KES for Kenya via Flutterwave. Buyer pays with M-Pesa (the rail Kenya actually uses), cards, bank transfer. Returns a hosted checkout URL the buyer opens to pay — payment completes automatically, no confirm step. Bring your own credentials via HTTP header (x-flutterwave-secret-key; free test credentials from dashboard.flutterwave.com never move real money). Money always flows buyer→Flutterwave→merchant; this service never touches funds.

Parameters5

amount_kes	number	required	Amount in KES (decimals allowed), e.g. 10. Minimum 1.
description	string	required	What this payment is for (shown to the buyer, ≤200 chars)
customer_email	string	required	Buyer email (required by Flutterwave; the receipt goes there).
reference_id	string	optional	Your unique order reference (≤40 chars). Auto-generated if omitted.
success_url	string	optional	Optional https URL to send the buyer to after payment.

Raw schema

{
  "type": "object",
  "properties": {
    "amount_kes": {
      "type": "number",
      "minimum": 1,
      "maximum": 100000000,
      "description": "Amount in KES (decimals allowed), e.g. 10. Minimum 1."
    },
    "description": {
      "type": "string",
      "description": "What this payment is for (shown to the buyer, ≤200 chars)"
    },
    "customer_email": {
      "type": "string",
      "description": "Buyer email (required by Flutterwave; the receipt goes there)."
    },
    "reference_id": {
      "type": "string",
      "description": "Your unique order reference (≤40 chars). Auto-generated if omitted."
    },
    "success_url": {
      "type": "string",
      "description": "Optional https URL to send the buyer to after payment."
    }
  },
  "required": [
    "amount_kes",
    "description",
    "customer_email"
  ]
}

query_payment_status

Check whether a Kenya payment (created by create_payment_link) has been paid. Queries Flutterwave directly — pull-based, no webhook needed. paid=true when status is PAID.

Parameters1

tx_ref

string

required

The tx_ref returned by create_payment_link

Raw schema

{
  "type": "object",
  "properties": {
    "tx_ref": {
      "type": "string",
      "description": "The tx_ref returned by create_payment_link"
    }
  },
  "required": [
    "tx_ref"
  ]
}

refund_payment

Refund a paid payment (created by create_payment_link). Full refund by default; pass amount for a partial refund where supported. Refunds respect the same owner policy guardrails (x-agentpay-max-amount) as payments — the amount is checked before anything is sent to the gateway.

Parameters2

tx_ref	string	required	The tx_ref of the paid payment (same id used by query_payment_status)
amount	number	optional	Optional partial-refund amount in the local currency major unit. Omit for a full refund.

Raw schema

{
  "type": "object",
  "properties": {
    "tx_ref": {
      "type": "string",
      "description": "The tx_ref of the paid payment (same id used by query_payment_status)"
    },
    "amount": {
      "type": "number",
      "description": "Optional partial-refund amount in the local currency major unit. Omit for a full refund."
    }
  },
  "required": [
    "tx_ref"
  ]
}

create_subscription_link

Create a recurring subscription checkout link (KES, monthly/yearly/weekly billing) via Flutterwave. The buyer opens the URL, authorizes payment once, and is then charged automatically every period until canceled. Amount is per billing period. Respects the same owner policy guardrails as payments (the per-period amount is checked before anything is created).

Parameters5

amount_kes	number	required	Amount charged per billing period (KES major unit)
interval	string	optional	Billing period. Default "month".
description	string	required	What the subscription is for (also used as the Flutterwave plan name, <=80 chars)
customer_email	string	required	Buyer email (required by Flutterwave; receipts and renewal notices go there).
success_url	string	optional	Optional https URL to send the buyer to after subscribing.

Raw schema

{
  "type": "object",
  "properties": {
    "amount_kes": {
      "type": "number",
      "description": "Amount charged per billing period (KES major unit)"
    },
    "interval": {
      "type": "string",
      "enum": [
        "month",
        "year",
        "week",
        "day"
      ],
      "description": "Billing period. Default \"month\"."
    },
    "description": {
      "type": "string",
      "description": "What the subscription is for (also used as the Flutterwave plan name, <=80 chars)"
    },
    "customer_email": {
      "type": "string",
      "description": "Buyer email (required by Flutterwave; receipts and renewal notices go there)."
    },
    "success_url": {
      "type": "string",
      "description": "Optional https URL to send the buyer to after subscribing."
    }
  },
  "required": [
    "amount_kes",
    "description",
    "customer_email"
  ]
}

query_subscription

Check a subscription created by create_subscription_link. Query by customer_email (required); pass plan_id (returned at creation) to disambiguate when the same email has several plans. active=true when the subscription status is ACTIVE; NOT_SUBSCRIBED_YET means the buyer has not completed the first payment yet. The result includes subscription_id — keep it to cancel later.

Parameters2

customer_email	string	required	The buyer email used in create_subscription_link
plan_id	string	optional	Optional plan_id returned by create_subscription_link (disambiguates multiple subscriptions on the same email).

Raw schema

{
  "type": "object",
  "properties": {
    "customer_email": {
      "type": "string",
      "description": "The buyer email used in create_subscription_link"
    },
    "plan_id": {
      "type": "string",
      "description": "Optional plan_id returned by create_subscription_link (disambiguates multiple subscriptions on the same email)."
    }
  },
  "required": [
    "customer_email"
  ]
}

cancel_subscription

Cancel a subscription so it will not renew. Requires the subscription_id, which you get from query_subscription (Flutterwave does not expose it at creation time — the buyer must complete the first payment, then query_subscription returns it).

Parameters1

subscription_id

string

required

The subscription_id returned by query_subscription

Raw schema

{
  "type": "object",
  "properties": {
    "subscription_id": {
      "type": "string",
      "description": "The subscription_id returned by query_subscription"
    }
  },
  "required": [
    "subscription_id"
  ]
}

README.md2 KBView on GitHub

Kenya Payments MCP — let AI agents accept payments in Kenya

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

json

{
  "mcpServers": {
    "kenya-payments": {
      "type": "http",
      "url": "https://mcp-ke.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

bash

git clone https://github.com/junter1989k-ai/kenya-payments-mcp && cd kenya-payments-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Live · MCP endpoint: https://mcp-ke.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/kenya-payments-mcp · Part of a 30-country family — hub: mcp.wishpool.app

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Kenya: M-Pesa (the rail Kenya actually uses), cards, bank transfer — via Flutterwave's hosted checkout.

⚖️ Stateless translation layer: funds always flow buyer → Flutterwave → merchant directly. Never holds funds or stores credentials — no database at all.

Quick start

MCP endpoint: https://mcp-ke.wishpool.app/mcp (Streamable HTTP, stateless JSON-RPC)

Header	Value
`x-flutterwave-secret-key`	your Flutterwave secret key (FLWSECK_TEST- = test mode from dashboard.flutterwave.com, FLWSECK- = production)

Tools

Tool	What it does
`create_payment_link`	Create a KES hosted-checkout link.
`query_payment_status`	Pull-based status check; `paid=true` when PAID.

Develop

bash

node test/serve.js      # local server (http://localhost:3234/mcp)
node test/e2e.js        # protocol + validation suite (probes real Flutterwave auth errors)

Zero runtime dependencies; Node ≥ 18. MIT license.

Install

Tools (6)

create_payment_linkquery_payment_statusrefund_paymentcreate_subscription_linkquery_subscriptioncancel_subscription

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp-ke.wishpool.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "kenya-payments-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-ke.wishpool.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

create_payment_link

query_payment_status

refund_payment

create_subscription_link

query_subscription

cancel_subscription

Kenya Payments MCP — let AI agents accept payments in Kenya

Use it in 60 seconds

Or run it yourself

Quick start

Tools

Develop

Install

Remote endpoint

Related servers