Hostinger vs MainWP
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). MainWP is an MCP server published by mainwp. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
| Marketplace |  Hostinger |  MainWP |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 1.2.0 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 1.2.0 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 1 738 Downloads/week (npm): 1 006 Forks (GitHub): 6 Stars (GitHub): 28 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 | Hostinger | MainWP |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 2 (worse) |
| Stars (GitHub) (differs) | 4 (worse) | 28 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 6 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@mainwp/mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 8 | 12 |
| Licence (differs) | MIT | GPL-3.0 |
| Repository (differs) | github.com/hostinger/claude-plugin | github.com/mainwp/mainwp-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 14 h ago | no 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
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
MainWP
Manage WordPress sites in MainWP from AI tools, with approval before destructive changes by default.
How to run each
Hostinger As a Claude Code plugin
/plugin install hostinger@claude-plugins-officialMainWP As a local MCP server: npm package
claude mcp add --env "MAINWP_APP_PASSWORD=<YOUR_MAINWP_APP_PASSWORD>" --env "MAINWP_URL=<YOUR_MAINWP_URL>" --env "MAINWP_USER=<YOUR_MAINWP_USER>" --transport stdio mainwp-mcp -- npx -y @mainwp/mcpRequires: MAINWP_APP_PASSWORD (secret), MAINWP_URL, MAINWP_USER
Commands 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
The marketplaces of Hostinger publish no settings it asks for, so we do not compare settings.
What it can do: Hostinger · What it can do: MainWP · Compare two other plugins
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. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.