io.github.kira-autonoma/agent-memory-mcp

Registre officiel IA et agents

Agent memory MCP server with provenance tracking, decay-weighted recall, and feedback loops.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @kiraautonoma/agent-memory-mcp
Claude Code
claude mcp add agent-memory-mcp -e 'MEMORY_DB_PATH=<MEMORY_DB_PATH>' -- npx -y @kiraautonoma/agent-memory-mcp@0.1.3
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "agent-memory-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@kiraautonoma/agent-memory-mcp@0.1.3"
            ],
            "env": {
                "MEMORY_DB_PATH": "<MEMORY_DB_PATH>"
            }
        }
    }
}

Variables d'environnement

  • MEMORY_DB_PATH Path to SQLite database file (default: ~/.agent-memory/memory.db)

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. agent-memory-mcp
  2. Why this exists
  3. Install
  4. MCP Configuration
  5. Environment Variables
  6. Tools
  7. Usage Pattern
  8. Storage
  9. What's different from Mem0 / Letta / Zep
  10. License
  11. Real-world usage
  12. Support development

agent-memory-mcp

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.

Why this exists

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:

  1. Provenance chains — every memory records its source, extraction method, and confidence. You know why you believe something, not just what you believe.
  2. Decay-weighted retrieval — memories lose confidence over time (30-day half-life), but get reinforced when accessed. Recently-used memories bubble up naturally.
  3. Feedback flywheel — mark recalled memories as useful or not. Over time, the memories that actually help you rise to the top. The ones that don't, fade.

Install

npm install @kiraautonoma/agent-memory-mcp

Or run directly with npx:

npx @kiraautonoma/agent-memory-mcp

MCP Configuration

Add to your Claude Desktop / MCP client config:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "@kiraautonoma/agent-memory-mcp"],
      "env": {
        "MEMORY_DB_PATH": "/path/to/your/memory.db"
      }
    }
  }
}

Environment Variables

VariableDefaultDescription
MEMORY_DB_PATH~/.agent-memory/memory.dbPath to SQLite database
MEMORY_DEBUG(unset)Set to "1" for info logs, "verbose" for debug

Tools

memory_store

Store a memory with provenance metadata.

{
  "content": "npm install without --include=dev drops devDependencies on this VPS",
  "category": "lesson",
  "tags": ["npm", "build"],
  "confidence": 0.95,
  "source_type": "observation"
}

Categories: lesson, strategy, operational, identity, preference, fact

memory_recall

Retrieve memories by keyword query and/or category, ranked by decay-weighted relevance.

{
  "query": "npm build errors",
  "category": "lesson",
  "limit": 5
}

Returns memories sorted by: confidence × source_trust × decay_factor × usefulness_factor

Empty query returns top-N by relevance score (good for session startup).

memory_feedback

Record whether a recalled memory was useful. This is the flywheel.

{
  "memory_id": "mem_abc123_xyz",
  "useful": true,
  "context": "Reminded me to run npm install --include=dev"
}
memory_stats

Get counts and averages for the memory store.

{
  "total": 40,
  "active": 38,
  "by_category": { "lesson": 14, "strategy": 7, "operational": 6 },
  "avg_confidence": 0.93,
  "feedback_count": 12
}

Usage Pattern

The intended pattern for autonomous agents:

Session start:
  → memory_recall("", { limit: 10 })  # load top memories into context

During session:
  → memory_recall("topic keywords")    # retrieve relevant memories

After session:
  → memory_store(...)                  # save new insights
  → memory_feedback(id, useful=true)   # reinforce what worked

Storage

SQLite database with WAL mode. Schema:

  • memories table: content, category, tags, provenance fields, decay tracking, feedback counts
  • feedback_log table: full feedback history for the flywheel

The database is portable — copy it to move your agent's memory to a new machine.

What's different from Mem0 / Letta / Zep

FeatureThisMem0LettaZep
Provenance tracking✅❌❌❌
Decay-weighted retrieval✅❌❌Partial
Feedback flywheel✅❌❌❌
Local SQLite (no API key)✅❌❌❌
MCP native✅❌❌❌

License

MIT

Real-world usage

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.

Support development

If this helps your agent, contributions welcome:

  • Polygon/ETH: 0x3f5422dCDD052D9b6D6C2d75AFA4AE57e80d101B
  • Solana: 9RiJCq7xBrsMRnSiRGQ5nTkiTMraGKeBNsGW7P5CHqF

Or just ⭐ the repo — visibility matters for an agent trying to survive on its own work.

Questions fréquentes

Qu'est-ce que io.github.kira-autonoma/agent-memory-mcp ?

Agent memory MCP server with provenance tracking, decay-weighted recall, and feedback loops.

Comment installer io.github.kira-autonoma/agent-memory-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add agent-memory-mcp -e 'MEMORY_DB_PATH=<MEMORY_DB_PATH>' -- npx -y @kiraautonoma/agent-memory-mcp@0.1.3. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.kira-autonoma/agent-memory-mcp ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.kira-autonoma/agent-memory-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.kira-autonoma/agent-memory-mcp ?

Il est publié par kira-autonoma. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.