pickfit

BrowseMCP servers

Contentrain AI

Repo-native content governance that extracts app copy into Git-stored JSON and Markdown for review.

Use it

Before you install: known vulnerabilities

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

  • npm:@simple-git/argv-parser 1.1.1 simple-git: `VISUAL` editor environment variable is omitted from unsafe editor detection (GHSA-v5rq-49vh-5v5c, critical, fixed in 2.0.1)
  • npm:simple-git 3.36.0 simple-git unsafe-operation guard does not block trailer command configuration (GHSA-x6jw-m9v5-85vh, critical, fixed in 4.0.1)
See 3 more

Linux x86_64

  1. install contentrain globally via npm

    npm install -g contentrain
Where the README and reality differ
  • README: npx contentrain init works without git
    What worked: needs git repo initialized and committed; without it init fails with fatal: not a valid object name: 'master' even with --yes

Add it to your agent

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

Add the contentrain MCP server to your AI client, then ask it to run contentrain_status to see the state of your project's content.

What it does

  • Extract, review and ship structured content
    Not shown working
  • Turn hardcoded strings into structured content
    Test failed
  • Use the same content across web, docs and mobile
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • Rescue hardcoded strings into structured translatable content
  • Start new projects with a structured content layer
  • Serve same JSON and Markdown content across web, docs, mobile and backend

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.18.24

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

Differences the test machine hit

  • README: An MCP server over stdio writes only JSON-RPC messages to stdout
    In the test: This server wrote 1 other line(s) to stdout during the handshake; strict MCP clients may reject them.

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.