Nomba MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOMBA_CLIENT_ID | Yes | OAuth client ID | |
| NOMBA_ACCOUNT_ID | Yes | Nomba account ID | |
| NOMBA_CLIENT_SECRET | Yes | OAuth client secret |
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 |
|---|---|
| create_checkoutC | Create a checkout page |
| get_transactionC | Get transaction details |
| list_transactionsD | List transactions |
| create_transferC | Create a bank transfer |
| get_balanceB | Get account balance |
| list_terminalsC | List POS terminals |
| create_virtual_accountC | Create a virtual account |
| get_virtual_accountC | Get virtual account details |
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 8 tools
Each tool has a clearly distinct purpose targeting specific resources and actions: creating different financial entities (checkout, transfer, virtual account), retrieving balance or transaction details, and listing terminals or transactions. There is no overlap or ambiguity in functionality.
All tools follow a consistent verb_noun pattern with clear action prefixes (create_, get_, list_) and descriptive nouns. The naming is uniform and predictable throughout the set.
With 8 tools, the server is well-scoped for a payment/financial domain, covering key operations like creation, retrieval, and listing without being overly broad or sparse. Each tool serves a clear, necessary function.
The toolset provides strong coverage for core financial workflows, including creation and retrieval of transactions, virtual accounts, and checkouts, plus balance and terminal listing. A minor gap exists in update/delete operations for resources like virtual accounts or transactions, but agents can work around this.