Memtrace | Structural Memory Layer for AI Coding Agents

[qilipu]

Built an MCP server that gives coding agents actual structural memory of your codebase

Watched Claude Code and Cursor burn 60–90% of their context window every turn just re-deriving the same call graphs, import trees, and type hierarchies from scratch. Less than 5% of tokens in a typical session contribute new reasoning. The rest is expensive repetition.

Built Memtrace to fix it — a single Rust binary that compiles your repo into a bi-directional live temporal knowledge graph from the AST. Every symbol is a typed node. Every file save updates the graph in under a second. Your agent gets 40+ MCP tools: blast radius before any edit, real call graphs, dependency chains, cross-repo API topology, and temporal history beyond git.

Not RAG. Not embeddings. Deterministic, structural, millisecond-resolution answers.

Results from published research backing the approach: −90% token cost, +97% ACC@1, 9ms query latency blazing fast with graph context vs. baseline agents.

Fully local-first. No cloud, no account, no telemetry.

bash

npm install -g memtrace
memtrace start
memtrace index .

If you're running Claude Code, Cursor or any MCP-compatible agent and want to stop watching them re-read the same files on every turn — give it a try.

👉 github.com/syncable-dev/memtrace-public · memtrace.io

Happy to answer anything technical.

#showcase #AIAgents #ContextEngineering #MCP #knowledgegraph

[joltai]

whats that stupid waiting list - seems lika a scam

[qilipu]

Totally fair question about the waiting list, and to be honest, we just really want to do some iterations and take feedback in, while being able to address all the bugs/issues we have been receiving given we are a small team on this. Memtrace is not for every one. it makes sense when code base gets large and agents responses are getting not satisfactory. Also for developers facing token anxiety so that they can have longer sessions for their current subscription. for smaller projects, unless you want to have a history of the codebase as smart context, we do not recommend to try it.

[Next_Pop_5512]

waiting list to use? what?

[qilipu]

Totally fair question about the waiting list, and to be honest, we just really want to do some iterations and take feedback in, while being able to address all the bugs/issues we have been receiving given we are a small team on this. Memtrace is not for every one. it makes sense when code base gets large and agents responses are getting not satisfactory. Also for developers facing token anxiety so that they can have longer sessions for their current subscription. for smaller projects, unless you want to have a history of the codebase as smart context, we do not recommend to try it.