Avie Money Lover MCP / Local Bridge

Unofficial Money Lover integration for two workflows:

1. MCP server — expose Money Lover read/write tools to an MCP-capable client.

2. GPT + local bridge — let ChatGPT prepare/review statement JSON while your own machine keeps the Money Lover token/cookie and performs the final import.

Unofficial project. This repository is not affiliated with, endorsed by, or sponsored by Money Lover. It uses web endpoints observed from the Money Lover web app. Those endpoints, authentication flows, category behavior, and anti-bot requirements can change without notice.

What it can do

• Read authenticated user info

• List wallets and wallet categories

• Read transactions by date range

• Resolve Money Lover user_category_v2 source IDs to runtime IDs using transaction history

• Preview a single transaction without writing

• Add a transaction with duplicate protection

• Preview a bank/card statement batch

• Reconcile expense − income against a statement total

• Flag exact duplicates, probable duplicates, unresolved categories, and review rows

• Import sequentially only after explicit confirmation

• Verify created transactions by reading them back

• Safely re-run after a partial import: exact duplicates are skipped

Related MCP server: monarch-mcp

Requirements

• Windows 10/11, macOS, or Linux

• Node.js 22+

• A Money Lover account you control

• For reliable writes: a fresh wallet-owner session, current browser cookie/cf_clearance if required, and the matching browser User-Agent

Quick start

git clone https://github.com/haonguyen97ftu/avie-moneylover-mcp.git
cd avie-moneylover-mcp
npm install
npm test

Windows helper setup

scripts\setup-windows.cmd

Set credentials in the current shell only:

set "MONEYLOVER_ACCESS_TOKEN=YOUR_FRESH_OWNER_TOKEN"
set "MONEYLOVER_CF_CLEARANCE=YOUR_CURRENT_CF_CLEARANCE_VALUE"
set "MONEYLOVER_USER_AGENT=YOUR_EXACT_BROWSER_USER_AGENT"

Then run:

scripts\doctor.cmd

Recommended GPT + local workflow

Bank/card statement
        ↓
ChatGPT extracts + categorizes
        ↓
statement JSON
        ↓
local preview
        ↓
review / duplicate / reconciliation checks
        ↓
explicit IMPORT confirmation
        ↓
Money Lover
        ↓
local verification report

Do not paste Money Lover tokens, refresh tokens, passwords, browser cookies, or cf_clearance into ChatGPT, GitHub issues, logs, or screenshots. ChatGPT only needs the statement plus the generated preview/result JSON.

Preview a statement

scripts\preview.cmd data\your-statement.json

Import after review

scripts\import.cmd data\your-statement.json

The importer requires you to type exactly:

IMPORT

before writes begin.

See docs/HUONG_DAN_SU_DUNG.md for the complete Vietnamese guide.

API behavior observed

Authenticated requests currently use:

Authorization: AuthJWT <access_token>

Observed endpoints:

Writes may require browser-like headers and a current Cloudflare session. Supported environment variables include:

• MONEYLOVER_ACCESS_TOKEN

• MONEYLOVER_CF_CLEARANCE

• MONEYLOVER_COOKIE

• MONEYLOVER_USER_AGENT

• MONEYLOVER_TIMEOUT_MS

• MONEYLOVER_CATEGORY_LOOKBACK_DAYS

• MONEYLOVER_WRITE_DELAY_MS

Batch statement format

Start from data/example-statement.json. Full field documentation is in docs/STATEMENT_FORMAT.md.

Preview:

npm run preview -- data\your-statement.json

Import:

npm run import -- data\your-statement.json

Optional flags:

• --allow-review — include rows intentionally left in review after you inspect them

• --allow-mismatch — bypass statement reconciliation protection; use only when you understand the discrepancy

• --allow-shared-wallet — bypass the owner safety check; shared-wallet writes may still fail

• --confirm IMPORT — non-interactive confirmation; not recommended for ordinary manual use

Safety defaults

The importer refuses to write when:

• any row is blocked

• a review row exists unless --allow-review is supplied

• the statement reconciliation difference is non-zero unless --allow-mismatch is supplied

• the authenticated user is not the wallet owner unless --allow-shared-wallet is supplied

• confirmation is not exactly IMPORT

Amounts must be positive numbers.

Category v2

Some accounts expose a source/template category ID from /category/list, while /transaction/add expects a different runtime category ID. The bridge learns this mapping from existing transactions.

If a category has never appeared in history, copy:

config/runtime-category-overrides.example.json

to:

config/runtime-category-overrides.json

and add the runtime ID observed from a real browser transaction request. The local override file is ignored by Git.

Public-repo safety

The repository is configured to avoid committing local financial data by default:

• data/*.json is ignored except the sanitized example

• out/ is ignored

• .env* is ignored

• local runtime category overrides are ignored

• local session helper files are ignored

Before pushing, run:

npm run repo:check
npm test

Then inspect git status manually.

Security

If a token, password, refresh token, browser cookie, or cf_clearance value is ever exposed, treat it as compromised and rotate/revoke the session. See SECURITY.md.

Contributing

Bug reports and pull requests are welcome. Please read CONTRIBUTING.md before submitting changes. Never include real financial statements, account identifiers, tokens, or cookies in issues or test fixtures.

Documentation

• Vietnamese usage guide

• Statement JSON format

• Architecture

• GitHub publishing guide

• Security policy

• Changelog

• GPT statement normalization prompt

• GPT preview review prompt

License

MIT — see LICENSE.