Money Lover MCP Server
This MCP server enables AI assistants to interact with Money Lover financial data through authentication and comprehensive management tools.
Authentication & User Management
Login using email and password credentials to obtain JWT tokens
Retrieve user profile information associated with authenticated sessions
Automatic token caching and refresh in
~/.moneylover-mcp/directoryEnvironment-based authentication (EMAIL/PASSWORD) with manual token override support
Wallet Operations
List all wallets accessible to the authenticated user
Access expense/income categories specific to a designated wallet ID
Transaction Management
Query transactions within a specified date range for any wallet
Create new transactions by specifying wallet ID, category ID, amount, date, and optional notes or related parties
Integration
Works with MCP-compliant clients like Claude Desktop and Cursor through stdio interface
Configurable via environment variables for seamless setup
Provides a Node.js implementation of an MCP server that wraps the Money Lover REST API, enabling authentication, wallet management, transaction querying, and creation of new transactions
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Money Lover MCP Server show my spending for this month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Money Lover MCP Server
Node.js implementation of a Model Context Protocol (MCP) server that wraps the unofficial Money Lover REST API. The server exposes authentication and wallet management capabilities as MCP tools, enabling AI assistants or compatible MCP clients to login, inspect wallets, query transactions, and create new transactions.
Features
Login tool returns Money Lover JWT tokens via the public OAuth flow.
Tools for retrieving user info, wallets, categories, and transactions.
Tool for adding new transactions, mirroring the behaviour of the Go reference client.
Stdio-based server entrypoint that can be consumed by MCP-aware clients.
Node-friendly REST wrapper for direct programmatic usage.
Related MCP server: LunchMoney MCP Server
Prerequisites
Node.js 22 or newer.
Money Lover account credentials for authentic API access.
Installation
npm installUsage
Launch the MCP server over stdio (suitable for tools such as Claude Code, Cursor, or other MCP hosts):
npm startMCP Client Configuration
Configure an MCP-compliant client (for example, Claude desktop or Cursor) to invoke the published package via npx and supply credentials through environment variables:
{
"mcpServers": {
"mcp-moneylover": {
"command": "npx",
"args": ["@ferdhika31/moneylover-mcp@latest"],
"env": {
"EMAIL": "alamat-email-anda@example.com",
"PASSWORD": "kata-sandi-anda"
}
}
}
}The server automatically logs in with the provided credentials and refreshes the session token when required. Supplying a token argument to tools overrides the environment-based authentication.
Tokens resolved through the login tool or environment credentials are cached per-email under ~/.moneylover-mcp/. Cached tokens are reused on subsequent runs and refreshed automatically when the API reports they have expired.
The server registers the following tools:
Tool | Description | Required Arguments |
| Retrieves a JWT token using email & password. |
|
| Returns profile information tied to the token. |
|
| Lists wallets available to the authenticated user. |
|
| Lists categories for a wallet. |
|
| Retrieves transactions in a date range. |
|
| Creates a new transaction. |
|
Tokens are not persisted; provide them explicitly when invoking tools other than login.
Library Usage
The underlying REST wrapper is available for reuse:
import { MoneyloverClient } from '@ferdhika31/moneylover-mcp';
const token = await MoneyloverClient.getToken(email, password);
const client = new MoneyloverClient(token);
const wallets = await client.getWallets();Testing
Run the automated test suite:
npm testTests rely on mocked fetch responses and do not hit the live Money Lover service.
Security Notes
Never commit real credentials or tokens.
The project intentionally avoids persisting tokens; MCP clients should store secrets securely on their side.
Cached tokens are stored locally with file permissions restricted to the current user. Delete the
~/.moneylover-mcp/directory if you need to revoke stored sessions.
Available Tools
6 toolsadd_transactionAdd TransactionC
Create a new transaction in a wallet.
Inputs: walletId (required), categoryId (required), amount (required), date (required), +3 more.
get_categoriesGet CategoriesB
Retrieve categories for a specific wallet.
Inputs: walletId (required), token. Returns: categories
get_transactionsGet TransactionsB
Fetch transactions for a wallet between two dates.
Inputs: walletId (required), startDate (required), endDate (required), token.
get_user_infoGet User InfoA
Retrieve the Money Lover user profile associated with the provided token.
Inputs: token.
get_walletsGet WalletsB
List all wallets accessible to the authenticated user.
Inputs: token. Returns: wallets
loginLogin to Money LoverA
Authenticate using Money Lover credentials to retrieve a JWT token.
Inputs: email (required), password (required). Returns: token
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: authentication, user info, wallets, categories, and transactions (add and fetch). No two tools overlap in functionality.
Most tools follow a consistent verb_noun pattern (e.g., add_transaction, get_categories), but 'login' deviates by being a single verb. This minor inconsistency does not cause confusion.
With 6 tools, the server is well-scoped for a personal finance API covering essential operations like authentication, wallet and category retrieval, and transaction management.
The set covers basic CRUD for transactions (only create and read) and read-only for categories and wallets. Missing update/delete for transactions and full wallet/category management, which are notable gaps for a finance tool.
Maintenance
Related MCP Connectors
Log, query, and edit expenses, budgets, and accounts in Manilo (formerly Ledgy) from any MCP-compatible AI assistant.
Log, query, and edit expenses, budgets, and accounts in Manilo from any MCP-compatible AI assistant.
Personal finance for AI agents: accounts, budgets, goals, 9-strategy debt payoff, reports. OAuth 2.1
Track expenses, budgets, balances, transfers, and multi-currency reports with OAuth-secured tools.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to query and manage personal finance data through the unofficial Money Lover REST API. It provides 27 tools covering authentication, wallets, categories, transactions, events, debts, and static configuration with both read and write capabilities.3314 npmISC
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants and MCP clients to interact with personal finance data for transaction management, budgeting, recurring expenses, accounts, categories, tags, crypto, and balance history via LunchMoney's API.41 npm-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants and other MCP clients to manage personal finances through the LunchMoney API, covering transactions, budgets, categories, tags, recurring items, accounts, crypto, and balance history.41 npm-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and MCP clients to access and manage personal finance data through LunchMoney's API, including transactions, budgets, categories, tags, recurring items, accounts, crypto, and balance history.41 npmMIT