LSP resolution: existing repo first for sysmledgraph-mcp

- Resolve order: SYSMLLSP_SERVER_PATH, then cwd/repo, then package node_modules
- docs/MCP-AND-KUZU.md: document resolution order
- chore: release v0.4.0

Made-with: Cursor

Author: chouswei

docs/MCP-AND-KUZU.md

@@ -33,7 +33,7 @@ That was **path resolution**: the sysmledgraph CLI (or MCP) was only looking in
 
 **Fixes:**
 
-- Resolver now also checks **repo root** (and parent directories) for `node_modules/sysml-v2-lsp/dist/server/server.js`, so when sysmledgraph runs from a subfolder (e.g. `tools/sysmledgraph`), it can find the LSP at the repo root.  
+- Resolver looks for the LSP in this order: **SYSMLLSP_SERVER_PATH** (if set), then the **existing repo** (walk up from the current working directory), then sysmledgraph’s own `node_modules`. So when the MCP runs with cwd = workspace root, the repo’s sysml-v2-lsp is used first.  
 - You can always set **SYSMLLSP_SERVER_PATH** to the absolute path of your built `dist/server/server.js` if you want to point at a specific LSP install.
 
 The sysml-v2 MCP runs from repo root and uses `mcpServer.js`; it doesn’t depend on this resolver and doesn’t block it.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "sysmledgraph",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Path-only SysML indexer: knowledge graph (Kuzu), MCP server (query, context, impact, rename, cypher), CLI (analyze, list, clean)",
   "type": "module",
   "main": "dist/src/index.js",

release-notes-v0.4.0.md

@@ -0,0 +1,4 @@
+## Changes
+
+- **LSP resolution: existing repo first** — sysmledgraph-mcp now looks for sysml-v2-lsp in this order: `SYSMLLSP_SERVER_PATH` (if set), then the **current workspace/repo** (walk up from cwd), then sysmledgraph’s own `node_modules`. When the MCP runs with cwd = workspace root, the repo’s LSP is used first.
+- **Docs** — MCP-AND-KUZU.md updated to describe the resolution order.

src/parser/lsp-client.ts

@@ -1,7 +1,7 @@
 /**
  * sysml-v2-lsp integration: stdio LSP client.
  * Spawns the LSP server (dist/server/server.js). Uses LSP message framing (Content-Length).
- * Server path: SYSMLLSP_SERVER_PATH, or local node_modules, or walk up from cwd (e.g. repo root).
+ * Server path: SYSMLLSP_SERVER_PATH, or existing repo (walk up from cwd) first, then sysmledgraph's node_modules.
  */
 
 import { spawn } from 'child_process';
@@ -39,11 +39,11 @@ async function resolveServerPath(): Promise<string | null> {
   if (process.env.SYSMLLSP_SERVER_PATH) {
     return process.env.SYSMLLSP_SERVER_PATH;
   }
+  const fromRepo = findLspInNodeModules(process.cwd());
+  if (fromRepo) return fromRepo;
   const packageRoot = join(__dirname, '..', '..', '..');
   const local = join(packageRoot, 'node_modules', LSP_REL_PATH);
   if (existsSync(local)) return local;
-  const fromCwd = findLspInNodeModules(process.cwd());
-  if (fromCwd) return fromCwd;
   return null;
 }