Skip to main content
Glama
Tunzaa

Tunzaa MCP Server

Official
by Tunzaa

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TUNZAA_API_KEYNoYour Tunzaa API key for accessing live data
TUNZAA_SECRET_KEYNoYour Tunzaa secret key for accessing live data
TUNZAA_ENVIRONMENTNoThe environment to use (e.g., sandbox)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_tokenB

Retrieve a Malipo API access token. Refreshes internal token automatically. Use this to verify your API credentials and see the internal token structure.

initiate_paymentC

Initiate a payment request (M-Pesa, etc.) via Malipo API. Call this to inspect the response structure needed to implement mobile money flows in your local code.

get_payment_statusB

Check the status of a payment transaction. Helpful for understanding the various status states (COMPLETED, PENDING, FAILED) for your application logic.

handle_callbackC

Simulate or handle the callback payload sent by Malipo to your webhook. Essential for grounding your webhook integration code with real payload examples.

create_installmentB

Create a new installment plan. Use this to understand the complex object structure required for installment-based payments.

list_installmentsB

List existing installment plans. Use this to see how pagination and plan summaries are returned by the Malipo API.

get_installment_planB

Get details of a specific installment plan. Use this to see the precise fields returned for a plan (status, schedules, etc.).

edit_installment_planC

Update an existing installment plan. Use this to understand which fields are mutable via the Malipo API.

delete_installment_planC

Cancel/Delete an existing installment plan. Use this to verify the cancellation response structure.

create_demo_shopC

The ultimate grounding tool. Executes a full sequence of Malipo API calls (Token -> Payment -> Installments). Use this to see a 'live trace' of the API, allowing you to generate perfect integration code.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Authentication & Token ManagementBest practices for managing Malipo Bearer tokens and environment headers.
Webhook Integration & SecurityHow to securely handle payment callbacks from Malipo.
Node.js Express Integration snippetA golden example of a Malipo payment integration using Express.js.

TDQS

B3.3/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target distinct actions and resources: auth, payment initiation, callback handling, installment CRUD, and payment status. create_demo_shop is a composite trace tool that overlaps with get_token, initiate_payment, and create_installment, and its name does not perfectly match its grounding purpose, but it remains distinguishable.

Naming Consistency5/5

All names use consistent snake_case verb_noun patterns, such as get_token, initiate_payment, list_installments, and create_installment. Verbs like get, list, create, edit, and delete are used predictably across the set.

Tool Count5/5

The set has 10 tools, which fits the payment and installment API domain well. Each tool appears to earn its place by covering a distinct operation or grounding scenario.

Completeness4/5

Installment plan coverage includes full CRUD plus listing, and payment coverage includes initiation, status, callback handling, and token retrieval. Minor gaps exist on the payment side, such as listing payments, retrieving full payment details, or refund/cancel operations, but agents can largely work around these.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive