pickfit

BrowseMCP servers

Bastra Recall

Local-first memory that stores preferences and decisions as Markdown for AI assistants.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node 22-26
  1. Install bastra-recall globally via npm

    node --version && npm --version && npm install -g bastra-recall
  2. Expose MCP forwarder on PATH

    ln -sf "$HOME/.local/lib/node_modules/bastra-recall/node_modules/@bastra-recall/daemon/dist/mcp-forwarder.js" "$HOME/.local/bin/bastra-recall-mcp" && chmod +x "$HOME/.local/bin/bastra-recall-mcp" && ls -l ~/.local/bin/bastra-recall-mcp && ls ~/.pickfit/mcp_probe.py

Check that it works

ls ~/.local/lib/node_modules/bastra-recall/node_modules/@bastra-recall/ 2>&1; ls ~/.local/lib/node_modules/bastra-recall/node_modules/.bin/ 2>&1; which bastra && bastra --version

The output should contain “1.1.1”.

First thing to try

bastra doctor 2>&1

Add it to your agent

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

Run bastra doctor to check the setup, then add Bastra Recall as an MCP server in your AI assistant so it can use tools such as recall and save_memory.

What it does

  • Keep preferences, decisions and lessons across sessions
    Not tested
  • Retrieve relevant memories before starting work
    Not shown working
  • Share the same vault across AI tools
    Not tested
  • Browse memories in the local vault map
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • keep preferences, decisions and fixes across chat sessions
  • store each decision and lesson as its own file
  • browse and search memories via local vault map

An alternative to CLAUDE.md and AGENTS.md.

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 30 Oct 2026
  • Version 1.1.1

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

Differences the test machine hit

  • README: npx bastra-recall install with no prior global install
    In the test: npm install -g bastra-recall so bastra is on PATH for offline replay; npx fetch would fail with network off
  • README: MCP forwarder launch command on PATH
    In the test: symlink daemon dist/mcp-forwarder.js to ~/.local/bin/bastra-recall-mcp; only bastra is on PATH after install
  • README: MCP tools work with no setup
    In the test: BASTRA_VAULT_PATH=/tmp/bastra-vault with pre-created dir, otherwise recall/save_memory return tools/call error

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.