ateam vs Hostinger
ateam is a plugin bundle for AI coding tools published by Clawnify. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Hostinger is a plugin bundle for AI coding tools published by hostinger. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-16. 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 |  Hostinger | |
|---|---|---|
| Community marketplace clawnify/ateam | Listed Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 1.2.0 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 1.2.0 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 5 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 | ateam | Hostinger |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 13 (better) | 5 (worse) |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | 8 |
| Licence (differs) | GPL-3.0-or-later | MIT |
| Repository (differs) | github.com/clawnify/ateam | github.com/hostinger/claude-plugin |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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
ateam
Prepare a Linux VPS to run Ateam's agents and connect the desktop app to it.
Hostinger
Deploy, manage and monitor your Hostinger services directly from Claude Code. The plugin connects Claude to Hostinger's remote MCP server, so you can ship sites and apps, manage domains and DNS, run WordPress and operate VPS servers without leaving your coding environment. There's nothing to install on your machine: no Node.js, no npm, no local server. Key features include one-prompt deployments for static sites, Node.js apps (built on Hostinger), full WordPress site imports, and WordPress plugins and themes, plus static and PHP sites on the Agency Plan. Beyond deployments, Claude can search and register domains, edit DNS records and snapshots, check build logs, and manage mailboxes, online stores, email marketing contacts, subscriptions and orders. It can also control VPS firewalls, snapshots and monitoring. Sign in through your browser (OAuth) on first use, or set a `HOSTINGER_API_TOKEN` from hPanel. How to use: there are no commands to memorize. Describe what you want and Claude picks the right tool or dep
How to run each
ateam As a Claude Code plugin
/plugin marketplace add clawnify/ateam
/plugin install ateam@ateamHostinger As a Claude Code plugin
/plugin install hostinger@claude-plugins-officialCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hostinger has a remote endpoint we check. How we check endpoints
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: ateam · What it can do: Hostinger · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.