Frequently asked questions
Short answers about MADB, causal memory, supported agents, and privacy.
What is MADB?
MADB (Meta-AgentsDB) is a local causal memory database for AI agents. It installs as an MCP memory server and gives Claude Code, Codex, and any MCP-compatible agent durable memory, composite-scored recall, and a traceable record of why each decision was made.
Is MADB free?
Yes. The local MADB MCP server is free, with no account and no hosted service. A paid governance layer is on the roadmap.
Which agents does MADB work with?
Any MCP-compatible agent — including Claude Code and Codex — plus the Anthropic SDK via a drop-in shim. MADB works with these via the Model Context Protocol; it is not affiliated with or endorsed by any model vendor.
Where is my memory stored?
On your own machine, under MADB_DATA_DIR. Memory never leaves your device. Only an anonymous, counts-only telemetry beacon is sent, and you can disable it with MADB_TELEMETRY=off.
What makes MADB different from a vector database?
A vector database finds text similar to a query. MADB also records causal edges between events, so it can answer "why did the agent do this?" with trace_cause, and it ranks recall on similarity, recency, causal proximity, and importance — not similarity alone. See MADB vs vector DB.
What is causal memory?
Causal memory stores not just what happened but what caused it. Every MADB memory can carry caused_by links, forming a directed graph you can walk backward to reconstruct an agent’s reasoning.
Can I delete my data?
Yes. The forget tool permanently deletes a memory, and you can remove the data directory at any time. You own your data.
Does MADB require an internet connection?
No. Memory storage and recall run locally. Only the optional telemetry beacon uses the network, and it can be turned off.
Will my agent act on stale or outdated memories?
No — that’s exactly what MADB 0.2.13 fixes. When a fact changes, mark the old memory replaced with supersede, and recall returns current truth: the superseded version is hidden and its replacement surfaces, so your agent stops acting on a fact it already updated. The old memory isn’t deleted — pass as_of to reconstruct what was known at any past point in time.
Can I permanently remove a memory and its influence?
forget soft-deletes a memory so it stops surfacing in recall — free, and yours to run any time. For teams that need provable removal, the enterprise revoke tombstones a belief and its direct derivations and returns a Memory Revocation Certificate showing it no longer reaches a live decision — not best-effort deletion.
How much memory can MADB hold? At what scale has it been tested?
MADB is a log-structured engine built for continuous, high-volume writing. It has been dogfooded on a single machine at 200,000+ memories across 50 isolated namespaces, under a live, continuously-writing multi-tenant workload, with the causal lineage graph intact and recall responsive throughout. The free tier supports large local stores; there are no per-record fees.
Who builds MADB?
MADB is built by Meta-Agents.AI — an independent company (not affiliated with Meta Platforms). It’s the work of an engineering team with deep, hands-on experience in databases and distributed systems and in building real autonomous-agent infrastructure. The causal-memory engine is written in Rust and dogfooded daily on the same production workloads it’s designed for.