IL Bank MCP 🐷💸 MCP Server

Most database access work still happens through a UI a human drives. IL Bank MCP 🐷💸 MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server that provides financial data access through automated Israeli bank and credit card data scraping. Supports all major Israeli financial institutions dynamically based on your configuration.

The short version

IL Bank MCP is a finance assistant that brings your Israeli bank data to any AI assistant. It combines a headless scraper (powered by israeli-bank-scrapers) with an MCP server, letting LLMs analyze your transactions, track spending patterns, and provide financial insights.

• Smart Analysis — Get spending breakdowns, detect recurring charges, and track merchant patterns
• Local & Secure — All data stays in a local SQLite database
• Multi-Provider — Works with most Israeli banks and credit cards
• Real-time Updates — Refresh data on-demand from any provider
• On-Demand Sync — Scrape your bank data whenever you need fresh insights

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 8 tools. What each one is for:

• get_transactions — Fetch transactions for any time period
• get_financial_summary — Income, expenses, and trends at a glance
• search_transactions — Find specific transactions by amount or description
• get_monthly_credit_summary — Credit card usage breakdown
• get_recurring_charges — Find subscriptions and repeated payments
• analyze_merchant_spending — Spot unusual spending patterns
• refresh_all_data — Update from all connected accounts
• get_scrape_status — Check when data was last updated

What it needs from you

Configuration is passed through the environment: LEUMI_USERNAME, LEUMI_PASSWORD. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. IL Bank MCP 🐷💸's toolset — get_transactions, get_financial_summary, search_transactions and 5 more — is a fair guide to whether it matches your workflow. It is maintained by glekner; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.