@systemdox/mcp-server 0.1.18 → 0.1.19

package/README.md

@@ -1,8 +1,38 @@
 # @systemdox/mcp-server
 
-MCP server that exposes your SystemDox context — checks, specs, docs, tech
-stack, project rules, and prompt templates — to AI coding tools (Claude Code,
-Cursor, and any MCP-compatible client).
+> Your architecture, in your agents' context window.
+
+[SystemDox](https://www.systemdox.com) is the document plane for AI-assisted
+engineering: your standards — specs, architecture decision records, checks,
+project rules, docs — versioned in git and delivered into your coding agents'
+context at write time. This MCP server is how Claude Code, Cursor, and any
+MCP-compatible tool read that context — and write decisions back.
+
+**Why teams use it**
+
+- **Write-time context** — `get_context` ranks the checks, specs, and docs
+  relevant to the task at hand and fetches their bodies within a token budget,
+  so the agent starts from your architecture instead of guessing it.
+- **Both directions** — agents call `report_decision` and `update_spec` as they
+  work, so decision records exist as a by-product of shipping, not as
+  archaeology afterwards.
+- **One source for every agent** — no per-developer rules-file forks; every
+  session in every repository starts from the same governed, versioned context.
+- **Scoped by key** — the API key is the boundary: a department-scoped key sees
+  only its own space's checks, specs, and docs.
+
+**Get started in about a minute**
+
+1. [Create a SystemDox workspace](https://app.systemdox.com/signup) — the free
+   tier covers one repository, permanently.
+2. Connect a GitHub repository and generate an API key (workspace settings).
+3. Add the server to your tool — hosted (Option A) or local (Option B) below.
+
+Docs: [MCP setup guide](https://www.systemdox.com/guides/mcp-setup) ·
+[Documentation standard](https://www.systemdox.com/guides/documentation-standard) ·
+[Why write-time context](https://www.systemdox.com/blog/architecture-only-exists-at-write-time)
+
+---
 
 There are two ways to run it. Both authenticate with a SystemDox API key
 (generate one on your SystemDox settings page) and act strictly as the caller —

package/dist/cli.js

@@ -1979,7 +1979,7 @@ var init_server = __esm({
     init_create_project_rule();
     init_get_prompt_templates();
     init_create_prompt_template();
-    SERVER_VERSION = true ? "0.1.18" : "0.0.0-dev";
+    SERVER_VERSION = true ? "0.1.19" : "0.0.0-dev";
   }
 });
 

package/dist/http.js

@@ -1790,7 +1790,7 @@ function registerCreatePromptTemplate(server, apiClient) {
 }
 
 // src/server.ts
-var SERVER_VERSION = true ? "0.1.18" : "0.0.0-dev";
+var SERVER_VERSION = true ? "0.1.19" : "0.0.0-dev";
 function createServer(apiClient) {
   const server = new McpServer({
     name: "systemdox-mcp-server",

package/dist/index.js

@@ -1806,7 +1806,7 @@ function registerCreatePromptTemplate(server2, apiClient2) {
 }
 
 // src/server.ts
-var SERVER_VERSION = true ? "0.1.18" : "0.0.0-dev";
+var SERVER_VERSION = true ? "0.1.19" : "0.0.0-dev";
 function createServer(apiClient2) {
   const server2 = new McpServer({
     name: "systemdox-mcp-server",

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@systemdox/mcp-server",
-  "version": "0.1.18",
+  "version": "0.1.19",
   "type": "module",
-  "description": "MCP server that exposes SystemDox checks, specs, docs, and tech stack to AI coding tools",
+  "description": "Give AI coding agents your architecture context over MCP — checks, specs, ADRs, project rules, and docs from SystemDox, delivered at write time",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "bin": {
@@ -44,11 +44,18 @@
   "keywords": [
     "mcp",
     "model-context-protocol",
+    "mcp-server",
     "systemdox",
     "ai",
     "claude",
+    "claude-code",
+    "cursor",
+    "context",
+    "architecture",
+    "adr",
     "checks",
-    "specs"
+    "specs",
+    "governance"
   ],
   "author": "Emanuele Pugliese",
   "license": "ISC",