deployhq-cli vs io.github.FlayedOne/plesk-mcp
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). io.github.FlayedOne/plesk-mcp is an MCP server published by FlayedOne. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 |  io.github.FlayedOne/plesk-mcp | |
|---|---|---|
| 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: 0.1.1 Forks (GitHub): 1 Stars (GitHub): 6 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 | deployhq-cli | io.github.FlayedOne/plesk-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 6 (better) |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (plesk-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/deployhq/deployhq-cli | github.com/flayedone/plesk-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
deployhq-cli
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.
io.github.FlayedOne/plesk-mcp
Manage your Plesk hosting server using AI assistants.
How to run each
deployhq-cli
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.FlayedOne/plesk-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio plesk-mcp -- uvx plesk-mcpCommands 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 deployhq-cli publish no settings it asks for, so we do not compare settings.
What it can do: deployhq-cli · What it can do: io.github.FlayedOne/plesk-mcp · 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.