pickfit

BrowseMCP servers

.dai + .cai

Plain-text local memory files for AI covering chat history and code graph.

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: Node 18+, Python 3.10+
  1. install daidocs globally via npm (provides mcp_server.mjs)

    npm install -g daidocs

Add it to your agent

claude mcp add daidocs -- node $HOME/.local/lib/node_modules/daidocs/mcp_server.mjs
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "daidocs": {
      "command": "sh",
      "args": [
        "-c",
        "exec node \"$HOME/.local/lib/node_modules/daidocs/mcp_server.mjs\""
      ]
    }
  }
}

Add the daidocs MCP server to your AI client, then ask it to use tools such as list_memories, recall_memory or save_memory.

What it does

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

  • Store AI memory as plain-text files
    Not tested
  • Answer code questions from a code graph
    Not tested
  • Send questions to code or to documents
    Not tested
  • Save browser AI chats on your computer
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • search .dai memory to answer a question
  • save a fact as a memory note

An alternative to Graphify.

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 5.1.1

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

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.