Tunzaa MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TUNZAA_API_KEY | No | Your Tunzaa API key for accessing live data | |
| TUNZAA_SECRET_KEY | No | Your Tunzaa secret key for accessing live data | |
| TUNZAA_ENVIRONMENT | No | The 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
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tokenA | Retrieve a Tunzaa access token. Refreshes internal token automatically. Use this to verify your API credentials and see the internal token structure. |
| initiate_paymentB | Initiate a payment request (M-Pesa, etc.) via Tunzaa. 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_callbackB | Simulate or handle the callback payload sent by Tunzaa 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_installmentsA | List existing installment plans. Use this to see how pagination and plan summaries are returned by the Tunzaa 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 Tunzaa API. |
| delete_installment_planC | Cancel/Delete an existing installment plan. Use this to verify the cancellation response structure. |
| create_demo_shopB | The ultimate grounding tool. Executes a full sequence of Tunzaa 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Authentication & Token Management | Best practices for managing Tunzaa Bearer tokens and environment headers. |
| Webhook Integration & Security | How to securely handle payment callbacks from Tunzaa. |
| Node.js Express Integration snippet | A golden example of a Tunzaa payment integration using Express.js. |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Tunzaa API workflow, such as token retrieval, payment initiation, installment plan management, and callback handling. There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one based on the task.
All tool names follow a consistent verb_noun pattern with clear, descriptive actions like 'create', 'get', 'list', 'edit', 'delete', 'initiate', and 'handle'. The naming is uniform throughout, using snake_case consistently without any deviations or mixed conventions.
With 10 tools, the server is well-scoped for its purpose of demonstrating and interacting with the Tunzaa API. Each tool serves a specific, necessary function in the payment and installment workflow, avoiding bloat while covering core operations from authentication to transaction management.
The tool set provides complete coverage of the Tunzaa API domain, including token management, payment initiation and status checks, full CRUD operations for installment plans, and webhook callback handling. There are no obvious gaps, ensuring agents can handle the entire integration lifecycle without dead ends.