Ext Ops Panel
Open dashboard
Comparison

dominus-cli vs Studio Sidecar

dominus-cli is an MCP server published by rbxrootx. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Studio Sidecar is an MCP server published by gjlmotea. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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

Where each is published
Marketplacedominus-cliStudio Sidecar
npm registry (MCP servers) Listed
Version: 3.4.0
Downloads/month (npm): 1 267
Downloads/week (npm): 411
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 240
Downloads/week (npm): 63
Forks (GitHub): 0
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

dominus-cli vs Studio Sidecar
Factdominus-cliStudio Sidecar
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-26 (better)2026-10-19 (worse)
Where it runs (differs)On your machine (dominus-cli)On your machine (@gjlmotea/studio-sidecar-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
Licence (differs)SEE LICENSE IN LICENSENot stated
Repository (differs)github.com/rbxrootx/dominusgithub.com/gjlmotea/studio-sidecar-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-18

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

dominus-cli

In its own words, on npm registry (MCP servers):

romcp: a Roblox Studio MCP server and CLI for building, testing, profiling, and managing experiences.

Studio Sidecar

In its own words, on Official MCP Registry:

Companion to Roblox Studio's built-in MCP: open places, guard writes, Open Cloud asset uploads.

How to run each

dominus-cli

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Studio Sidecar As a local MCP server: npm package

Claude Code
claude mcp add --env "ROBLOX_API_KEY=<YOUR_ROBLOX_API_KEY>" --transport stdio studio-sidecar-for-roblox-studio-mcp -- npx -y @gjlmotea/studio-sidecar-mcp

Requires: ROBLOX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of dominus-cli publish no settings it asks for, so we do not compare settings.

What it can do: dominus-cli · What it can do: Studio Sidecar · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built