Skip to main content
Glama
Privat24 Business MCP Server

Privat24 Business MCP Server

by narkov

Privat24 Business MCP Server

Unofficial Model Context Protocol server for the Privat24 Business API.

This project exposes practical MCP tools for account statements, balances, transactions, payment creation, and exchange-rate lookups so an MCP-compatible client can work with Privat24 Business through structured tool calls instead of custom glue code.

This repository is not affiliated with, endorsed by, or maintained by PrivatBank.

What It Covers

  • token-authenticated access to the Privat24 Business Autoclient API

  • account and card discovery through statement settings

  • balances and transactions for date ranges

  • interim and final statement endpoints

  • payment creation through the business API

  • current and historical exchange-rate lookups through PrivatBank's public API

  • a raw API tool for unsupported endpoints

Related MCP server: Mono-MCP

Real Use Cases

  • finance copilots that answer "show the balances for yesterday and flag accounts with low cash"

  • treasury assistants that collect statement activity for a date range and summarize outgoing payments

  • operations bots that fetch interim transactions during the day and compare them with final statements later

  • internal accounting workflows that prepare payment drafts from natural-language requests and send them to /payment/create

  • support or back-office agents that need a safe MCP layer instead of direct API scripting

  • multi-tool automations that combine Privat24 Business data with ERP, CRM, BI, or reconciliation systems

Official References

Tools

  • privat24_business_auth: verifies that the configured token can access the business API

  • privat24_business_get_settings: returns statement settings, cards, and related metadata

  • privat24_business_get_balances: returns balances from /statements/balance

  • privat24_business_get_transactions: returns statement transactions from /statements

  • privat24_business_get_interim_balances: returns data from /statements/interim/balance

  • privat24_business_get_interim_transactions: returns data from /statements/interim/transactions

  • privat24_business_get_final_balances: returns data from /statements/final/balance

  • privat24_business_get_final_transactions: returns data from /statements/final/transactions

  • privat24_business_create_payment: posts a JSON payment payload to /payment/create

  • privat24_business_get_exchange_rates: returns current rates from the public PrivatBank API

  • privat24_business_get_exchange_rate_history: returns historical rates for a DD.MM.YYYY date

  • privat24_business_call_api: raw authenticated business API call for unsupported endpoints

Environment

Copy .env.example to .env and configure:

  • PRIVAT24_BUSINESS_TOKEN: required token from Privat24 Business / Autoclient API access

  • PRIVAT24_BUSINESS_BASE_URL: defaults to https://acp.privatbank.ua/api

  • PRIVATBANK_PUBLIC_API_BASE_URL: defaults to https://api.privatbank.ua

Install

npm install

Run

npm run build
npm start

Development mode:

npm run dev

MCP Configuration Example

{
  "mcpServers": {
    "privat24-business": {
      "command": "node",
      "args": [
        "D:/usr/www/mcp-dev/privat24-business-mcp-server/dist/index.js"
      ],
      "env": {
        "PRIVAT24_BUSINESS_TOKEN": "your-token-here"
      }
    }
  }
}

Example Workflows

1. Verify access

Ask your MCP client:

Verify my Privat24 Business token and show the available statement settings.

The client should call privat24_business_auth or privat24_business_get_settings.

2. Summarize outgoing cash movement

Get transactions from 2026-03-01 to 2026-03-15 and summarize the largest outgoing payments.

The client should call privat24_business_get_transactions with:

{
  "from": "2026-03-01",
  "to": "2026-03-15"
}

3. Compare interim and final activity

Show the interim transactions for 2026-03-15, then compare them with the final transactions for the same day.

The client should call:

  • privat24_business_get_interim_transactions

  • privat24_business_get_final_transactions

4. Create a payment draft

Create a payment using this business API payload.

The client should call privat24_business_create_payment with a payload shaped to your Privat24 Business integration requirements.

Example:

