pickfit

BrowseMCP servers

thread-keeper

Local MCP server giving multiple AI coding CLIs shared memory and coordination.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python>=3.11
  1. install threadkeeper[semantic] via uv tool install

    uv tool install 'threadkeeper[semantic]'

Check that it works

which thread-keeper-setup && which tk-agent-status && tk-agent-status --help 2>&1 | head -n 100; thread-keeper-setup --help 2>&1

The output should contain “usage: tk-agent-status”.

First thing to try

tk-agent-status 2>&1; echo ---; thread-keeper-setup --dry-run 2>&1

Add it to your agent

claude mcp add thread-keeper -- $HOME/.local/share/uv/tools/threadkeeper/bin/python -m threadkeeper.server
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "thread-keeper": {
      "command": "sh",
      "args": [
        "-c",
        "exec \"$HOME/.local/share/uv/tools/threadkeeper/bin/python\" -m threadkeeper.server"
      ]
    }
  }
}

Add thread-keeper as an MCP server in your AI coding CLI; you can preview the setup first with thread-keeper-setup --dry-run.

What it does

  • Share memory between agents across sessions
    Not shown working
  • Coordinate agents running in parallel with signals
    Not shown working
  • Improve the skill library with automatic loops
    Not shown working

How far pickfit got

Linux x86_64

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

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

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 0.22.0

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

Differences the test machine hit

  • README: thread-keeper-setup registers MCP server and copies hooks
    In the test: setup reported no CLI detected and hook sources missing for tk-brief.sh etc. when installed via uv tool — server still starts

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.