pickfit

BrowseMCP servers

MIND-Mem

Governed replayable memory layer for AI agents with hybrid recall and audit evidence.

Tested on Linux

Use it

Linux x86_64

  1. install mind-mem with MCP extra via uv tool install

    uv tool install "mind-mem[mcp]" --force
Where the README and reality differ
  • README: pip install mind-mem provides mind-mem-mcp
    What worked: mind-mem-mcp requires extra: pip install "mind-mem[mcp]" (uv tool install "mind-mem[mcp]") else error No module named fastmcp

Check that it works

mind-mem-mcp --help

The output should contain “usage: mind-mem-mcp”.

First thing to try

mind-mem-init ~/my-workspace && ls ~/my-workspace && cat ~/my-workspace/mind-mem.json

Add it to your agent

claude mcp add mind-mem -- mind-mem-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "mind-mem": {
      "command": "mind-mem-mcp",
      "args": []
    }
  }
}

Run mind-mem-init <workspace> to create a workspace with a mind-mem.json config, then connect the MCP server to your AI client.

What it does

  • Give AI agents memory that persists
    Not shown working
  • Recall memory with audit evidence
    Not tested
  • Search memory with hybrid BM25 and vector search
    Not shown working
  • Find drift and contradictions in memory
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Good for

  • recall past decisions with hybrid BM25F search
  • detect drift and contradictions in memory

An alternative to Mem0, claude-mem and Zep.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 5.0.3

An MCP client handshake over stdio listed 107 tools, and a call to recall returned a result.

Differences the test machine hit

  • README: MIND_MEM_WORKSPACE env var implied
    In the test: MCP server requires MIND_MEM_WORKSPACE env var pointing to initialized workspace to start

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.