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. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tunzaa/tunzaa_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server