Money Lover

What Money Lover MCP server does

Money Lover MCP server lets an MCP-compatible AI client read data from a Money Lover account and, optionally, create transactions. The available read operations cover wallets, income and expense categories, transactions within a date range, and spending totals grouped by category and currency.

The project is unofficial. Money Lover does not provide a public API, so the server uses undocumented web endpoints also used by the Money Lover web application. Those endpoints may change or stop working, and the project notes that their use could conflict with Money Lover's terms. Treat the integration as an account-risk decision, back up financial data, and test with a disposable wallet before relying on it.

How it works

The server communicates with the MCP client over standard input and output. Authentication is performed through Money Lover's web services. The password is used during login and is not stored; an authentication token is kept locally in a file with restrictive permissions. Secrets are not returned to the model or written to logs.

Network requests are limited to Money Lover's HTTPS hosts, web.moneylover.me and oauth.moneylover.me. Redirects are not followed, and the documented implementation does not send telemetry or perform update checks.

Wallets and categories are cached in memory for five minutes by default. The wallet listing indicates whether its result came from cache, and refresh: true requests current balances. Adding a transaction clears cached balances. If a requested name is absent from the cache, the server performs a fresh fetch.

Setup and configuration

You can install a release binary for macOS, Linux, or Windows, build from source with Rust 1.89 or newer, or install an MCPB bundle for clients that support that format. Source and binary builds use the locked dependency versions in Cargo.lock.

Log in once from a terminal. The password is entered through a hidden prompt, and only the resulting token is retained. MCPB clients can instead collect the email and password through their configuration flow, or reuse a token created by the command-line login process.

Write access is disabled by default. Set MONEYLOVER_ALLOW_WRITE=true to register the transaction-creation tool. The server still applies a server-side guard when writes are enabled. Verify release archives with the supplied SHA-256 checksums and build-provenance attestation before use.

Tools and capabilities

• list_wallets returns wallet names, currencies, balances, and cache status. A refresh option requests live balances.
• list_categories returns income and expense categories, optionally limited to a wallet.
• list_transactions retrieves date-range transactions in newest-first order. The default limit is 50 and the maximum is 200.
• summarize_spending groups date-range totals by category and currency.
• add_transaction creates a transaction when write mode is enabled and supports a dry-run option.

Names are used instead of internal IDs. Matching is exact apart from letter case; unknown or ambiguous names produce an error with candidate names rather than causing the server to guess. Amounts must be positive, with income or expense determined by the selected category. Supply a transaction type when a category name exists in both forms. Dates use YYYY-MM-DD in the configured timezone, and monetary values are represented as decimal strings rather than floating-point numbers.

Limitations and notes

The Money Lover MCP server is not affiliated with or supported by Money Lover. Undocumented endpoints can break without notice, and the repository disclaims responsibility for account restrictions, incorrect transactions, or data loss. Money Lover tokens are full-access because the service does not offer scoped read-only tokens; the server provides read-only behavior by withholding write tools unless explicitly enabled. Changes made directly in the Money Lover application may remain hidden until the cache expires or a refresh is requested.

The project is released under the MIT license. Release binaries are not signed with Apple or Microsoft certificates, so macOS Gatekeeper or Windows SmartScreen may require a confirmation after verification.