{
  "payload": {
    "payerAccount": "26000000000000",
    "recipientAccount": "26000000000001",
    "recipientCode": "12345678",
    "recipientName": "Example LLC",
    "amount": 1500.25,
    "purpose": "Invoice 42"
  }
}

Use the official payment documentation above to adapt field names to your integration profile.

5. Reach an unsupported endpoint

Call the raw business API endpoint /some/custom/path with these query parameters.

The client should call privat24_business_call_api.

Notes

  • The business API implementation in this repository assumes the documented Autoclient base URL https://acp.privatbank.ua/api.

  • Current and historical FX tools use PrivatBank's public API, which does not require the business token.

  • Payment payload requirements can vary by workflow. This server intentionally leaves the payload flexible and forwards your JSON as-is.

  • If you need more endpoints, start with privat24_business_call_api, validate the request shape against the official docs, and then add a dedicated tool.

License

MIT

Available Tools

12 tools
privat24_business_authVerify Privat24 Business tokenB

Calls the statements settings endpoint to verify token access.

Inputs: no named parameters.

privat24_business_call_apiCall Privat24 Business APIC

Calls any business endpoint with arbitrary query parameters or JSON body.

Inputs: path (required), method (required), body, query.

privat24_business_create_paymentCreate a paymentC

Posts an arbitrary payment payload to /payment/create.

Inputs: payload (required).

privat24_business_get_balancesGet balancesC

Returns balances from /statements/balance for a date range or filtered cards.

Inputs: to, card, from, filters.

privat24_business_get_exchange_rate_historyGet historical exchange ratesA

Returns exchange rates for a specific date using DD.MM.YYYY format.

Inputs: date (required).

privat24_business_get_exchange_ratesGet current exchange ratesB

Returns current PrivatBank exchange rates using the public API.

Inputs: coursid.

privat24_business_get_final_balancesGet final balancesC

Returns end-of-day balances from /statements/final/balance.

Inputs: card, date, filters.

privat24_business_get_final_transactionsGet final transactionsB

Returns end-of-day transactions from /statements/final/transactions.

Inputs: card, date, filters.

privat24_business_get_interim_balancesGet interim balancesC

Returns interim balances from /statements/interim/balance.

Inputs: card, date, filters.

privat24_business_get_interim_transactionsGet interim transactionsC

Returns interim transactions from /statements/interim/transactions.

Inputs: card, date, filters.

privat24_business_get_settingsGet statement settingsB

Returns available cards, accounts, and statement-related settings.

Inputs: no named parameters.

privat24_business_get_transactionsGet transactionsC

Returns statement transactions from /statements for a date range or filtered cards.

Inputs: to, card, from, filters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource (balances, transactions, rates) and time scope (standard/interim/final), so an agent can usually pick the right one. The generic call_api overlaps with every specific endpoint, and auth vs get_settings is slightly blurry, but descriptions help clarify intent.

    Naming Consistency4/5

    All tools share the privat24_business_ prefix and use snake_case, with most following a get_<resource> pattern. create_payment and call_api fit the verb_noun style, but auth breaks the pattern slightly and get_exchange_rate_history is a minor deviation from the plural get_exchange_rates.

    Tool Count5/5

    12 tools is within the ideal range for a business banking integration. The count reflects the statement matrix, payments, exchange rates, and setup/verification without feeling bloated or too thin.

    Completeness4/5

    The set covers balances, transactions (regular/interim/final), payments, exchange rates, settings, and auth verification. It lacks dedicated payment status or detailed payment management tools, but call_api provides an escape hatch for accessing any missing endpoint.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Monobank personal account data through MCP tools, allowing users to fetch client info, accounts, and jars. It also enables retrieving account statements for specific time periods.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to retrieve and format Monobank account statements and transactions by date range.
      8 npm
      5
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      MCP server for Payme payment system (Uzbekistan). Supports transactions, statements, payment links, and balance queries via JSON-RPC 2.0.
      8
      15 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server for Sberbank business API enabling account management, balance checks, statements, payments, and counterparty operations.
      8
      44 npm
      1
      MIT