Ext Ops Panel
Open dashboard
Comparison

Rube vs HaloPSA MCP

Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). HaloPSA MCP is an MCP server published by Servosity. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceRubeHaloPSA MCP
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.19
Forks (GitHub): 12
Stars (GitHub): 59
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

Rube vs HaloPSA MCP
FactRubeHaloPSA MCP
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub59
Forks (GitHub) (differs)No figure on GitHub12
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (rube.app/mcp)On your machine (https://github.com/Servosity/msp-skills/releases/download/halopsa-v0.2.19/halopsa-mcp.mcpb)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 110, secrets among them: 4
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/servosity/msp-skills
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

Rube

In its own words, on Docker MCP Catalog:

Access to Rube's catalog of remote MCP servers.

HaloPSA MCP

In its own words, on Official MCP Registry:

HaloPSA ticket triage, SLA-breach pre-emption, and cross-client analytics for any MCP agent.

How to run each

Rube As a remote MCP server

Claude Code
claude mcp add --transport http rube https://rube.app/mcp

Requires: RUBE_API_KEY (secret)

HaloPSA MCP

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

Requires: HALOPSA_CLIENT_ID (secret), HALOPSA_CLIENT_SECRET (secret), HALOPSA_OAUTH_SCOPE (secret), HALOPSA_TENANT, HALOPSA_TOKEN (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

Only Rube asks for

  • RUBE_API_KEY (secret)

Only HaloPSA MCP asks for

  • HALOPSA_BASE_URL
  • HALOPSA_CLIENT_ID (secret)
  • HALOPSA_CLIENT_SECRET (secret)
  • HALOPSA_DOMAIN
  • HALOPSA_NO_CONFIG_WRITE
  • HALOPSA_OAUTH_SCOPE (secret)
  • HALOPSA_SCOPE
  • HALOPSA_TENANT
  • HALOPSA_TOKEN (secret)
  • HALOPSA_TOKEN_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Rube · What it can do: HaloPSA MCP · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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