Download for MacApple silicon, macOS 14+
Skill

deploy-to-hosting

@hostinger Updated 2026-10-23

Deploy an existing project to a website on Hostinger web hosting (Shared, Cloud or Agency plans) and keep it deployed: picks the right deploy for static sites, Node.js apps (Next.js, Nuxt, Express, Vite and similar), PHP apps and WordPress plugins or themes, sets up auto-deploy from GitHub or GitLab, manages Node.js environment variables and MySQL databases, and verifies the live site. Triggers: deploy this project, deploy to Hostinger, push my app live, redeploy, set up auto-deploy, connect my GitHub repo, add environment variables, my app needs a database, deploy my WordPress plugin or theme.

libraries

Install

With your agent

Install OMGSkills skill "hostinger/claude-plugin:skills/deploy-to-hosting" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/hostinger/claude-plugin /tmp/claude-plugin && ln -s /tmp/claude-plugin/skills/deploy-to-hosting ~/.claude/skills/deploy-to-hosting

From README

Deploy to hosting Ship a project that already exists — on disk or in a Git repository — to a Hostinger website. Building a new site from a prompt (design, store, blog) is the hostinger-headless skill; this one takes code as it is. Calling the operations Read the inputSchema that search returns before the first call of each operation. If a name below is rejected as unknown, search for what the step does (e.g. "deploy static"). Batch reads with multi-execute; values pass between steps as $steps. . . Batches chain operations from one server only — the Hostinger Connector runs hosting, wordpress and agency-hosting as separate servers. Every deploy overwrites the website's current contents. Confirm the target domain with the user before the first deploy to a site that already has content. Pick the target website .hostinger/site.json in the project: reuse its domain and username (or websiteuid).