Monobank

What the Monobank MCP server does

The Monobank MCP server connects MCP clients to selected Monobank API operations. It provides three tools:

• get_currency_rates retrieves currency exchange rates from Monobank's public endpoint and does not require a token.
• get_client_info returns client information, accounts, and jars. This tool requires MONOBANK_API_TOKEN.
• get_statement retrieves transactions for an account or jar across a requested date range. It also requires MONOBANK_API_TOKEN.

The server is intended for agents that need to answer questions about exchange rates, balances, account activity, or spending based on Monobank data. It does not provide a general banking interface; the documented scope is limited to these three API operations.

How it works

The Monobank MCP server runs locally and sends API requests to Monobank. The API token is used locally and is sent only to Monobank's API. The server can start without a token, so currency-rate requests remain available. If the token is missing, the two authenticated tools return an error explaining that MONOBANK_API_TOKEN is not set.

In-memory caching helps limit repeated requests. Currency rates are cached for five minutes. Client information and each distinct statement query are cached for 60 seconds. A repeated request within the relevant period returns the cached result instead of making another API call.

Monetary values are returned in currency units rather than minor units. For example, a balance of 100,000.00 UAH is represented as 100000, not 10000000. This applies to monetary fields from both client information and statements, including commissionRate.

Setup and configuration

The README documents two installation paths. The latest .mcpb bundle can be downloaded from the repository's Releases page and opened; Claude Desktop or Claude Code then handles installation and prompts for the Monobank API token. The project requires Node.js 18.0 or newer.

For an MCP client configuration using the package, run monobank-mcp-server through npx and define MONOBANK_API_TOKEN in the server's environment. The token can be obtained from Monobank's API site. The public currency-rate tool can be used without setting the variable.

The project also documents npm run pack:mcpb for building the MCPB bundle locally. That command creates monobank-mcp-server.mcpb for installation in an MCPB-compatible client.

Tools and capabilities

The Monobank MCP server supports these concrete workflows:

• Look up current exchange rates, including prompts such as asking for a USD-to-UAH rate.
• Inspect client details, account balances, and jars.
• Retrieve transactions for the default account, a selected account, or a jar.
• Query statements using ISO 8601 dates in YYYY-MM-DD format.

For statements, the account parameter defaults to 0, representing the client's default account. Account and jar identifiers returned by get_client_info can also be used. The maximum requested statement interval is 31 days plus one hour. The to date is inclusive, uses UTC interpretation, and may be omitted to request data through the current time.

Limitations and notes

Authenticated operations depend on a valid Monobank API token. Statement queries must respect the documented maximum range, so longer periods need to be divided into multiple requests. Date interpretation is UTC, which matters when a request is intended to include activity near a day boundary.

The server is licensed under MIT. Its documented MCPB installation targets Claude Desktop and Claude Code; the available client information specifically confirms Claude Desktop compatibility. Caching can make a repeated request return data from the cache window rather than a newly fetched response.