CMDOP Machine Care vs TacticalRMM
CMDOP Machine Care is an MCP server published by commandoperator. Marketplaces we read that list it: 1 (Official MCP Registry). TacticalRMM is an MCP server published by shin2344234. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  CMDOP Machine Care |  TacticalRMM |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.0 Downloads/month (PyPI): 112 Downloads/week (PyPI): 34 Forks (GitHub): 0 Stars (GitHub): 3 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 | CMDOP Machine Care | TacticalRMM |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 3 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/commandoperator/cmdop-care:v0.1.2) | On your machine (trmm-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/commandoperator/cmdop-care-mcp | github.com/shin2344234/trmm-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
CMDOP Machine Care
Read-only health and storage diagnostics for an enrolled CMDOP machine fleet.
TacticalRMM
Read your TacticalRMM fleet; run commands only after per-command human approval.
How to run each
CMDOP Machine Care As a local MCP server: Docker image
claude mcp add --transport stdio cmdop-care -- docker run -i --rm ghcr.io/commandoperator/cmdop-care:v0.1.2TacticalRMM As a local MCP server: PyPI package
claude mcp add --env "TRMM_API_URL=<YOUR_TRMM_API_URL>" --env "TRMM_COMMAND_API_KEY=<YOUR_TRMM_COMMAND_API_KEY>" --env "TRMM_READONLY_API_KEY=<YOUR_TRMM_READONLY_API_KEY>" --transport stdio trmm-mcp -- uvx trmm-mcpRequires: TRMM_API_URL, TRMM_COMMAND_API_KEY (secret), TRMM_READONLY_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 CMDOP Machine Care publish no settings it asks for, so we do not compare settings.
What it can do: CMDOP Machine Care · What it can do: TacticalRMM · Compare two other plugins
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.