Keeps coding agents on your design system: catches palette colors, native elements and APIs your system lacks, at eve...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Multiple
Fastest way to find out if onsystem belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add onsystem -- npx onsystemRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove onsystemNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ onsystem ← registers here
Keeps coding agents on your design system: catches palette colors, native elements and APIs your system lacks, at every edit and pull request, with the fix. Set it up once in your design-system package; every app in your monorepo gets it.
Source: GitHub repository
Source check: November 3, 2026
Upstream commit: November 1, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.