Monobank MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONOBANK_API_TOKEN | Yes | Your Monobank API token. You can obtain it at: https://api.monobank.ua/ |
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 |
|---|---|
| get_currency_ratesA | Get a basic list of currency rates from Monobank. The information can be refreshed once per 5 minutes, otherwise an error will be thrown. |
| get_client_infoA | Get information about a client and a list of their accounts and jars. The tool can be called not more than 1 time per 60 seconds, otherwise an error will be thrown. |
| get_statementC | Get Monobank statement for the time from {from} to {to} time in seconds in Unix time format. The maximum time for which it is posssible to obtain a statement is 31 days + 1 hour (2682000 seconds). The statement can be retrieved not more than once per 60 seconds, otherwise an error will be thrown. |
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 3 tools
Each tool targets a distinct resource: currency rates, client/account info, and transaction statements. No overlap or ambiguity between them.
All three tools follow the exact same get_noun pattern, with clear and uniform naming. This is perfectly consistent.
With 3 tools, the server is tightly scoped to the core Monobank personal API endpoints. Each tool earns its place, and the count is ideal for this narrow domain.
The server covers all primary read-only Monobank API operations: currency rates, client info, and statements. No obvious gaps exist for the intended functionality, as the API itself offers few other personal endpoints.