Build, connect, or iterate on a website hosted on Hostinger — provision hosting and a domain, optionally seed an ecommerce store with a real hosted checkout or a WordPress content backend (headless CMS/blog), build the frontend, deploy, and verify. Requires an authenticated Hostinger MCP session (see entry/skill.md).…
Hostinger Billing API for catalog browsing, payment method management, and subscription control. Use when checking pricing, managing payment methods, viewing subscriptions, or toggling auto-renewal.
Hostinger DNS API for zone record management, snapshots, and validation. Use when creating, updating, or deleting DNS records, restoring DNS snapshots, validating zone changes, or resetting DNS to defaults.
Hostinger Ecommerce API for managing online stores. Use when listing the stores on an account or creating a new store (which also provisions a primary sales channel).
Hostinger Horizons API for the AI website builder. Use when creating a website, landing page, blog, or web app from a natural-language prompt, or when getting an editor link to modify an existing Horizons website.
Hostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.
Deploy a PHP (or other no-build) Agency Plan website from an archive via public-api, using standalone MCP tools/plain curl instead of a filesystem-driven deploy tool. Use when asked to deploy a PHP app to an Agency Plan / h5g / agency-hosting website.
Deploy a node-static Agency Plan website (Node.js-built static site, or a plain simple static site) from an archive via public-api, using standalone MCP tools/plain curl instead of a filesystem-driven deploy tool. Use when asked to deploy/build a static or node-static app on an Agency Plan / h5g / agency-hosting…
Deploy a Node.js application (needs a build step) to a Hostinger "hosting" website via public-api, using standalone MCP tools/plain curl instead of a filesystem-driven deploy tool. Use when asked to deploy/build a Node.js/JS app on hosting (not Agency Plan).
Deploy a pre-built static site (HTML/CSS/JS, no build step) to a Hostinger "hosting" website via public-api, using standalone MCP tools/plain curl instead of a filesystem-driven deploy tool. Use when asked to deploy/upload a static site to hosting (not Agency Plan).
Deploy a WordPress plugin (a directory of files, not a single archive) to a Hostinger "hosting" WordPress website via public-api, using standalone MCP tools/plain curl instead of a filesystem-driven deploy tool. Use when asked to deploy/upload a WP plugin.
Import a full WordPress website (archive + database dump) into a Hostinger "hosting" website via public-api, using standalone MCP tools/plain curl instead of a filesystem-driven deploy tool. Use when asked to import/restore a whole WordPress site on hosting (not Agency Plan).
Deploy a WordPress theme (a directory of files, not a single archive) to a Hostinger "hosting" WordPress website via public-api, using standalone MCP tools/plain curl instead of a filesystem-driven deploy tool. Use when asked to deploy/upload a WP theme.