zenmoney-mcp
Related Servers
Alternatives to zenmoney-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityDmaintenanceAn MCP server for the Zenmoney personal-finance API that exposes read access to accounts, transactions, categories, budgets, merchants, and reminders, plus the ability to create transactions.8MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for personal finance management. Enables natural language expense logging, budgeting, recurring charge detection, and statement import with deterministic local calculations.-
- AlicenseNot gradedqualityDmaintenanceMCP server for the BudgetBakers Wallet REST API, enabling management of transactions, accounts, categories, budgets, labels, and more through natural language.29 npmMIT
- -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.-
- AlicenseAqualityBmaintenanceMCP server for YNAB. Reconcile bank statements, itemize receipts, manage transactions — all through natural language.35127 npm9AGPL 3.0
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.