zenmoney-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENMONEY_TOKEN | Yes | Your ZenMoney API token from https://zerro.app/token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sync_dataA | Sync data with ZenMoney. Run this first before using other tools. Use force_full=true to re-download everything. |
| list_accountsA | List all user accounts (wallets, cards, cash). Sync must be done first. |
| list_categoriesA | List all expense/income categories (tags) with their hierarchy. Sync must be done first. |
| list_merchantsA | List known merchants/payees. Sync must be done first. |
| create_categoryB | Create a ZenMoney category. Codex must request user approval before calling this tool. |
| update_categoryA | Rename or configure an existing ZenMoney category. Codex must request user approval before calling this tool. |
| delete_categoryA | Delete an empty ZenMoney category. Refuses categories used by transactions or containing children. Codex must request user approval before calling. |
| merge_categoriesA | Move transactions from one leaf category into another, then delete the source. Codex must request user approval before calling. |
| add_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. |
| add_incomeA | Add an income transaction to ZenMoney. Codex must request user approval before calling this tool. |
| 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. |
| 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. |
| review_transactionsA | Review a period for likely duplicate, uncategorized, and unusually large transactions. Returns transaction IDs and never changes data. |
| change_transaction_categoryA | Replace the category of one existing ZenMoney transaction. Codex must request user approval before calling this tool. |
| delete_transactionA | Permanently delete one ZenMoney transaction. Codex must request user approval before calling this tool. |
| update_transaction_detailsA | 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. |
| suggest_categoryA | Get ZenMoney's auto-suggestion for category and merchant based on a payee name. Useful for categorizing receipts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.