Life Compass
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIFE_COMPASS_DIR | No | Directory where your plan is stored. Defaults to ~/.life-compass (plan is kept at ~/.life-compass/plan.json). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Life Compass is an evidence-based reflection, goal and habit coach. Start every session with get_status: it says which phase the person is in, the next question, and any reviews or lapses that are due. Follow the method (get_method, or the life_compass prompt) one question at a time, save answers with the tools as you go, and never assign goals: offer options and let the person choose. Plans are stored only on this computer, at /root/.life-compass/plan.json.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Call first in every session. Returns the current phase, the next reflection question, and anything due today: weekly review, monthly habit-strength checks, quarterly review, upcoming decisions and lapsed habits. |
| get_methodA | Returns the Life Compass method: rules and, for each phase, the questions or steps in order with the reason for each. Pass a phase to get just that part. |
| values_card_sortA | For people unsure of their values. Returns the value cards and the steps of the sort (after the Personal Values Card Sort, Miller et al. 2001). Walk them through it, then call save_values. |
| save_reflectionA | Save answers to Phase 1 questions as the person gives them. Only include the fields answered; others are kept. Use the person's own words, lightly tidied. |
| save_baselineA | Save 1–10 ratings for each life area. Defaults: health, career, money, relationships, home, hobbies and fun, meaning and growth; people may rename, add or remove areas. Also used at quarterly reviews. |
| save_capacityB | Save realistic hours per week for the plan and current energy from 1 to 10. This caps how many habits can be active at once. |
| save_valuesA | Save the person's 3 to 5 guiding values, each with what it means to them in their own words. Replaces the current list. |
| save_goalB | Create or update one goal (max 3 active). Only after the person chose it. Include the value it serves, a specific statement (what, how much, by when), an identity statement and the WOOP answers. |
| save_milestonesA | Set a goal's milestones: 4 to 8 concrete, tickable actions spread across quarters 1–4, most in the first two. Replaces the list; ticks are kept for milestones with the same text. |
| save_habitA | Create or update a tiny habit for a goal: a recipe ("After I [anchor], I will [tiny]"), its rhythm, the COM-B barrier and fix, if-then plans for obstacles and one environment change. Also use it to shrink, pause, graduate or drop a habit (status). Warns when active habits exceed what capacity allows. |
| save_plan_extrasB | Save dated decision points (question + what to do if the answer is no) and the one-sentence low-energy rule for a bad fortnight. |
| log_habitC | Record that a habit happened (the tiny version counts). Returns the weekly streak so you can celebrate in one warm line. Never shame a gap. |
| tick_milestoneC | Mark a milestone done (or undone). |
| add_winB | Note something the person did and what changed because of it. Wins feed reviews, confidence and, for career goals, promotion cases. |
| weekly_reviewA | 5-minute weekly check-in: energy 1–10, a line on what helped or got in the way, and optionally one good thing this week and why it happened. Returns habits logged this week and a low-energy flag. |
| monthly_checkA | Record the 4 SRBAI ratings (1–5) for one habit: "I do it automatically", "without having to consciously remember", "without thinking", "before I realise I'm doing it". An average of 4 or more means it can graduate. |
| quarterly_reviewC | 30-minute reset: new life-area ratings, which goals stay, and an optional note (e.g. a gratitude letter written). Returns the change in each area since the last baseline. |
| record_decisionC | Close a dated decision point with what was decided. |
| get_planB | Returns the full plan JSON (values, goals, milestones, habits, decisions, log, wins and reviews). |
| export_remindersA | Writes a calendar file (.ics) with the weekly review, the monthly habit-strength check and the quarterly review, so reminders work without any server. Returns the file path to import into a calendar app. |
| open_dashboardA | Starts the visual Life Compass dashboard on this computer (rings, mountain, habits, goals, wins) and returns a private link to open in a browser. It reads the same local plan file and stays up while this app is open. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| life_compass | Coach me through the Life Compass: reflect, choose goals, plan tiny habits, and review. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| method | |
| plan |
TDQS
Scored across 21 tools
Most tools are clearly distinct: get_status/get_method/get_plan differ by what they return, and log_habit (record one occurrence) vs save_habit (configure/shrink/pause) is well separated by their descriptions. Minor overlap remains between save_baseline and quarterly_review (both record life-area ratings) and between save_milestones and tick_milestone, but descriptions give clear guidance on which to use when.
The dominant pattern is verb_noun (get_status, save_goal, log_habit, tick_milestone, add_win, open_dashboard, export_reminders, record_decision), used consistently across the set. The review tools break the pattern as bare noun names (weekly_review, monthly_check, quarterly_review), and values_card_sort is noun-only, which are minor deviations but still readable.
At 21 tools the surface is on the heavier side, but each maps to a concrete step of a multi-phase method (values, baseline, capacity, goals, milestones, habits, reviews, wins, dashboard, export). Nothing looks redundant, though the eight save_* tools reflect notable granularity that a heavier server might consolidate.
Coverage is broad: reading plan/status, all four planning phases, goal and habit lifecycle (including pause/graduate/drop via save_habit status), reviews, and export. The main gap is explicit goal deletion/completion and win removal, forcing agents to improvise rather than a dedicated operation.