Model Context Protocol server for ZenMoney personal finance management. Provides tools to synchronize, query, and manage financial data including accounts, transactions, categories, and merchants.
ZenMoney MCP has solid naming conventions (verb_noun pattern: sync_data, list_accounts, add_expense) and all 9 tools are explicitly registered with descriptions and tool annotations. However, input schemas are incomplete: most tools lack formal JSON Schema definitions with type declarations and constraints. Descriptions are adequate (100-200 chars) but lack dependency hints and recovery guidance. Parameter descriptions exist but are minimal. Output schemas are not documented. Error handling is basic, no recovery guidance or actionable error messages visible in code.
Create a new expense in ZenMoney. This mutates the account by adding one transaction; it never deletes data.
Create a new income transaction in ZenMoney. This mutates the account by adding one transaction; it never deletes data.
Create a new transfer between two ZenMoney accounts. This mutates the account by adding one transaction; it never deletes data.
List ZenMoney wallets, cards, cash, and other accounts with balances and currencies.
List expense and income categories (tags), including parent-child hierarchy.
List known ZenMoney merchants/payees, optionally filtered by title.
Three write tools (add_expense, add_income, add_transfer) have NO visible input schemas in source code. Only tool names and descriptions are registered; parameter definitions are missing entirely.
No output schemas documented for any tool. LLMs cannot predict response structure, forcing them to guess field names and types for downstream tool chaining.
Error handling is not visible in code. No recovery guidance, actionable error messages, or error classification (retryable vs fatal) documented.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | <=2025-11-25 | v2 |
List and filter ZenMoney transactions. Defaults to the last 30 days.
Ask ZenMoney to suggest a category and merchant for a payee name. This does not modify data.
Synchronize cached data with ZenMoney. Other read tools sync automatically; use force_full only to re-download all data.
list_transactions accepts 'days', 'start_date', 'end_date' but no documentation of mutual exclusivity or default behavior when both are omitted. LLMs may pass conflicting parameters.
list_merchants and list_transactions accept 'limit' parameters but lack min/max constraints in descriptions. LLMs could pass invalid values (0, negative, or >500).