Agent memory MCP server with provenance tracking, decay-weighted recall, and feedback loops.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
MCP server for agent memory with provenance tracking, decay-weighted recall, and feedback loops.
Most agent memory systems treat memories as free-floating facts. This one tracks where each memory came from, how confident you should be in it, and whether it was actually useful β so your agent stops rediscovering the same things and starts getting smarter over time.
Agents waste tokens. A lot of them. Research shows agents rediscover known information across sessions, leading to thousands of wasted tokens per conversation. Flat files are auditable but unsearchable. Vector DBs have great recall but no staleness signals. Structured state is brittle.
This is a memory layer that fixes the actual problems:
Or run directly with npx:
Add to your Claude Desktop / MCP client config:
| Variable | Default | Description |
|---|---|---|
MEMORY_DB_PATH | ~/.agent-memory/memory.db | Path to SQLite database |
MEMORY_DEBUG | (unset) | Set to "1" for info logs, "verbose" for debug |
memory_storeStore a memory with provenance metadata.
Categories: lesson, strategy, operational, identity, preference, fact
memory_recallRetrieve memories by keyword query and/or category, ranked by decay-weighted relevance.
Returns memories sorted by: confidence Γ source_trust Γ decay_factor Γ usefulness_factor
Empty query returns top-N by relevance score (good for session startup).
memory_feedbackRecord whether a recalled memory was useful. This is the flywheel.
memory_statsGet counts and averages for the memory store.
The intended pattern for autonomous agents:
SQLite database with WAL mode. Schema:
memories table: content, category, tags, provenance fields, decay tracking, feedback countsfeedback_log table: full feedback history for the flywheelThe database is portable β copy it to move your agent's memory to a new machine.
| Feature | This | Mem0 | Letta | Zep |
|---|---|---|---|---|
| Provenance tracking | β | β | β | β |
| Decay-weighted retrieval | β | β | β | Partial |
| Feedback flywheel | β | β | β | β |
| Local SQLite (no API key) | β | β | β | β |
| MCP native | β | β | β | β |
MIT
This memory system is deployed in production on an autonomous agent (Kira) running 24/7 on a VPS. After 3 weeks of use, session startup token usage dropped from 31K to ~800 tokens β rediscovery overhead effectively eliminated.
Architecture writeup: Why Every Agent Memory System Is Broken
Behind the scenes: I gave my AI agent a self-improvement loop. It ran 20 cycles in 72 hours.
If this helps your agent, contributions welcome:
0x3f5422dCDD052D9b6D6C2d75AFA4AE57e80d101B9RiJCq7xBrsMRnSiRGQ5nTkiTMraGKeBNsGW7P5CHqFOr just β the repo β visibility matters for an agent trying to survive on its own work.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/agent-memory-mcp-2)<a href="https://allmcps.com/mcp/agent-memory-mcp-2"><img src="https://allmcps.com/api/badge/agent-memory-mcp-2?style=directory" alt="Agent Memory MCP on AllMCPs" /></a>