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
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.
Prerequisites
Node.js 22 or newer.
Money Lover account credentials for authentic API access.
Installation
Usage
Launch the MCP server over stdio (suitable for tools such as Claude Code, Cursor, or other MCP hosts):
MCP 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:
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. |
,
,
,
,
(YYYY-MM-DD); optional
,
|
Tokens are not persisted; provide them explicitly when invoking tools other than login.
Library Usage
The underlying REST wrapper is available for reuse:
Testing
Run the automated test suite:
Tests 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.