Verbative Memory

io.github.verbativePublished by GitHub account verbativev1.1.3Updated Oct 24, 2026

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

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

On-device memory for AI coding agents that captures commands, edits and test results and recalls relevant facts into each prompt.

What you can do
Remember, recall and search stored memories, with semantic ranking and a reranker surfacing only the most relevant facts per query. Ask questions against memory and list, get, pin, revise or forget individual memories. Edit core memories and give feedback on recalled items. Explore relationships, history, timeline and the raw event ledger of past commands, edits and test results. Capture and injection happen automatically in Claude Code CLI and Codex; other MCP clients call the tools manually.
When to use it
Worth adding when you want a coding agent to carry decisions, conventions and dead ends across sessions and agents, and to recall exact records of what was run or when a test started failing, without sending code to a cloud memory service.
Requirements
Runs as a local stdio process via npx or pip. macOS on Apple silicon or Windows 10/11 x64; Linux is not supported. A Verbative account is required, part of the Code Advanced plan with a 14-day free trial, and sign-in via the login command. First run downloads the on-device engine and models; later recall works offline.
Before you install
The engine is closed-source and shipped as a sealed compiled package, so its behavior cannot be inspected. It records every command, edit and test result in your repository, which may include sensitive content; memory files stay local unless you share them. A paid subscription is needed after the trial, and account or licensing questions go to the vendor.

Installation

In SourceWeft

  1. Open Verbative Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

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

pip:

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

Any MCP client (mcp.json / stdio):

json
{ "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.

Links

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 [email protected].


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.

Source: README.md at commit 44fe9cb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations