DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to get alerts when a balance or payment changes with Bankmcp

Create watches that notify a Slack channel or webhook when balances or payments cross a rule.

  • Money
  • Advanced
  • 60 minutes
  • From the README
  • Any agent

Credentials. The webhook URL can receive account balance and payment details, so use a private Slack channel or an endpoint you control.

Who it is forA person who wants to know about low balances or an overdue incoming payment without checking the bank every day.

The problemBalances and incoming payments change without notice, and checking manually is slow and easy to forget.

The outcomeA server-side watch sends a notification to your webhook when a rule fires, checked at most four times a day.

What you need first

  • A free Enable Banking account and an application with a key file (.pem)
  • Node 24 or newer for running on your own machine
  • A bank covered by Enable Banking (the README says 2,700+ European banks)
  • For hosted use: a container host with a persistent volume at /data and a public https address
  • Your MCP client, such as Claude Code, Claude Desktop or Cursor

Steps

  1. Set the environment variable NOTIFY_WEBHOOK_URL on your server to a Slack incoming webhook or a URL that accepts a JSON POST.
  2. Deploy BankMCP on a small server using one of the listed hosts, or run the Docker command docker run -d --name bankmcp --restart unless-stopped -p 8080:8080 -v bankmcp-data:/data ghcr.io/noskillish/bankmcp:latest. (inferred, check the README)
  3. In your assistant, say "connect my bank" and confirm the accounts appear.
  4. Ask the assistant to create a watch, for example "Tell me when my balance drops below 5,000".
  5. Ask the assistant to list your watches with list_watches to confirm the rule is saved.

Prompt for your agent

Using the repo noskillish/bankmcp, create a balance watch on the account labelled <account label> with a threshold of <amount>. Expected output: a saved watch returned by list_watches with its rule and webhook target. Verify that the webhook URL is set and that the watch shows the correct threshold.

Caveat. Watches only check accounts about four times a day because of the PSD2 limit for unattended access, so they are not real-time alerts.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page