Back to Browse

Memoir MCP Server

Developer ToolsLow Risk10.0Local
Free

Structured session journals for AI agents. Persistent memory across sessions.

About

Structured session journals for AI agents. Persistent memory across sessions.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (4/4 approved).

4 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Max characters for content fieldsOptional

Environment variable: MEMOIR_MAX_CONTENT

Max characters for outcome/resolution fieldsOptional

Environment variable: MEMOIR_MAX_OUTCOME

Max entries per sessionOptional

Environment variable: MEMOIR_MAX_ENTRIES

Max sessions per project (rolling)Optional

Environment variable: MEMOIR_MAX_SESSIONS

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-bighippoman-memoir": {
      "env": {
        "MEMOIR_MAX_CONTENT": "your-memoir-max-content-here",
        "MEMOIR_MAX_ENTRIES": "your-memoir-max-entries-here",
        "MEMOIR_MAX_OUTCOME": "your-memoir-max-outcome-here",
        "MEMOIR_MAX_SESSIONS": "your-memoir-max-sessions-here"
      },
      "args": [
        "-y",
        "memoir-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

memoir-mcp

Structured session journals for AI agents. Persistent memory across sessions -- no more repeating dead ends.

When a session ends, all reasoning is lost -- what was tried, what failed, what's blocked. The next session starts from scratch and repeats the same mistakes. memoir logs it all and hands it off so the next session picks up where the last one left off.

Works with any MCP client: Claude Code, Cursor, Codex, Windsurf, and more.

Install

Claude Code

claude mcp add memoir -s user -- npx -y memoir-mcp

Other MCP clients

npx -y memoir-mcp

How it works

  • Automatic project detection -- identifies the project by its git root, so logs stay scoped without any configuration.
  • Implicit sessions -- a session is created automatically on first log. No setup step.
  • Rolling retention -- keeps the last 20 sessions per project (configurable). Old sessions are pruned automatically.

Tools

Write

ToolDescription
log_attemptRecord something that was tried and its outcome.
log_blockerFlag something that's stuck and why.
resolve_blockerMark a blocker as resolved with what fixed it.
log_decisionRecord a design or architecture choice and its rationale.
end_sessionClose the current session with an optional summary.

Read

ToolDescription
get_handoffStructured summary of the last session -- what was attempted, what's blocked, what was decided.
get_historyQuery past sessions (default: last 3, max 20).
get_blockersList unresolved (or resolved) blockers across all sessions.

Storage

Single SQLite file at ~/.memoir/memoir.db. No API keys, no external services.

Configuration

All limits are configurable via environment variables:

VariableDefaultDescription
MEMOIR_MAX_CONTENT500Max characters for content fields
MEMOIR_MAX_OUTCOME300Max characters for outcome/resolution fields
MEMOIR_MAX_ENTRIES50Max entries per session
MEMOIR_MAX_SESSIONS20Max sessions per project (rolling)

Example with custom limits:

claude mcp add memoir -s user -e MEMOIR_MAX_CONTENT=1000 -e MEMOIR_MAX_ENTRIES=100 -- npx -y memoir-mcp

Handoff output uses a compact format to keep context window usage low.

License

MIT

Reviews

No reviews yet

Be the first to review this server!