Skip to main content
Glama
gabrielmahia

mpesa-mcp

by gabrielmahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mpesa-mcp

No user-submitted related servers found.

    Related Servers

    • PayLink MCP Server by paylink-ai

      PayLink MCP Serverofficial

      paylink-ai
      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
      -

    • lipila-mcp

      zencoder01
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Lipila payment gateway, enabling AI agents to initiate mobile money and card collections, disburse funds, check transaction statuses, and verify webhook callbacks.
      1
      -

    • Minisend MCP

      itschrisoketch
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Minisend payment APIs, enabling stablecoin-to-local-currency payouts and on-ramps across Kenya, Nigeria, Ghana, and Uganda. Exposes tools for off-ramp, on-ramp, checkout, wallets, and API knowledge, with permissions-based tool visibility.
      -

    • Safaricom Daraja MCP Server

      mboya
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that integrates Safaricom's M-PESA Daraja API with Claude, enabling natural language payment processing and real-time transaction notifications.
      3
      -

    • Interswitch MCP Server

      Dairus01
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with Interswitch APIs for payments, transfers, VAS, cardless paycodes, Transaction Search, Card 360, lending, payouts, agency banking, and fintech card-processing utilities.
      74
      58 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct function: airtime sending, STK push initiation, STK push status query, transaction status by receipt, and SMS sending. There is no overlap or ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun or noun_verb pattern (e.g., airtime_send, sms_send, mpesa_stk_push), but mpesa_transaction_status lacks a verb, breaking the pattern slightly.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose, covering core M-Pesa and SMS operations without being too few or too many.

    Completeness3/5

    The set covers STK push initiation/query and basic transaction status, but lacks airtime status, B2C/C2B transfers, or account balance queries, leaving notable gaps for a full M-Pesa integration.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources