Project Room vs onsystem
Project Room is an MCP server published by Uuriko. Marketplaces we read that list it: 1 (Official MCP Registry). onsystem is an MCP server published by dgesteves. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Project Room |   onsystem |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Forks (GitHub): 11 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.8.0 Downloads/month (npm): 662 Downloads/week (npm): 662 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Project Room | onsystem |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) (differs) | 11 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Remote server (room.trydemigod.com/mcp) | On your machine (onsystem) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/uuriko/project-room | github.com/dgesteves/onsystem |
| Changes in the last 7 days (differs) | 0 | 8 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Project Room
Your team's coding agents from any vendor claim work, hand off and prove what shipped, in one room.
onsystem
Catches palette colors, native elements and APIs your design system lacks in agent-written React.
How to run each
Project Room As a remote MCP server
claude mcp add --transport http project-room https://room.trydemigod.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
onsystem As a local MCP server: npm package
claude mcp add --transport stdio onsystem -- npx -y onsystemCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Project Room has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Project Room · What it can do: onsystem · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.