Bank statement

What bank statement MCP server does

The bank statement MCP server turns exported bank CSV files into a ledger stored on the local machine. It can locate a header beneath introductory text, identify date, description, amount or debit-and-credit, and currency columns, and interpret common date and number formats. Supported input handling includes UTF-8 and UTF-16 files, common line endings, quoted fields, mixed currencies, accounting parentheses, and trailing minus signs.

Imported debits become negative values and credits become positive values. Each transaction receives a duplicate-detection hash based on its date, amount, currency, description, and occurrence index. This means repeated identical transactions remain separate, while importing the same statement again does not add another copy.

How it works

Use statement_import to load a CSV and receive details about detected columns and formats, stored rows, duplicates, and skipped lines. A blank or dash amount is skipped instead of being treated as zero. If a date such as 03/04/2026 is ambiguous, the assumed order is reported.

After import, transactions_list reads a date range with optional account, category, or uncategorized filters. transactions_search performs substring matching across descriptions, counterparties, categories, and accounts; it does not interpret the query as a regular expression. statement_summary reports money in, money out, and net totals grouped by category, month, account, or counterparty, while keeping currencies separate.

The bank statement MCP server can apply categorisation rules or assign categories directly by transaction ID. Rules use case-insensitive substring matching by default. Regular expressions can be enabled, subject to a check that rejects patterns capable of exponential backtracking. recurring_detect identifies likely subscriptions and recurring charges from counterparty, amount stability, and cadence. It reports the typical amount, cadence, next expected date, and annualised cost; annualisation remains unconfirmed until three charges establish an interval.

Setup and configuration

Three supported paths are available. A hosted streamable-HTTP endpoint accepts a bearer token, or the token can be included in the URL path for clients that cannot set headers. The bare hosted endpoint requires authentication for tool calls. For local use, download the .mcpb bundle and open it in Claude Desktop, or clone the source, install dependencies, and build it before pointing an MCP client at dist/index.js.

The repository states that the npm package is not yet published, so an npx configuration will not work until publication. Claude Desktop, Claude Code, and Cursor are named client options. Pro mode can be enabled by setting MCP_LICENSE_KEY in the client configuration or by calling license_activate; license_status reports the current mode.

Tools and capabilities

• Import, list, search, categorise, summarise, and export transactions.
• Define or inspect category rules and apply categories by transaction ID.
• List imported accounts with bank, currencies, transaction count, date range, and last balance.
• Reconcile bank debits with receipts from mcp-expense-tracker using currency, amount, and a date window. The expense ledger is read-only to this tool.
• Export a selected range as CSV or JSON. Files are written atomically, and replacement of an existing file is reported.
• Use the bank://month resource for the current month's per-currency totals and the monthly_review prompt for a month-end review flow.

Limitations and notes

The bank statement MCP server keeps its ledger in plain JSON files on the local machine, according to the provided documentation. Free mode limits accounts to two, read-back history to 12 months, and category rules to five. Free reconciliation is limited to 31 days at a time, while recurring detection covers the last three months and five charges. Pro mode removes those stated account, history, and rule limits and permits broader reconciliation and recurring-charge analysis.

The source mirror includes profiles for Revolut, Wise, mBank, PKO BP, ING, and N26, plus a generic header-based reader. Reconciliation depends on the separate mcp-expense-tracker ledger being available. The hosted option requires a token; local source builds do not require the npm package to be published.