Monobank MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONOBANK_API_TOKEN | Yes | Your personal Monobank API token. Get it from https://api.monobank.ua/index.html |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_client_infoA | Get client information from Monobank API. This tool retrieves information about the client, their accounts, and jars. It requires a Monobank API token with the necessary permissions. |
| get_statementA | Get account statement for a given period. Rate limit: 1 request per 60 seconds. Max period: 31 days + 1 hour. Rules: 1. Fetch from default account (account_id = '0') unless another account is specified. 2. Amounts are converted from the smallest currency unit (e.g., kopiyka, cent) to the main unit and returned as decimals. 3. Transaction timestamps ('time') are converted from Unix timestamps to ISO 8601 datetime strings (UTC). 4. Fields 'id', 'invoiceId', 'counterEdrpou', and 'counterIban' are omitted from the returned results. |
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 2 tools
The two tools have clearly distinct purposes: get_client_info retrieves client metadata, accounts, and jars, while get_statement fetches transaction data for a specific period. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun naming pattern (get_client_info, get_statement) with identical verb style and snake_case formatting, making them predictable and easy to understand.
With only two tools, the server feels severely under-scoped for a banking API. Key operations like creating transactions, managing accounts, or updating client details are missing, limiting its utility for comprehensive financial tasks.
The toolset is highly incomplete for a banking domain. It only supports read operations (get_client_info, get_statement) with no ability to perform writes (e.g., transfers, payments), updates, or deletions, leaving significant gaps in typical banking workflows.