zenmoney-mcp
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., "@zenmoney-mcp How much did I spend on groceries 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.
zenmoney-mcp
MCP server for ZenMoney — access your personal finance data from any MCP-compatible AI client (Claude Desktop, Cursor, etc.).
Features
Tool | Description |
| Sync data with ZenMoney (run first) |
| List wallets, cards, and cash accounts |
| List expense/income categories with hierarchy |
| List known merchants/payees |
| List and filter recent transactions |
| Add an expense transaction |
| Add an income transaction |
| Transfer money between accounts (including cross-currency) |
| Get auto-suggested category for a payee |
| Find likely duplicates, uncategorized entries, and unusually large transactions |
| Replace the category of an existing transaction |
| Update a transaction's payee/payer or comment |
| Delete an existing transaction |
| Create an income, expense, or combined category |
| Rename a category or change its hierarchy and budget settings |
| Delete an unused leaf category |
| Move transactions into another category and remove the source category |
All tools that modify ZenMoney advertise MCP write/destructive annotations so compatible clients can request approval before executing them. Approval behavior still depends on the MCP client's policy and configuration.
Related MCP server: accounting-mcp-server
Prerequisites
Node.js >= 18
A ZenMoney account
API token from zerro.app/token
Quick start
No cloning or building needed — just add to your MCP client config:
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"zenmoney": {
"command": "npx",
"args": ["-y", "zenmoney-mcp"],
"env": {
"ZENMONEY_TOKEN": "your_token_here"
}
}
}
}Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"zenmoney": {
"command": "npx",
"args": ["-y", "zenmoney-mcp"],
"env": {
"ZENMONEY_TOKEN": "your_token_here"
}
}
}
}Claude Code
claude mcp add zenmoney -- npx -y zenmoney-mcpReplace your_token_here with your token from zerro.app/token.
Claude Desktop (MCPB bundle)
If you prefer a one-click install without editing JSON, build a .mcpb bundle and drag it into Claude Desktop → Settings → Extensions:
npm install
npm run pack:mcpb
# → dist/zenmoney-mcp-<version>.mcpbOn install, Claude Desktop will prompt for your ZenMoney token (stored in the OS keychain).
From source
git clone https://github.com/a-tarasoff/zenmoney-mcp.git
cd zenmoney-mcp
npm install
npm run build
cp .env.example .env # add your tokenUsage
Once configured, start a conversation and ask your AI client to:
Sync first — "Sync my ZenMoney data"
Browse — "Show me my accounts", "List my categories"
Query — "Show expenses for the last 7 days", "List transactions from January 1–31", "How much did I spend on groceries?"
Add transactions — "Add a 500 RUB expense for coffee today"
Transfer — "Transfer 1000 USD from Checking to Euro Card, received 920 EUR"
Review — "Review July for duplicate, uncategorized, and unusually large transactions"
Organize categories — "Create an expense category named Utilities under Housing"
Clean up — "Change this transaction to Groceries" or "Merge Dining Out into Food"
Transaction listing and review tools return transaction IDs. Use those IDs for precise edits instead of relying on ambiguous dates, amounts, or payee names.
Contributing
PRs welcome! Feel free to open issues for bugs or feature requests.
License
Available Tools
17 toolsadd_expenseA
Add an expense transaction to ZenMoney. Requires account name/id, amount, and date. Optionally accepts category, payee, and comment. Codex must request user approval before calling this tool.
Inputs: date (required), amount (required), account (required), payee, +2 more.
add_incomeA
Add an income transaction to ZenMoney. Codex must request user approval before calling this tool.
Inputs: date (required), amount (required), account (required), payee, +2 more.
add_transferA
Transfer money between two accounts in ZenMoney. For cross-currency transfers, specify both outcome_amount (source) and income_amount (destination). For same-currency transfers, just use outcome_amount (or amount as alias). Codex must request user approval before calling this tool.
Inputs: date (required), to_account (required), from_account (required), amount, +3 more.
change_transaction_categoryADestructive
Replace the category of one existing ZenMoney transaction. Codex must request user approval before calling this tool.
Inputs: category (required), transaction_id (required).
create_categoryB
Create a ZenMoney category. Codex must request user approval before calling this tool.
Inputs: kind (required), title (required), parent_category, required_expense, +1 more.
delete_categoryADestructive
Delete an empty ZenMoney category. Refuses categories used by transactions or containing children. Codex must request user approval before calling.
Inputs: category (required).
delete_transactionADestructive
Permanently delete one ZenMoney transaction. Codex must request user approval before calling this tool.
Inputs: transaction_id (required).
list_accountsA
List all user accounts (wallets, cards, cash). Sync must be done first.
Inputs: include_archived.
list_categoriesA
List all expense/income categories (tags) with their hierarchy. Sync must be done first.
Inputs: no named parameters.
list_merchantsA
List known merchants/payees. Sync must be done first.
Inputs: no named parameters.
list_transactionsA
List transactions. By default returns the last 30 days; pass start_date/end_date for an arbitrary period (e.g. Jan 1–31). Sync must be done first.
Inputs: days, limit, account, category, +2 more.
merge_categoriesADestructive
Move transactions from one leaf category into another, then delete the source. Codex must request user approval before calling.
Inputs: source_category (required), target_category (required).
review_transactionsA
Review a period for likely duplicate, uncategorized, and unusually large transactions. Returns transaction IDs and never changes data.
Inputs: end_date (required), start_date (required), large_amount_rub, duplicate_window_days.
suggest_categoryA
Get ZenMoney's auto-suggestion for category and merchant based on a payee name. Useful for categorizing receipts.
Inputs: payee (required).
sync_dataA
Sync data with ZenMoney. Run this first before using other tools. Use force_full=true to re-download everything.
Inputs: force_full.
update_categoryADestructive
Rename or configure an existing ZenMoney category. Codex must request user approval before calling this tool.
Inputs: category (required), kind, new_title, clear_parent, +3 more.
update_transaction_detailsADestructive
Update the payee/payer and/or comment of one existing ZenMoney transaction. Omitted fields stay unchanged; null clears a field. Codex must request user approval before calling this tool.
Inputs: transaction_id (required), payee, comment.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Each tool targets a distinct action-resource pair: sync, list accounts/categories/merchants/transactions, CRUD for categories, transaction entry and modification, and review/suggest. There is no meaningful overlap or ambiguity in purpose.
Tool names consistently use snake_case verb_noun patterns (e.g., list_transactions, create_category, delete_transaction). Minor deviations: 'change_transaction_category' uses 'change' while 'update_transaction_details' uses 'update' for similar operations, and 'merge_categories' pluralizes where singular is used elsewhere.
At 17 tools, the count is slightly above the typical 3-15 range but nearly every tool serves a distinct function in sync, listing, category management, and transaction lifecycle. No tool feels redundant or token.
The server covers the core CRUD lifecycle for categories and transactions, plus sync, review, and auto-suggestion. Missing account mutation (create/update/delete) is a notable but acceptable gap since the focus appears to be on transaction and category management.
Maintenance
Related MCP Connectors
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
MCP server for AI dialogue using various LLM models via AceDataCloud
Read-only finance MCP server. Connects your banks, cards, payment apps, books and payroll into one ledger for your AI. Can't move money. Open source (AGPL-3.0), free during beta.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for YNAB. Reconcile bank statements, itemize receipts, manage transactions — all through natural language.35109 npm9AGPL 3.0
- -licenseNot gradedqualityNot gradedmaintenanceA personal accounting MCP server that enables AI assistants to record and query financial transactions through natural language, supporting income/expense tracking, balance inquiry, and monthly summaries.-
- AlicenseBqualityCmaintenanceRead-only MCP server for ZenMoney that syncs financial data into memory and exposes it through tools and resources, enabling agentic analysis of transactions and spending patterns.1016 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for personal finance management. Enables natural language expense logging, budgeting, recurring charge detection, and statement import with deterministic local calculations.-