lunchmoney-mcp-v2
Related Servers
Alternatives to lunchmoney-mcp-v2
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and MCP clients to manage personal finance data through the LunchMoney API, including transactions, budgets, categories, tags, accounts, recurring items, and crypto balances.22 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to interact with your Lunch Money personal finance data, providing tools for managing transactions, categories, budgets, assets, and accounts.1522 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and other MCP clients to manage personal finance data via the LunchMoney API, covering transactions, categories, tags, budgets, recurring items, accounts, crypto, and balance history.22 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants and other MCP clients to manage personal finances through the LunchMoney API, covering transactions, budgets, categories, tags, recurring items, accounts, crypto, and balance history.22 npm-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and MCP clients to manage personal finance data through LunchMoney's API, including transactions, budgets, categories, tags, accounts, and balances.22 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and other MCP clients to manage personal finance data through LunchMoney's API, including transactions, budgets, categories, tags, accounts, crypto, and balance history.22 npmMIT
TDQS
Scored across 14 tools
Each tool targets a distinct resource or operation. Read (list/get), write (manage), batch (bulk_update), and structural operations (split/group) are clearly separated, minimizing the chance of misselection.
The naming follows a verb_noun convention with intuitive prefixes like get_/list_, manage_, bulk_update_, split_, and group_. The only minor inconsistency is mixing get_ and list_ for read operations (e.g., get_accounts vs list_transactions), but the pattern is still predictable.
With 14 tools, the server covers user info, transactions, categories, tags, accounts, recurring items, and budget summaries—each earning its place. This is within the ideal 3-15 range and feels well-scoped.
The tool set provides solid coverage for core CRUD on transactions, categories, tags, and accounts, plus advanced transaction operations (split/group/bulk update). Minor gaps exist, such as recurring items being read-only and no bulk delete, but agents can work around these.