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
Install bastra-recall globally via npm
node --version && npm --version && npm install -g bastra-recallExpose 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 --versionThe output should contain “1.1.1”.
First thing to try
bastra doctor 2>&1Add it to your agent
claude mcp add bastra-recall -- bastra-recall-mcpJSON 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 sessionsNot tested
- Retrieve relevant memories before starting workNot shown working
- Share the same vault across AI toolsNot tested
- Browse memories in the local vault mapNot tested
How far pickfit got
Linux x86_64
- Installs
- Connects
- 0 of 4 features work
- 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