selfos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SELFOS_VAULT | No | Path to a different vault to use. By default the MCP server uses the vault at ~/.selfos/vault (or <clone>/vault). | ~/.selfos/vault |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_contextA | Call first. Returns today's date, the user's preferences and identity, active/paused goals with pace and check-in status, habits, upcoming birthdays, and a list of all vault files. |
| list_goalsB | Goals with progress vs pace, days since check-in, whether a check-in is due, and linked habits. |
| list_habitsB | Active habits with this period's count vs required, streak, recent hit rate and last miss reason. |
| read_fileA | Read any vault file by path relative to the vault, e.g. 'people/jane-doe.md'. |
| searchB | Case-insensitive text search across the vault. |
| upcoming_birthdaysC | Birthdays in the next N days. |
| weekly_reviewA | Build this week's review: goals, habits, what's coming up, and the questions worth asking. Walk the user through it: wins first, then questions one at a time, then next week's focus. |
| create_goalA | Create a goal after coaching the user through it. Requires at least one if-then plan. Refuses if over the active-goal cap unless confirm_over_cap is true. |
| log_goal_checkinA | Log a check-in on a goal (by name or title), optionally with the metric value. Returns updated pace. |
| update_goalA | Change a goal: status (pausing needs resume_date), dates, target, cadence; add plans, obstacles or reasons; optionally log a note. Only change status when the user says so. |
| create_habitA | Create a repeatable habit, optionally linked to a goal, with a cue and a minimum version for bad days. |
| log_habitB | Log a habit occurrence as done, or missed with the reason the user gave. |
| add_noteA | Append a fact the user told you to a vault file (one subject per file), e.g. 'people/jane-doe.md', 'profile/preferences.md', 'journal/2026-10-16.md' (auto-created). Pass |
| init_vaultA | Create the vault from the template if it doesn't exist yet. |
| validateA | Check every vault file's frontmatter; reports errors and coaching warnings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| coach | The full self.os coaching protocol (AGENTS.md). |
| set-goal | Coach the user through setting a new goal. |
| check-in | Check in on goals and habits that are due. |
| weekly-review | Run the weekly review. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes across goals, habits, files, search, birthdays, and reviews. There is some overlap between get_context and the dedicated list_goals/list_habits/upcoming_birthdays tools, and between weekly_review and those listing tools, but descriptions provide enough guidance to select correctly.
Names are consistently snake_case and mostly follow a verb_noun pattern such as list_goals, create_goal, log_habit, and add_note. A few outliers like search, validate, weekly_review, and upcoming_birthdays break the pattern but remain readable and predictable.
At 15 tools, the surface is well-scoped for a personal operating system covering goals, habits, notes, vault admin, and reviews. Each tool maps to a concrete workflow and none appear redundant enough to remove.
Goal workflows are reasonably covered with create, update, list, check-in, and review support, but habit lifecycle coverage is notably incomplete: there is no update_habit or delete/archive operation for habits. Vault file operations are also limited to reading, searching, and appending notes, with no general file update capability.