hostinger · catalog manifest
Saved declaration
{
"name": "hostinger",
"author": {
"name": "Hostinger"
},
"source": {
"sha": "569880c60681a7068b3ca8ca84e2fe7ab6cfa7ff",
"url": "https://github.com/hostinger/claude-plugin.git",
"source": "url"
},
"category": "deployment",
"homepage": "https://www.hostinger.com",
"description": "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 deployment skill. Try \"deploy my static site to Hostinger\", \"deploy this Next.js app to example.com\", \"create an A record pointing example.com to 1.2.3.4\", or \"show VPS metrics for the last 24 hours.\"",
"displayName": "Hostinger"
}
hostinger · catalog manifest
Saved declaration
{
"name": "hostinger",
"author": {
"name": "Hostinger"
},
"source": {
"sha": "10259650b82ceee43741ce2f8a7fa564a8c286c7",
"url": "https://github.com/hostinger/claude-plugin.git",
"source": "url"
},
"category": "deployment",
"homepage": "https://www.hostinger.com",
"description": "Deploy, manage and monitor Hostinger services — Websites, Domains, Ecommerce, Email Marketing, Subscriptions & Payments, and VPS. Authenticate via browser (OAuth) or API token.",
"displayName": "Hostinger"
}
hostinger · catalog manifest
Saved declaration
{
"name": "hostinger",
"source": {
"sha": "569880c60681a7068b3ca8ca84e2fe7ab6cfa7ff",
"url": "https://github.com/hostinger/claude-plugin.git",
"source": "url"
},
"category": "deployment",
"homepage": "https://www.hostinger.com",
"description": "Deploy, manage and monitor Hostinger services — Websites, Domains, Ecommerce, Email Marketing, Subscriptions & Payments, and VPS. Authenticate via browser (OAuth) or API token.",
"displayName": "Hostinger"
}
hostinger · catalog manifest
Saved declaration
{
"name": "hostinger",
"author": {
"url": "https://www.hostinger.com",
"name": "Hostinger"
},
"license": "MIT",
"version": "1.2.0",
"homepage": "https://developers.hostinger.com",
"repository": "https://github.com/hostinger/claude-plugin",
"description": "Deploy, manage and monitor Hostinger services — Websites, Domains & DNS, Ecommerce, Email, Email Marketing, WordPress, Subscriptions & Payments, and VPS. Runs as a remote MCP server with browser (OAuth) sign-in — nothing to install locally."
}
Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.
