
Mpesa Mcp
Wire M-Pesa STK pushes, Daraja callbacks, and Africa’s Talking SMS/airtime into your agent so East Africa payment flows ship from the same chat session.
Overview
M-Pesa MCP is a Build-phase MCP server that links AI agents to Safaricom Daraja M-Pesa payments and Africa’s Talking SMS/airtime over stdio.
What is this MCP server?
- PyPI mpesa-mcp v0.1.2 stdio server combining M-Pesa (Daraja) and Africa’s Talking
- Required Daraja vars: MPESA_CONSUMER_KEY, MPESA_CONSUMER_SECRET, MPESA_SHORTCODE, MPESA_PASSKEY
- MPESA_ENV toggles sandbox vs production Lipa Na M-Pesa online flows
- Africa’s Talking AT_API_KEY path for SMS and airtime alongside payments
- Built for AI agents serving Kenya and East Africa mobile-money users
- PyPI package mpesa-mcp version 0.1.2
- Stdio transport; 5+ documented MPESA env vars plus AT_API_KEY
- MPESA_ENV supports sandbox and production per manifest
What problem does it solve?
East Africa founders waste days jumping between Daraja docs, callback code, and SMS providers while the agent cannot safely initiate or verify M-Pesa flows.
Who is it for?
Solo builders launching Kenya/East Africa products who need agent-assisted M-Pesa STK and SMS from Claude Code or Cursor during integration sprints.
Skip if: Global card-only stacks, teams without Daraja credentials, or merchants who need PCI/card rails instead of mobile money.
What do I get? / Deliverables
You register one MCP server so your agent can operate documented M-Pesa and Africa’s Talking tools with env-based secrets and sandbox-first testing.
- MCP tools for M-Pesa payment flows with sandbox/production env switch
- Africa’s Talking SMS and airtime hooks for agent-driven ops
- Stdio registration pattern for regional fintech prototyping
Recommended MCP Servers
Journey fit
Payment and telco rails belong in Build when you connect a real product to Safaricom Daraja and regional messaging—not in late Launch SEO work. Integrations is the shelf for third-party payment and SMS APIs your backend or agent will call in production.
How it compares
Regional payments and telco MCP bridge—not a full billing SaaS or Shopify plugin.
Common Questions / FAQ
Who is M-Pesa MCP for?
Developers building for M-Pesa users who want Daraja and Africa’s Talking exposed as MCP tools for AI-assisted integration and ops.
When should I use M-Pesa MCP?
During Build integrations when you are wiring checkout, payouts, or SMS notifications for East African customers and testing in Daraja sandbox.
How do I add M-Pesa MCP to my agent?
Install mpesa-mcp from PyPI, set MPESA_* and optional AT_API_KEY env vars, choose MPESA_ENV sandbox or production, and add the stdio server to your MCP config.