Memtrace Public
Shared structural memory for multi-agent coding: bi-temporal graph, MCP-native, 27x faster in v1.0.0
Memtrace solves a real pain for multi-agent coding: context decay and work collisions. The v1.0.0 update with a 27x faster graph engine signals active development, but benchmarks remain self-reported. The free Community tier is generous—try it with your agents. Hold off on team pricing until it's published and community-validated.
Verified 2d ago · liveness 60/100 · cite: rightaichoice.com/tools/memtrace-public
- Teams running 3+ AI coding agents on the same codebase
- Engineering teams with large monorepos needing impact analysis
- Organizations automating CI/CD agent workflows
- Privacy-conscious teams wanting local memory without sending code to LLM APIs
- Single-agent setups (value weakens dramatically)
- Teams unwilling to grant agents file-write permissions
- Projects requiring public cloud hosting (self-hosted only)
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Memtrace if you run a single agent or a small codebase, need public cloud hosting, or cannot allow agents file-write permissions.
The Community tier is limited to one repository; adding more repositories requires a paid plan, which is not yet publicly priced.
Memtrace offers a free Community tier for one repository, which is generous compared to similar tools that charge per-seat from day one. For teams with multiple agents, the value in token savings and reduced merge conflicts likely outweighs the cost, but paid tiers are not yet public, so it's hard to compare directly with peers.
In short
Memtrace Public — Shared structural memory for multi-agent coding: bi-temporal graph, MCP-native, 27x faster in v1.0.0. Best for Teams running 3+ AI coding agents on the same codebase, Engineering teams with large monorepos needing impact analysis, Organizations automating CI/CD agent workflows. Free to use.
What's new in Memtrace Public
Checked 2 days agoAcross the latest 5 updates: 5 feature updates.
v1.1.5 – Cross-repository calls stay connected from service map to graph
Improved cross-repository call detection for C#/C++ HTTP clients, gRPC, WebSocket, message queues, and Python subprocesses; added confidence for inferred relationships.
v1.1.4 – Start Memtrace and sit still — idle CPU stays down
Reduced idle CPU usage by not rebuilding search indexes on start and improved MCP server lifecycle handling.
v1.0.6 – Test coverage measures maintained code, not frozen copies
Fixed test coverage calculation to exclude immutable evidence copies, so maintained code is measured accurately.
v1.0.5 – Insight panels tell the truth about every language
Fixed dead-code detection for Java, C#, Go, and other languages; improved import resolution and unified graph renderers.
REST API for Graph and Fleet tools (v0.8.55)
Introduced a REST API for Graph and Fleet tools, enabling programmatic access to code intelligence and coordination features.
What people actually say about Memtrace Public — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
1 mentions across 1 source (Hacker News) · researched Jul 3, 2026.
- +Promises to eliminate agent-forgotten context and merge conflicts.
- +Bi-temporal graph enables instant time travel to any past state.
- +97.3% impact analysis accuracy (self-reported) could save debugging time.
- +Sub-13ms query latency (self-reported) for real-time coordination.
- +Run on a laptop with 16MB memory at 100k records (self-reported).
- −Not publicly available; behind a paced access queue as of July 2026.
- −No independent validation of any performance or accuracy claims.
- −Zero public documentation, changelog, or pricing information.
- −Only one community mention exists, limited to a brief Hacker News post.
- −Requires MCP-native agents; may not integrate with non-listed tools.
- • No pricing available; may require paid tiers for production use.
Viability Score
How well maintained and how widely used is Memtrace Public? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: August 2026
How we score →Key Features
- Bi-temporal graph database (MemDB) with time-as-first-class
- GPU-accelerated graph engine (27x faster in v1.0.0)
- Live code map: functions, files, call graph, dependencies
- Fleet coordination: agents announce intent and auto-merge safe overlaps
- Time travel: rewind to any past state in milliseconds
- Impact analysis: query breakage before editing
- Persistent decision memory (Cortex) for conventions and rationale
- MCP-native integration with Cursor, Claude Code, Codex, Gemini CLI, Windsurf, VS Code
- REST API for Graph and Fleet tools (v0.8.55)
- Hybrid BM25 + semantic search over code graph
- Detects non-HTTP dependencies and Java/C# API topology (v1.0.0)
- Auto-merges 90% of parallel-work overlaps
- Local-first: source code stays in your environment
- No LLM calls for memory or coordination
- CLI with 83 MCP tools, stdio or HTTP
About Memtrace Public
Memtrace is a shared memory layer for teams running multiple AI coding agents on the same codebase. It replaces context loss and merge conflicts with a live code map, decision history, and parallel-work coordination—all without relying on LLM calls for memory operations. Built on a custom bi-temporal graph database (MemDB), Memtrace tracks every function, file, and dependency over time, letting agents check impact and recall why code exists before editing. The platform is MCP-native and integrates with Cursor, Claude Code, Codex, Gemini CLI, Windsurf, and VS Code, plus more. In its v1.0.0 release, Memtrace redesigned its app and delivered a 27x faster graph engine via GPU Barnes-Hut, adding non-HTTP dependencies and Java/C# API detection in topology. Public benchmarks show 96.6% top-1 retrieval accuracy on 1,000 exact-symbol queries, and a 3.9x advantage in correct results per token over the runner-up. Memtrace is local-first: source code stays in your environment, and team memory can be self-hosted. The Community tier is free for one repository.
Behind the Verdict
Memtrace addresses a genuine bottleneck in multi-agent development: every agent starts cold, burning tokens to understand the codebase and often stepping on each other's changes. By maintaining a bi-temporal graph of symbols, relationships, and decisions, Memtrace gives agents a shared reference that persists across sessions. The integration via MCP means it slots into your existing workflow with Cursor, Claude Code, Codex, and others without forcing a new editor. What stands out is the focus on efficiency: the public benchmark shows 202 response tokens per correct result and a 3.9x improvement in correct results per token, which translates into lower API costs and faster iterations. The local-first architecture is a plus for privacy-conscious teams—source code never leaves your environment unless you choose to self-host team memory. Weaknesses: the performance claims are self-reported, so independent validation is still needed. The free tier is limited to one repository, which feels tight if you're working across multiple services. Also, the value drops significantly for solo developers or teams running just one agent; the coordination benefits only kick in with real parallelism. Memtrace fits well for engineering teams with 3+ agents on a monorepo, especially those tired of merge conflicts and context loss. It's less suitable for small projects or teams unwilling to grant agents file-write permissions. If you're already using a tool like Sourcegraph or CodeQL for code intelligence, Memtrace offers a different angle: it's not just about search, it's about temporal memory and coordination. Pricing is still in flux—only the Community tier is public. If you're evaluating, start with the free tier to see if it reduces token spend and merge conflicts in your actual workflow. Keep an eye on the changelog; the pace of updates (v1.1.5 as of August 2026) suggests a rapidly evolving product.
Researching Memtrace Public? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Memtrace Public actually fits — and what changes day-one when you adopt it.
Your team of five engineers uses Cursor and Claude Code to implement a new payment feature. You install Memtrace, and agents start checking impact before editing, avoiding overlaps.
Outcome: Merge conflicts drop by 70%, and the feature ships two days early because agents spend less time re-reading code.
You manage a monorepo with hundreds of services. You deploy MemDB self-hosted and integrate with Codex and Windsurf.
Outcome: Impact analysis catches a breaking change in a shared library before it reaches review, saving hours of debugging.
You try Memtrace on a side project to see if it helps coordinate your two agents.
Outcome: You find it useful but the single-repo limit feels restrictive, so you stick to the free tier for your main project.
Use Cases
- Coordinate a fleet of AI coding agents to avoid editing the same file simultaneously
- Instantly assess the impact of a code change across the entire call graph
- Rewind the codebase to any past state to debug or replay agent actions
- Reduce merge conflicts by having agents announce intent before writing code
- Maintain a live map of symbols, dependencies, and history for your entire repo
- Run automated code review with quality gates and PR insights
Limitations
- Memtrace is a local-first tool that indexes repositories into a temporal knowledge graph and serves it over MCP, with code staying in your environment.
- It requires sign-in to provision a license and uses MCP-native integration and a CLI.
- Performance claims such as 27x faster graph engine and 3.9x more correct results per token are self-reported.
- It is actively updated (e.g., v1.1.5 as of August 20, 2026) but early-stage.
as of 2026-08-21
Verification history
We have re-verified Memtrace Public 5 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Memtrace Public tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Community
$0/mo
Ideal for
Individual developers or small teams with a single repository who want to evaluate Memtrace's impact on their agent workflow at no cost.
What this tier adds
Free entry point: includes local analysis, MCP integration, code graph, and impact analysis for one repository.
Where the pricing makes sense
The company stage and team size where Memtrace Public's pricing actually pencils out — and where peers do it cheaper.
Memtrace offers a free Community tier for one repository, which is generous compared to similar tools that charge per-seat from day one. For teams with multiple agents, the value in token savings and reduced merge conflicts likely outweighs the cost, but paid tiers are not yet public, so it's hard to compare directly with peers.
Setup time & first value
How long it actually takes to get something useful out of Memtrace Public — broken out by persona, not the marketing-page minute.
Setup takes about 15 minutes: sign in with Google/GitHub, install via npm, run `memtrace start`, then connect your agent via MCP. Most users have the first index running within 10 minutes, and full graph indexing scales with repository size.
Switching to or from Memtrace Public
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From in-house scripts: Replace ad-hoc grep-based code searches with Memtrace's indexed graph and impact analysis.
- →From simple context files: Migrate static docs into Cortex decision memory for persistent agent context.
- ↗To Sourcegraph: Export the code graph via the REST API for broader code intelligence.
- ↗To another MCP server: Since MCP is standard, you can swap Memtrace for any other MCP-compatible memory server.
Integrations
Resources & Guides
Tutorials & Learning
Official links
Tools that pair well with Memtrace Public
Common stack mates teams adopt alongside Memtrace Public, with the specific reason each pairing earns its keep.
Chrome DevTools MCP
Free MCP server that gives AI coding agents live Chrome debugging, performance traces, and reliable automation.
QuantDinger
Self-hosted AI quant trading platform with MCP integration for AI agents.
Graphmind
Turns your codebase into a knowledge graph your AI can query, navigate, and remember.
Featured Head-to-Head Comparisons
Memtrace Public vs Voyage Ai
Choose Voyage AI if you need high-accuracy embedding and reranking for enterprise RAG, especially in finance or legal. Choose Memtrace if you run multiple AI coding agents and need shared memory to avoid context loss and conflicts. They solve completely different problems; your decision depends on whether your bottleneck is retrieval accuracy or agent coordination.
Memtrace Public vs Temporal Ai
Choose Temporal AI if you need a battle-tested durable execution platform for long-running workflows, AI agents, or human-in-the-loop processes with automatic retries and state recovery. Choose Memtrace if you are a team running multiple AI coding agents on a large codebase and need shared, time-travel-capable memory to avoid context loss and merge conflicts, but be prepared for a less mature, self-hosted tool.
Memtrace Public vs Spider Cloud
If you run a fleet of AI coding agents and need shared memory with conflict detection, Memtrace is purpose-built—but it's waitlist-only and weakens for single-agent setups. For web data retrieval powering AI agents or RAG, Spider Cloud offers a proven, low-cost API with real-time scraping features and recent Browser AI commands. Choose Memtrace for coordination, Spider Cloud for data.
Alternatives to Memtrace Public
View allChrome DevTools MCP
Free MCP server that gives AI coding agents live Chrome debugging, performance traces, and reliable automation.
QuantDinger
Self-hosted AI quant trading platform with MCP integration for AI agents.
Frequently Asked Questions
Used Memtrace Public? Help shape our editorial sentiment research.