pickfit

BrowseMCP servers

Aletheia

Free, local memory and rules hub for AI coding tools: persistent memory for Claude Code, Codex, Cursor and Gemini CLI. One SQLite store over MCP, REST and CLI. Rules sync to CLAUDE.md and AGENTS.md.…

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Bun >=1.1
  1. install Bun 1.4.4 runtime

    curl -fsSL https://bun.sh/install | bash 2>&1; ~/.bun/bin/bun --version

    Runs a downloaded script: read it before you run it.

  2. npm install -g aletheia-mem

    export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH"
    npm install -g aletheia-mem

Check that it works

export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH"; aletheia --version 2>&1

The output should contain “0.1.11”.

First thing to try

export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH"
timeout 5 aletheia install --list

Add it to your agent

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

Run aletheia install --list to see which coding tools Aletheia can connect to, then add the aletheia-mcp server to your MCP client.

What it does

  • Share saved memory across your coding tools
    How to use it
    1. Add aletheia-mcp as an MCP server in your coding tool.
    2. Call the save_memory tool with your text to store a memory.
    3. Call the search tool with a query to find saved memories.
    Tested
  • Use one memory store over MCP, REST or CLI
    Not shown working
  • Sync rules to your tools' instruction files
    Not shown working

How far pickfit got

Linux x86_64

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

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • share persistent memory across Claude Code, Codex, Cursor and Gemini CLI
  • write rules once and sync to tool instruction files
  • search shared memory
  • save a memory
  • load session start context

An alternative to claude-mem, Mem0, Zep/Graphiti, Supermemory and Basic Memory.

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 31 Oct 2026
  • Version 0.1.11

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

Differences the test machine hit

  • README: Bun >=1.1 required, then npm install -g aletheia-mem
    In the test: Bun must be installed manually first via bun.sh/install script
  • README: MCP launch command bun bin/mcp.mjs
    In the test: installed package provides aletheia-mcp binary (bun wrapper) for on-PATH stdio server
  • README: install step 1 runs https://bun.sh/install straight from the network
    In the test: nothing to change; a note: the box ran it without saving or reading it first, so pickfit did not inspect it

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.