pickfit

BrowseMCP servers

onsystem

Checks React UI edits and pull requests against design-system components and tokens with fixes.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 20.19 or later
  1. install onsystem globally via npm

    npm install -g onsystem

Check that it works

onsystem --help

The output should contain “Show this help”.

Add it to your agent

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

Add onsystem as an MCP server in your AI coding client, then ask the client to check your React UI with the check_ui tool.

What it does

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

  • Catch raw palette colors and get suggested fixes
    Not tested
  • Replace native HTML elements with design-system components
    Not tested
  • Catch unknown components, props and variants
    Not tested
  • Check UI at every edit and pull request
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

An alternative to @shadcn/lint.

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 0.12.1

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

Differences the test machine hit

  • README: npx -y onsystem starts MCP server with no path
    In the test: tool calls need absolute path argument pointing to a project folder; otherwise server returns isError with guidance to pass path or --root

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.