@systemdox/mcp-server 0.1.49 → 0.1.50

package/README.md

@@ -122,7 +122,8 @@ npx @systemdox/mcp-server setup
 
 Read: `get_checks`, `get_specs`, `get_docs`, `get_tech_stack`,
 `get_planning_context`, `get_plan_board`, `get_change`, `get_context`,
-`get_project_rules`, `get_prompt_templates`. Write: `create_check`,
+`get_project_rules`, `get_prompt_templates`, `get_team_setup`, `get_document_links`,
+`trace_document_path`, `get_graph_stats`. Write: `create_check`,
 `update_spec`, `report_decision`, `create_project_rule`,
 `create_prompt_template`. Write tools require an API key with `editor`+ role.
 
@@ -141,6 +142,34 @@ npx -y @systemdox/mcp-server install-skill <name> [--version n] [--target dir] [
 Exit codes: `0` installed, `1` usage / no key / API error, `2` refused because
 files there were edited.
 
+### What every session is told (ADR-223)
+
+Installing this server is enough for a computer to know what its team uses. When
+a session connects, the server answers with `instructions`, which Claude Code puts
+in the session's system prompt with no tool call:
+
+- the workspace, and to call `get_context` before writing code;
+- each skill your team put in the team setup, with when to use it;
+- what this computer lacks. A missing or older skill is installed with
+  `install_skill`, which writes files and runs nothing. A file you edited is never
+  replaced, and a folder that did not come from SystemDox is left alone.
+
+Hooks, MCP servers, team instructions and memory run or load by themselves, so they
+still wait for you: `setup`, in your own terminal, below. An agent never answers its
+prompts. So does a team skill that is not plain (anything in its frontmatter beyond a
+name and a description, files outside its own folders, or a `!`-command) or that sits
+outside the default space: a session is told its name and not to install it. A skill may
+not hold `.claude-plugin/`, which would make it a plugin. The hosted server cannot see
+your disk, so it says how to check.
+
+**`get_team_setup`** (both servers, read-only) answers the same question in full:
+every skill, hook command and MCP server, and on your own computer what is missing
+and what to do. Use it with a client that does not surface `instructions`.
+
+If this computer has no key, or SystemDox refuses it, the server still connects and
+tells the session what to do. See the words a session gets in the console, under
+**Docs › Team setup › What every session is told**.
+
 ### Team setup (ADR-217)
 
 Your workspace's Claude Code setup (hooks, MCP servers, agents, commands, the