pickfit

BrowseMCP servers

RecallNest

Local-first shared memory layer for AI clients with hybrid recall and session continuity.

Use it

Before you install: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:zod 3.25.76 Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)

Linux x86_64

You need first

  • Runtimes: Bun
  • Keys or accounts: JINA_API_KEY
  1. download Bun installer

    curl -fsSL https://bun.sh/install -o /tmp/bun-install.sh
  2. install Bun prerequisite

    bash /tmp/bun-install.sh && export PATH="$HOME/.bun/bin:$PATH"
  3. npm install -g recallnest

    export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH" && npm install -g recallnest
Where the README and reality differ
  • README: npm install -g recallnest works via Node
    What worked: requires Bun on PATH first; launcher exits with instructions if bun missing
  • README: MCP server starts after install
    What worked: config.json not found until you copy config.json.example to ~/.config/recallnest/config.json

Add it to your agent

claude mcp add recallnest -e JINA_API_KEY='<JINA_API_KEY>' -- bun run '<install-folder>/src/mcp-server.ts'
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "recallnest": {
      "command": "bun",
      "args": [
        "run",
        "<install-folder>/src/mcp-server.ts"
      ],
      "env": {
        "JINA_API_KEY": "<JINA_API_KEY>"
      }
    }
  }
}

You fill in

  • JINA_API_KEY: embeddings API key (required)

Replace <install-folder> with the folder you ran the install steps in. Ask the user for JINA_API_KEY; pickfit never had a value, so these are placeholders.

Add RecallNest as an MCP server in your AI client, then call its tools such as store_memory, search_memory and resume_context from the client.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Share memory across all your terminals
    Not tested
  • Recall context saved in other windows
    Not tested
  • Save session checkpoints and resume context
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. A tool call works
  4. Works offline

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

Good for

  • store durable memory for future windows
  • recall memories at task start
  • resume context in a fresh window
  • import conversations from Claude Code, ChatGPT, Slack
  • consolidate memories offline via clustering and pruning

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 connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 4.0.0

An MCP client handshake over stdio listed 30 tools.

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.