memtrace 0.1.50 → 0.2.0

package/README.md

@@ -235,7 +235,7 @@ For manual setup:
 ```bash
 claude plugin marketplace add syncable-dev/memtrace
 claude plugin install memtrace-skills@memtrace --scope user
-claude mcp add memtrace -- memtrace mcp -e MEMGRAPH_URL=bolt://localhost:7687
+claude mcp add memtrace -- memtrace mcp -e MEMTRACE_ARCADEDB_BOLT_URL=bolt://localhost:7687
 ```
 
 ### Other Editors (Cursor, Windsurf, VS Code, Cline)
@@ -248,7 +248,7 @@ After `npm install -g memtrace`, add the MCP server to your editor's config:
     "memtrace": {
       "command": "memtrace",
       "args": ["mcp"],
-      "env": { "MEMGRAPH_URL": "bolt://localhost:7687" }
+      "env": { "MEMTRACE_ARCADEDB_BOLT_URL": "bolt://localhost:7687" }
     }
   }
 }

package/installer/dist/transformers/claude.js

@@ -17,7 +17,7 @@ async function tryMcpAddJson(memtraceBinary) {
     const config = JSON.stringify({
         command: memtraceBinary,
         args: ['mcp'],
-        env: { MEMGRAPH_URL: 'bolt://localhost:7687' },
+        env: { MEMTRACE_ARCADEDB_BOLT_URL: 'bolt://localhost:7687' },
     });
     // Shell-quote the JSON. Use single quotes; escape any embedded single quote.
     const escaped = config.replace(/'/g, `'\\''`);
@@ -151,7 +151,7 @@ export function registerMcpInSettingsAt(settingsPath, memtraceBinary) {
     settings.mcpServers['memtrace'] = {
         command: memtraceBinary,
         args: ['mcp'],
-        env: { MEMGRAPH_URL: 'bolt://localhost:7687' },
+        env: { MEMTRACE_ARCADEDB_BOLT_URL: 'bolt://localhost:7687' },
     };
     writeJsonAtomic(settingsPath, settings);
     return { registered: true };
@@ -325,7 +325,7 @@ function writeClaudeLocalMcp(mcpPath, binary) {
     cfg.mcpServers['memtrace'] = {
         command: binary,
         args: ['mcp'],
-        env: { MEMGRAPH_URL: 'bolt://localhost:7687' },
+        env: { MEMTRACE_ARCADEDB_BOLT_URL: 'bolt://localhost:7687' },
     };
     writeJsonAtomic(mcpPath, cfg);
     return true;

package/installer/dist/transformers/cursor.js

@@ -30,7 +30,7 @@ export function registerCursorMcpAt(mcpFile, binary) {
     cfg.mcpServers['memtrace'] = {
         command: binary,
         args: ['mcp'],
-        env: { MEMGRAPH_URL: 'bolt://localhost:7687' },
+        env: { MEMTRACE_ARCADEDB_BOLT_URL: 'bolt://localhost:7687' },
     };
     writeJsonAtomic(mcpFile, cfg);
     return { registered: true };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memtrace",
-  "version": "0.1.50",
+  "version": "0.2.0",
   "description": "Code intelligence graph — MCP server + AI agent skills + visualization UI",
   "keywords": [
     "mcp",
@@ -36,9 +36,9 @@
     "fs-extra": "^11.0.0"
   },
   "optionalDependencies": {
-    "@memtrace/darwin-arm64": "0.1.50",
-    "@memtrace/linux-x64": "0.1.50",
-    "@memtrace/win32-x64": "0.1.50"
+    "@memtrace/darwin-arm64": "0.2.0",
+    "@memtrace/linux-x64": "0.2.0",
+    "@memtrace/win32-x64": "0.2.0"
   },
   "engines": {
     "node": ">=18"

package/skills/commands/memtrace-graph.md

@@ -20,7 +20,7 @@ Graph algorithms that reveal the structural architecture of a codebase — commu
 | Tool | Purpose |
 |------|---------|
 | `find_bridge_symbols` | Architectural chokepoints — symbols that connect otherwise-separate modules |
-| `find_central_symbols` | Most important symbols by PageRank or degree centrality |
+| `find_central_symbols` | Most important symbols (PageRank via ArcadeDB `algo.pagerank`) |
 | `list_communities` | Louvain-detected logical modules/services |
 | `list_processes` | Execution flows: HTTP handlers, background jobs, CLI commands, event handlers |
 | `get_process_flow` | Trace a single process step-by-step |
@@ -67,7 +67,8 @@ Use `find_central_symbols` to identify the most important symbols:
 - `repo_id` — string, required.
 - `branch` — string, optional. Defaults to `"main"`.
 - `limit` — **integer**, optional. How many to return. Default `20`, capped at `100`.
-- `algorithm` — string, optional. `"pagerank"` (default, via MAGE — falls back to degree if unavailable) or `"degree"` (simple in-degree count, no MAGE required).
+
+Returns the top-N symbols ranked by **PageRank** (ArcadeDB's native `algo.pagerank` procedure). Filters the global run to Function/Method/Class/Interface/Struct in the requested repo + branch. Falls back to in-degree centrality only if the native procedure isn't registered on the connected ArcadeDB build.
 
 ### 3. Find architectural chokepoints
 
@@ -81,6 +82,8 @@ Use `find_bridge_symbols` to find symbols that, if removed, would disconnect par
 - `branch` — string, optional. Defaults to `"main"`.
 - `limit` — **integer**, optional. Default `15`, capped at `50`.
 
+Ranks symbols by **betweenness centrality** (ArcadeDB's native `algo.betweenness` with `normalized: true`) — how many shortest paths between other symbols pass through each one. Falls back to an in-degree × out-degree heuristic only if the native procedure isn't registered.
+
 ### 4. Trace execution flows
 
 Use `list_processes` to see all entry points (HTTP handlers, background jobs, CLI commands, event handlers).
@@ -111,7 +114,7 @@ Use `execute_cypher` for advanced graph queries not covered by built-in tools. T
 | Question | Tool |
 |----------|------|
 | "What are the main modules?" | `list_communities` |
-| "What are the most important functions?" | `find_central_symbols` with method=pagerank |
+| "What are the most important functions?" | `find_central_symbols` (PageRank, native) |
 | "Where are the bottlenecks?" | `find_bridge_symbols` |
 | "How does a request flow through the system?" | `list_processes` → `get_process_flow` |
 | "What's the entry point for feature X?" | `list_processes`, then filter by name |

package/skills/workflows/memtrace-codebase-exploration.md

@@ -50,7 +50,7 @@ Each community represents a cohesive module — these are the "areas" of the cod
 
 ### 4. Find the most important symbols
 
-Call `find_central_symbols` with `method: "pagerank"` and `limit: 15`.
+Call `find_central_symbols` with `limit: 15`. It ranks symbols by PageRank (ArcadeDB's native `algo.pagerank`) — no extra parameter needed.
 
 These are the symbols that the rest of the codebase depends on most heavily. They form the "skeleton" of the architecture.