Ext Ops Panel
Open dashboard
Comparison

deployhq-cli vs Servonaut

deployhq-cli is a plugin bundle for AI coding tools published by deployhq. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Servonaut is an MCP server published by servonaut.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacedeployhq-cliServonaut
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.29.0
Forks (GitHub): 2
Stars (GitHub): 29
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

deployhq-cli vs Servonaut
Factdeployhq-cliServonaut
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)29 (better)
Forks (GitHub) (differs)1 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (servonaut)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/deployhq/deployhq-cligithub.com/zb-ss/servonaut
Changes in the last 7 days00
First seen2026-10-112026-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

deployhq-cli

In its own words, on Claude Code: claude-plugins-community:

Deploy code, manage servers, and automate infrastructure via the DeployHQ CLI. A Go binary that wraps the full DeployHQ REST API, designed for both humans and AI agents. Features --json output with breadcrumbs (suggested next commands), runtime self-discovery via dhq commands --json, and a comprehensive SKILL.md with decision trees. One-command setup: dhq setup claude.

Servonaut

In its own words, on Official MCP Registry:

Manage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec.

How to run each

deployhq-cli As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install deployhq-cli@claude-community

Servonaut As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio servonaut -- uvx --from "servonaut[mcp]" servonaut --mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: deployhq-cli · What it can do: Servonaut · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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