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
install onsystem globally via npm
npm install -g onsystem
Check that it works
onsystem --helpThe output should contain “Show this help”.
Add it to your agent
claude mcp add onsystem -- onsystemJSON 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 fixesNot tested
- Replace native HTML elements with design-system componentsNot tested
- Catch unknown components, props and variantsNot tested
- Check UI at every edit and pull requestNot tested
How far pickfit got
Linux x86_64
- Installs
- Connects
- A tool call works
- 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