memtrace 0.2.1 → 0.3.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +21 -9
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -25,11 +25,10 @@ Index once. Every agent query after that resolves through graph traversal — ca
25
25
 
26
26
  ```bash
27
27
  npm install -g memtrace # binary + 12 skills + MCP server — one command
28
- memtrace start # launches the graph database
29
- memtrace index . # indexes your codebase in seconds
28
+ memtrace start # launches the graph database and auto-indexes the current project
30
29
  ```
31
30
 
32
- That's it. Claude picks up the skills and MCP tools automatically.
31
+ That's it. Run `memtrace start` from your project root — it spins up the graph database and kicks off indexing automatically. Claude and Cursor (v2.4+) pick up the skills and MCP tools automatically.
33
32
 
34
33
  ---
35
34
 
@@ -89,7 +88,7 @@ Mem0 and Graphiti are strong conversational memory engines designed for tracking
89
88
 
90
89
  **Both** accumulate $10–50+ in API costs for large codebases because every relationship is inferred rather than parsed.
91
90
 
92
- **Memtrace takes a different approach:** it indexes files in ~4 seconds for $0.00 — no LLM calls, no API costs, no rate limits. Native Tree-sitter AST parsers resolve deterministic symbol references (`CALLS`, `IMPLEMENTS`, `IMPORTS`) locally. The tradeoff is that Memtrace is purpose-built for code — it doesn't handle conversational entity memory the way Mem0 and Graphiti do.
91
+ **Memtrace takes a different approach:** it indexes 1,500 files in 1.2–1.8 seconds for $0.00 — no LLM calls, no API costs, no rate limits. Native Tree-sitter AST parsers resolve deterministic symbol references (`CALLS`, `IMPLEMENTS`, `IMPORTS`) locally. The tradeoff is that Memtrace is purpose-built for code — it doesn't handle conversational entity memory the way Mem0 and Graphiti do.
93
92
 
94
93
  </details>
95
94
 
@@ -221,14 +220,14 @@ Uses **Structural Significance Budgeting** to surface the minimum set of changes
221
220
  |:---------------|:---------------:|:-----------:|:--------|
222
221
  | **Claude Code** | ✅ | ✅ | `npm install -g memtrace` — fully automatic |
223
222
  | **Claude Desktop** | ✅ | ✅ | Automatic — shared with Claude Code |
224
- | **Cursor** | ✅ | Coming soon | Add MCP server manually |
223
+ | **Cursor** (v2.4+) | ✅ | | `npm install -g memtrace` — fully automatic |
225
224
  | **Windsurf** | ✅ | Coming soon | Add MCP server manually |
226
225
  | **VS Code (Copilot)** | ✅ | — | Add MCP server manually |
227
226
  | **Cline / Roo Code** | ✅ | — | Add MCP server manually |
228
227
  | **Codex CLI** | ✅ | Coming soon | Add MCP server manually |
229
228
  | **Any MCP client** | ✅ | — | Add MCP server manually |
230
229
 
231
- > **MCP tools** work with any editor or agent that supports the [Model Context Protocol](https://modelcontextprotocol.io). **Skills** are Claude-specific workflow prompts that teach the agent *how* to chain tools — they require Claude Code or Claude Desktop.
230
+ > **MCP tools** work with any editor or agent that supports the [Model Context Protocol](https://modelcontextprotocol.io). **Skills** are workflow prompts that teach the agent *how* to chain tools — Claude Code, Claude Desktop, and Cursor (v2.4+) all load them natively from the same `SKILL.md` format.
232
231
 
233
232
  ## Setup
234
233
 
@@ -244,7 +243,21 @@ claude plugin install memtrace-skills@memtrace --scope user
244
243
  claude mcp add memtrace -- memtrace mcp -e MEMTRACE_ARCADEDB_BOLT_URL=bolt://localhost:7687
245
244
  ```
246
245
 
247
- ### Other Editors (Cursor, Windsurf, VS Code, Cline)
246
+ ### Cursor
247
+
248
+ Cursor **v2.4+** supports Agent Skills natively, and `npm install -g memtrace` handles everything automatically — no separate Cursor plugin is needed because Cursor reads the same `SKILL.md` format as Claude.
249
+
250
+ What the installer writes:
251
+ - **MCP server** → `~/.cursor/mcp.json` (global — works in every project you open)
252
+ - **12 skills + 4 workflows** → `~/.cursor/skills/memtrace-*/SKILL.md`
253
+
254
+ For a **project-local** install (so the skills travel with your repo and teammates get them on clone), run inside the project:
255
+
256
+ ```bash
257
+ memtrace install --only cursor --local
258
+ ```
259
+
260
+ ### Other Editors (Windsurf, VS Code, Cline)
248
261
 
249
262
  After `npm install -g memtrace`, add the MCP server to your editor's config:
250
263
 
@@ -265,7 +278,6 @@ After `npm install -g memtrace`, add the MCP server to your editor's config:
265
278
 
266
279
  | Editor | Config file |
267
280
  |:-------|:------------|
268
- | **Cursor** | `.cursor/mcp.json` in your project root |
269
281
  | **Windsurf** | `~/.codeium/windsurf/mcp_config.json` |
270
282
  | **VS Code (Copilot)** | `.vscode/mcp.json` in your project root |
271
283
  | **Cline** | Cline MCP settings in the extension panel |
@@ -293,7 +305,7 @@ Rust · Go · TypeScript · JavaScript · Python · Java · C · C++ · C# · Sw
293
305
 
294
306
  | Dependency | Purpose |
295
307
  |:-----------|:--------|
296
- | **Memgraph** | Graph database — auto-managed via `memtrace start` |
308
+ | **ArcadeDB** | Graph + document + vector database — auto-managed via `memtrace start` (pulls `arcadedata/arcadedb:latest`) |
297
309
  | **Node.js ≥ 18** | npm installation |
298
310
  | **Git** | Temporal analysis (commit history) |
299
311
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "memtrace",
3
- "version": "0.2.1",
3
+ "version": "0.3.5",
4
4
  "description": "Code intelligence graph — MCP server + AI agent skills + visualization UI",
5
5
  "keywords": [
6
6
  "mcp",
@@ -36,9 +36,9 @@
36
36
  "fs-extra": "^11.0.0"
37
37
  },
38
38
  "optionalDependencies": {
39
- "@memtrace/darwin-arm64": "0.2.1",
40
- "@memtrace/linux-x64": "0.2.1",
41
- "@memtrace/win32-x64": "0.2.1"
39
+ "@memtrace/darwin-arm64": "0.2.3",
40
+ "@memtrace/linux-x64": "0.2.3",
41
+ "@memtrace/win32-x64": "0.2.3"
42
42
  },
43
43
  "engines": {
44
44
  "node": ">=18"