io.github.verbative/verbative-memory

Registre officiel Outils de développement

On-device, self-organizing memory for AI coding agents — recalls the right facts into each prompt.

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 verbative-memory
Claude Code
claude mcp add verbative-memory -- npx -y verbative-memory@1.1.3
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "verbative-memory": {
            "command": "npx",
            "args": [
                "-y",
                "verbative-memory@1.1.3"
            ]
        }
    }
}
PYPI package verbative-memory
Claude Code
claude mcp add verbative-memory -- uvx verbative-memory==1.1.3
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "verbative-memory": {
            "command": "uvx",
            "args": [
                "verbative-memory==1.1.3"
            ]
        }
    }
}

Documentation

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

Sommaire
  1. Verbative Memory
  2. How it works — capture everything, recall selectively
  3. Requirements
  4. Install
  5. Tools
  6. Privacy
  7. Links
  8. Issues

Verbative Memory

On-device memory system for AI coding agents — a dual-layer engine (distilled facts + a lossless event ledger), automatically captured and injected, exposed over MCP. Shared across agents, persistent across sessions; stored as plain, human-readable files in your repo — no memory cloud, no vendor database.

This repository is the public home for docs, install help, and issues. The engine is closed-source and ships as a sealed, compiled package — there is no source code here.

How it works — capture everything, recall selectively

  • Complete capture, in two layers. Underneath sits a lossless ledger: a mechanical, no-model record of every command, edit, and test result, so "what did we run" and "when did this test start failing" are exact, replayable facts. On top, an on-device model distills that stream into atomic, typed memories — decisions, conventions, and dead ends.
  • Selective recall — the two layers fused. A single recall surfaces only the handful of distilled facts that matter (ranked by semantic search and a reranker) and interleaves them, by time, with the exact ledger record around them: what you decided next to what you actually did. One answer, not a dump of the whole history.
  • Self-organizing. New facts reconcile against old ones, importance decays on per-type forgetting curves, frequently-recalled facts strengthen, and recurring specifics distill into higher-level insights.
  • Yours, on-device. Memories live in human-readable files in your project. Recall makes zero cloud calls.

Requirements

  • macOS (Apple silicon) or Windows 10/11 (x64). (Linux is on the roadmap.)
  • A Verbative account — Memory is part of the Code Advanced plan and starts with a 14-day free trial. See the plans and the Terms.

Install

Claude Code CLI — automatic capture and recall:

claude mcp add verbative-memory -- npx -y verbative-memory

pip:

pip install verbative-memory
verbative-memory login      # sign in with your Verbative account

Any MCP client (mcp.json / stdio):

{ "mcpServers": { "verbative-memory": { "command": "npx", "args": ["-y", "verbative-memory"] } } }

Automatic capture and injection are built for the Claude Code CLI and Codex; any other Model Context Protocol client can call the tools manually. The first run downloads the on-device engine and models once; after that, recall runs fully offline.

More detail in docs/INSTALL.md and at verbative.de/docs/memory.

Tools

remember · recall · search · ask · list · get · pin · forget · revise · edit_core · feedback · related · history · timeline · events — and more. See the docs.

Privacy

Capture, embeddings, reranking, and the knowledge graph all run locally. Your code and memories are not uploaded; the memory files stay in your project and leave your machine only if you choose to share them.

Issues

Bug reports and feature requests are welcome in the issue tracker — the place for anything about the docs or the tool. For your account, licensing, or a trial, email info@verbative.de.


Verbative is a product of Cramer Digital. Not affiliated with, or endorsed by, Anthropic. Verbative works alongside Anthropic's Claude and the Claude Code CLI; those names belong to Anthropic. See LICENSE.

Questions fréquentes

Qu'est-ce que io.github.verbative/verbative-memory ?

On-device, self-organizing memory for AI coding agents — recalls the right facts into each prompt.

Comment installer io.github.verbative/verbative-memory ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add verbative-memory -- npx -y verbative-memory@1.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.verbative/verbative-memory ?

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.verbative/verbative-memory est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.verbative/verbative-memory ?

Il est publié par verbative. 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.