Aza MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZA_API_KEY | Yes | Your Aza API key (starts with 'aza_live_') | |
| AZA_API_BASE | No | Override base URL for the Aza API (default: https://aza.azabill.ng/api) | https://aza.azabill.ng/api |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aza_walletA | Show the connected Aza account: name, wallet balance, and how much spending room is left on this API key today. Call this first to confirm the key works. |
| aza_list_networksA | List the mobile networks Aza can top up (MTN, Glo, Airtel, 9mobile). |
| aza_list_data_plansA | List the data bundles available on a network, with their plan codes and prices. Use a plan code with aza_buy_data. |
| aza_buy_airtimeA | Buy airtime for a Nigerian phone number, paid from the connected Aza wallet. Amount is in naira. |
| aza_buy_dataA | Buy a data bundle for a Nigerian phone number, paid from the connected Aza wallet. Get a plan code from aza_list_data_plans first. |
| aza_transactionsA | Show the most recent airtime/data/bill purchases on the connected account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: buying airtime, buying data, listing data plans, listing networks, viewing transactions, and checking wallet. No overlap or ambiguity.
All tools use the 'aza_' prefix and most follow a verb_noun pattern (e.g., aza_buy_airtime). However, 'aza_transactions' and 'aza_wallet' are noun-only, slightly breaking the pattern.
With 6 tools covering the core operations for mobile airtime/data top-ups, the count is well-scoped and appropriate for the server's purpose.
The set covers essential functions: listing networks and plans, purchasing airtime and data, checking wallet, and viewing history. Minor gaps like bill payment are acceptable given the focused domain.