mcp memory agents sessions 

Logbook

Project memory across sessions for AI agents. A queryable decision log that survives between sessions.

Version

v0.1.3

License

MIT

Platforms

Node 18 or newer, Any MCP client

Interfaces

CLI, MCP

View on GitHubnpm packageMCP server

Overview

Agents forget everything between sessions. The decision that a domain is served by Cloudflare Pages and never deploy to Netlify is paid for once and lost. Logbook persists it in the repository as a tagged, searchable entry, so the next session starts where the last one finished.

Setup

npm install -g logbook-mcp

Add the server to your MCP client.

{
  "mcpServers": {
    "logbook": {
      "command": "logbook-mcp",
      "args": []
    }
  }
}

Entries are stored in .logbook/logbook.json in the repository and travel with the code.

Usage

  • logbook.record record a decision, finding, gotcha, or note with a scope and tags.
  • logbook.search search by text, scope, tags, or type.
  • logbook.recent the latest entries.
  • logbook.stats counts by type and scope.
  • logbook.forget remove an entry by id.

Typical agent instructions:

  • “What do we know about deploying this project?”
  • “Record that decision so the next session remembers it.”
  • “Have we hit this gotcha before?”

Gains

  • Institutional memory for agents. Knowledge is never re derived.
  • Decisions carry a why, so later agents understand the constraint.
  • Searchable and version controlled with the repository.
  • Token savings compound. Every recalled entry is context that was not re built.

Repository