Life Admin MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIFE_ADMIN_TODAY | No | Pretends it's another day (format YYYY-MM-DD) for tests and demos. | |
| LIFE_ADMIN_REGION | No | Set to Scotland or Northern Ireland for local bank holidays. Defaults to England and Wales. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Local-first life admin: renewals, bills, subscriptions, warranties, policies, vehicles and documents, each stored as a markdown file on the user's own machine. Use due_soon to see what needs attention, add_item to track something new (search_items first to avoid duplicates), and mark_handled once the user has dealt with a renewal or payment. Store only the last four digits of any account or card number. Never invent dates or prices; ask the user. Nothing here sends reminders by itself: export_calendar puts due dates and reminders into the user's own calendar app, so never promise a reminder without it.
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 |
|---|---|
| get_statsA | Where the life-admin folder lives and what it holds: item counts by type, how many are overdue and how many are due in the next 30 days. Call once at the start of a conversation to orient. |
| list_itemsB | List tracked items, optionally filtered by type, sorted by due date (undated items last). |
| get_itemA | Full details of one item by title: provider, cost, due date with days left and when reminders start, reference, and its notes and history. |
| search_itemsA | Find items whose title, provider, tags or notes contain any of the words in the query, best matches first. Use before add_item to avoid duplicates, and for questions like 'where's the boiler warranty?'. |
| due_soonA | What needs attention: overdue items, items due within the next |
| add_itemA | Start tracking something: a bill, renewal, subscription, warranty, policy, vehicle or document. Use only facts the user gave you; leave out a due date or cost rather than guessing. Refuses an exact duplicate title (use update_item instead) and anything that looks like a full card number. |
| update_itemA | Change fields on an existing item; anything you leave out stays as it is. |
| mark_handledA | Record that the user has dealt with an item (renewed, paid, switched, replaced). Logs it in the item's history and moves the due date on: repeating items roll forward by their period (keeping month-end dates right), |
| export_calendarA | Write every item that has a due date to an .ics file the user can import into Apple Calendar, Google Calendar or Outlook. Each item becomes an all-day event with a 9am reminder when its reminder window opens and another on the day; repeating items repeat in the calendar. After changes, export again and import into the same calendar to update the events. Provider and cost are included unless |
| delete_itemA | Stop tracking an item. It moves to the trash and can be brought back with restore_item. Confirm with the user first. |
| restore_itemB | Bring back the most recently deleted item with this title. |
| import_bank_fileA | Read a bank statement exported as CSV (every UK bank app can export one) and add its transactions to the person's spending records, sorted into categories. Always run first with confirm false to show a preview, then again with confirm true once the person agrees. Already-imported lines are skipped, so overlapping statements are safe. The file stays on this computer. |
| add_spendingA | Record one payment or refund the person tells you about ("I spent £42 on a meal out"). The category is worked out from the description unless given. Amounts are always positive; set money_in for refunds or money received. Categories: bills (Bills & energy), groceries (Groceries), shopping (Shopping), going-out (Eating & going out), transport (Transport), tax (Tax), subscriptions (Subscriptions), savings (Savings), income (Income), transfers (Transfers), other (Other). |
| categoriseA | Put every transaction whose description contains these words (whole words, any case) into a category, and by default remember it so future imports are sorted the same way. Use after an import lists unsorted shops. Categories: bills (Bills & energy), groceries (Groceries), shopping (Shopping), going-out (Eating & going out), transport (Transport), tax (Tax), subscriptions (Subscriptions), savings (Savings), income (Income), transfers (Transfers), other (Other). |
| spending_summaryA | What was spent this week or month by category, compared with what's usual for the person (the average of up to four earlier periods), plus money in, money saved and the biggest shops. Weeks run Monday to Sunday. offset 1 means last week/month. |
| money_aheadA | Payments due between today and the next payday (from income items, moved to the working day before if payday falls on a weekend or bank holiday), with their total. Given the person's current balance, says roughly what is left until payday. Never guess the balance: ask for it. |
| rainy_day_planA | Work out how much the person could put aside, from their own income items and spending records: big yearly bills smoothed into monthly set-asides, then Gentle, Steady and Stretch options, each with a risk check against their tightest recent month and time to a £1,000 pot and to three months of essentials. Flags varying income, rising spending, big bills due soon and signs of borrowing. Arithmetic only: never recommend financial products, accounts or investments. |
| update_potA | Record what is in the rainy-day pot: set the amount saved, add to it (or take from it with a negative amount), or set a goal. Only use figures the person gave you. |
| bank_holidaysA | Upcoming UK bank holidays (official gov.uk list, bundled) for England and Wales, Scotland or Northern Ireland. Useful because pay due on a bank holiday or weekend usually arrives the working day before, and payments due then are usually taken the next working day. |
| open_home_screenA | Open the person's home screen in their web browser: what's coming up, the next payday and the bills before it, this week's spending and the rainy-day pot, in large, calm print with a Print button. It runs only on this computer, and stays available while this assistant session is open. |
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 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.