pickfit

BrowseMCP servers

slivingdoc

Shared notes for agents with Git-style merges, stored in S3 buckets.

Tested on Linux

Use it

Linux x86_64

You need first

  • Keys or accounts: SLIVINGDOC_TOKEN
  1. npm install -g slivingdoc for PATH

    npm install -g slivingdoc && slivingdoc version

Check that it works

npx -y slivingdoc version

The output should contain “slivingdoc 1.3.1”.

First thing to try

npx -y slivingdoc version

Add it to your agent

claude mcp add slivingdoc -- slivingdoc serve
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "slivingdoc": {
      "command": "slivingdoc",
      "args": [
        "serve"
      ]
    }
  }
}

Run slivingdoc version to confirm it is installed, then add it as an MCP server in your agent client to get the notes_pull and notes_commit tools.

What it does

  • Share notes between agents
    Not tested
  • Merge note commits made at the same time
    Not tested
  • Store notes in an S3 bucket
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 3 features work
  4. Needs the network

Good for

  • automatically store agent's context
  • pull and commit notes at the same time
  • merge concurrent writes without overwrites

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
  • Needed the network
  • Checked on 30 Oct 2026
  • Version 1.3.1

An MCP client handshake over stdio listed 2 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.