MCP.so
ログイン
T

Tanzania Payments MCP Server

@junter1989k-ai

基本情報

ライセンス

MIT

トランスポート

stdio

作者

junter1989k-ai

投稿者

junter1989k-ai

Tanzania Payments MCP Server について

概要はまだありません

Tanzania Payments MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

Tanzania Payments MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

What is Tanzania Payments Mcp?

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor, etc.) accept payments in Tanzania via Flutterwave's hosted checkout. It supports M-Pesa Tanzania, Tigo Pesa, Airtel Money, and cards. The server is stateless—never holds funds or stores credentials.

How to use Tanzania Payments Mcp?

Connect to the endpoint https://mcp-tz.wishpool.app/mcp (Streamable HTTP, stateless JSON-RPC). Set the HTTP header x-flutterwave-secret-key to your Flutterwave secret key (FLWSECK_TEST- for test mode, FLWSECK- for production). Use the create_payment_link tool to generate a TZS hosted-checkout link and query_payment_status to check if payment is paid.

Key features of Tanzania Payments Mcp

  • Stateless translation layer – no database, never stores credentials.
  • Remote MCP server via Streamable HTTP transport.
  • Accepts M-Pesa Tanzania, Tigo Pesa, Airtel Money, and cards.
  • Single endpoint with secret key authentication.
  • Two tools: create payment link and query payment status.

Use cases of Tanzania Payments Mcp

  • AI agents handling checkout for Tanzanian customers.
  • Automated payment collection in chatbots or virtual assistants.
  • Pull-based payment confirmation for order fulfillment.

よくある質問

1

What payment methods are supported?

M-Pesa Tanzania, Tigo Pesa, Airtel Money, and cards – all via Flutterwave's hosted checkout, denominated in TZS.

2

How do I test payments?

Use a Flutterwave secret key starting with `FLWSECK_TEST-` (from your Flutterwave test dashboard). The MCP server has zero runtime dependencies; Node ≥ 18 is only required for local development.

3

Where does my money go?

Funds flow directly from buyer to Flutterwave to the merchant. The MCP server never holds or routes funds – it's a stateless translation layer.

4

What transport does the server use?

Streamable HTTP (stateless JSON-RPC). Authentication is via the `x-flutterwave-secret-key` HTTP header.

5

Are there any known limits?

No limits are documented in the README, but the server is remote and stateless – performance depends on Flutterwave availability.

コメント

マーケットプレイスの他のコンテンツ