Life Admin MCP
Related Servers
Alternatives to Life Admin MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, fill, check, and build on a private plain-file memory of recurring payments such as subscriptions, insurance, EMIs, and renewals, while refusing secrets and surfacing changes for approval.GPL 3.0
- FlicenseNot gradedqualityBmaintenanceEnables personal finance management through natural language, including tracking income/expenses, categories, loans, subscriptions, budgets, and AI-powered insights, all backed by a local SQLite database.1-
- AlicenseNot gradedqualityBmaintenanceEnables households and small teams to monitor bills and subscriptions, receive evidence-backed saving proposals, and execute actions only after a signed, scope-capped mandate, with every decision and refusal logged in an auditable ledger.MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language access to personal finance data, including consolidated balances, monthly overviews, transaction search, credit card invoices, recurring bills, budgets, category/tag reports, cash flow forecasts, and Open Finance status, with optional read/write tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to turn household paperwork into answers about upcoming deadlines, warranties, and plain-language explanations, and to draft related messages such as payment extension requests.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to read receipt and invoice files, organize them with standardized filenames, append entries to an Excel-friendly CSV ledger, and search ledger records locally without network access or deletion.MIT
TDQS
Scored across 20 tools
Most tools target clearly distinct purposes: item CRUD (add/update/delete/restore), retrieval (list/get/search/get_stats/due_soon), and a separate money sub-domain (add_spending, import_bank_file, categorise, spending_summary, money_ahead, rainy_day_plan, update_pot). The main soft spot is the retrieval cluster in the item domain, where list_items (sorted by due date), due_soon (overdue/reminder windows), and search_items can all return overlapping item sets. Descriptions do disambiguate ('main what's coming up tool', 'use before add_item to avoid duplicates'), so real confusion is limited.
The dominant pattern is snake_case verb_noun: delete_item, restore_item, list_items, get_item, search_items, add_item, update_item, export_calendar, import_bank_file, add_spending, update_pot, open_home_screen. Deviations are feature/entity-style names (due_soon, spending_summary, money_ahead, rainy_day_plan, bank_holidays, get_stats) but they are all snake_case and semantically transparent, not chaotic.
Twenty tools is on the heavy side for a single server and reflects that it bundles two fairly large domains (tracked items plus personal spending/planning) with some presentation extras (export_calendar, bank_holidays, open_home_screen). Each tool plausibly earns its place, but the surface is broad enough that an agent must sort through many similarly-scoped read tools. Splitting items vs. money would likely be cleaner.
Item lifecycle is well covered: create, read (get/list/search/stats/due), update, mark handled with roll-forward, delete, restore, and calendar export. Spending has add/import/categorise/summarise and pot tracking, so the main gap is the absence of edit or delete for individual spending records (a mistyped or mis-imported transaction can only be re-categorised, not removed). Minor gaps otherwise, with no major dead ends for the core workflows.