pickfit

BrowseMCP servers

klypix-mcp

Shared project memory for coding agents using one brain.klypix file committed with code.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 20 or newer
  1. install klypix-mcp globally via npm

    npm install -g klypix-mcp
Where the README and reality differ
  • README: klypix-mcp --version / --help shows version/help
    What worked: klypix-mcp without verb runs MCP server; --version/--help hang waiting for stdio, doctor command shows version v1.110.0

Check that it works

npx klypix-mcp doctor 2>&1 | tail -n 30
npx klypix-mcp runtime 2>&1 | tail -n 30
npx klypix-mcp conformance 2>&1

The output should contain “KLYPIX MCP conformance v1.110.0: PASS”.

First thing to try

pwd; ls -la; cat ~/.local/bin/klypix-mcp | head -n 5; klypix-mcp init 2>&1; ls -lh *.klypix 2>&1; ls -lh brain* 2>&1
npx klypix-mcp doctor 2>&1 | tail -n 30
npx klypix-mcp runtime 2>&1 | tail -n 30
npx klypix-mcp conformance 2>&1

Add it to your agent

claude mcp add klypix-mcp -- klypix-mcp --vault '<vault>'
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "klypix-mcp": {
      "command": "klypix-mcp",
      "args": [
        "--vault",
        "<vault>"
      ]
    }
  }
}

Replace <vault> with your own path.

Run klypix-mcp init in your project folder to create the brain file, then add klypix-mcp --vault <project folder> to your MCP client as a server.

What it does

  • Leave notes and handoffs between sessions
    How to use it
    1. Run klypix-mcp init in your project folder.
    2. Connect your MCP client to klypix-mcp --vault <project folder>.
    3. Call the brain_note tool with your note as "text" and an optional "area", such as {"text":"<your note>","area":"<area>"}.
    Tested
  • Carry project decisions over across sessions
    Not shown working
  • Get a warning when sessions touch the same files
    Not shown working
  • Guard shared git checkouts
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • carry project decisions over across sessions
  • warn when two sessions touch same file
  • leave notes and handoffs between sessions
  • record corrections that supersede old decisions
  • ask what the project believed at a past date

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 1 Nov 2026
  • Version 1.110.0

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

Differences the test machine hit

  • README: npx klypix-mcp install as install
    In the test: npm install -g klypix-mcp used; install requires interactive project detection, global install provides launch command for offline replay

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.