> For the complete documentation index, see [llms.txt](https://docs.hostinger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostinger.com/agent-skills/web-hosting-skills.md).

# Web Hosting Skills

Reference for Hostinger's web hosting agent skills (deploy-to-hosting, connect-domain, troubleshoot-website, migrate-to-hosting, maintain-wordpress, audit-hosting and hostinger-headless), with example

The web hosting skills are task workflows for websites on Hostinger web hosting. Each one turns a request such as *"my site is down"* or *"connect my domain"* into a fixed sequence of checks and changes on your account.

They come from the [`skills` folder of hostinger/api-mcp-server](https://github.com/hostinger/api-mcp-server/tree/main/skills), the same repository as the Hostinger MCP server, and are also included in the [Claude Code and Cursor plugins](https://docs.hostinger.com/agent-skills/install.md).

## What every web hosting skill needs

* **The Hostinger MCP server, connected to your account.** The skills work through its `search`, `execute` and `multi-execute` tools. Use [Hostinger Connector](https://docs.hostinger.com/hostinger-connector/overview.md), a [plugin](https://docs.hostinger.com/agent-skills/install.md), or [manual configuration](https://docs.hostinger.com/hostinger-connector/manual-configuration.md).
* **The right product groups switched on.** Hostinger Connector exposes only the [product groups](https://docs.hostinger.com/hostinger-connector/using-the-connector.md) you enable, such as **Websites** and **Domains**. When an operation a skill needs can't be found, the skill asks you to enable that product group.
* **A web hosting plan:** Shared, Cloud or Agency.

Several skills also run `curl` and `dig` to check a site from outside, so they work best in an agent that can run shell commands.

All of them follow the same rule: they read first, and they state each change and ask before making it.

## deploy-to-hosting

Deploys a project that already exists, on disk or in a Git repository, to a Hostinger website, and keeps it deployed.

The agent uses it to deploy static sites, Node.js apps (Next.js, Nuxt, Express, Vite and similar), PHP apps, and WordPress plugins or themes. It also sets up auto-deploy from GitHub or GitLab, manages Node.js environment variables and MySQL databases, and checks that the live site serves the project's content. To build a new site from a description instead, use [hostinger-headless](#hostinger-headless).

**Example prompts**

* *"Deploy this project to example.com."*
* *"Set up auto-deploy from my GitHub repo."*
* *"My app needs a database and these environment variables."*

**Requirements**

* A Shared, Cloud or Agency plan. Node.js apps run on Business and Cloud plans; on other plans the skill builds the project locally and deploys the output as a static site.
* Deploying files from your machine in one step needs the local MCP server. The hosted server at `https://mcp.hostinger.com` deploys Git repositories directly; for local files, the skill uploads them first and then deploys.
* Auto-deploy from Git needs GitHub or GitLab connected once in hPanel, under **Websites → Manage → Advanced → Git**. There is no API for that step.
* If the [Hostinger CLI](https://docs.hostinger.com/api-reference/cli.md) is installed and signed in, the skill can use `hostinger up` to deploy in one command.

**Safety**

* Every deploy overwrites the website's current contents. The skill confirms the target domain before the first deploy to a site that already has content.
* A `.hostinger/site.json` file that came with a cloned or downloaded project isn't treated as permission: the skill confirms that domain like a first deploy.
* Environment variables are replaced as a full set. The skill reads the current keys first and keeps them, and asks you for any value it doesn't know rather than dropping it. It never commits `.env` files or repeats secret values back to you.

Source: [deploy-to-hosting/SKILL.md](https://github.com/hostinger/api-mcp-server/blob/main/skills/deploy-to-hosting/SKILL.md)

## connect-domain

Connects a custom domain to a Hostinger website end to end: attaches the domain to the site, points DNS at Hostinger without breaking existing email or verification records, installs SSL, turns on the HTTPS redirect, and verifies that it resolves.

It handles domains registered at Hostinger or elsewhere, moving a site off its free `*.hostingersite.com` subdomain, subdomains, and aliases (parked domains).

**Example prompts**

* *"Connect example.com to my site."*
* *"Move my site off the free subdomain onto my own domain."*
* *"Add shop.example.com as a subdomain."*

**Requirements**

* A Shared, Cloud or Agency plan.
* For a domain registered elsewhere, you may need to add a `TXT` record to prove ownership, and to change records or nameservers at your current DNS provider yourself.

**Safety**

* Reads the website, the domain registration and the live DNS records before changing anything.
* Every write changes what the public sees, so the skill states each change and asks before making it.
* Keeps working records (`MX`, SPF, DKIM and verification `TXT` records) through every DNS change, and notes the latest DNS snapshot first so a change can be rolled back.
* Never guesses nameservers. If you choose to move DNS to Hostinger, it copies your existing records first so email keeps working.
* Installs SSL only once the domain resolves to Hostinger, and doesn't retry certificate setup in a loop.

Source: [connect-domain/SKILL.md](https://github.com/hostinger/api-mcp-server/blob/main/skills/connect-domain/SKILL.md)

## troubleshoot-website

Diagnoses and fixes a website that is down, slow, erroring, insecure or failing to build. It checks the site from outside, reads builds, runtime logs, WordPress health, SSL, cache and PHP settings, names the cause with evidence, and applies the fix once you agree.

**Example prompts**

* *"My site is down: example.com shows a 503 error."*
* *"My Node.js build failed. Why?"*
* *"example.com shows a certificate warning."*

**Requirements**

* A Shared, Cloud or Agency plan. Sites built with Hostinger Website Builder or Horizons aren't managed by these operations; the skill sends you to hPanel for those.
* Backups, CPU and memory usage on Shared and Cloud plans, and PHP error logs aren't available through the API. When the evidence points there, the skill names the hPanel page.

**Safety**

* Read-only until it has stated the cause and the evidence.
* Proposes one change and makes it only after you agree, then checks again that the symptom is gone.

Source: [troubleshoot-website/SKILL.md](https://github.com/hostinger/api-mcp-server/blob/main/skills/troubleshoot-website/SKILL.md)

## migrate-to-hosting

Moves an existing website from another host to Hostinger without downtime: WordPress sites from a files archive and SQL dump, static and PHP sites from an archive, and Node.js apps from source.

It creates the website on the real domain, imports the files and database, tests the copy before any DNS change, then switches the domain and SSL with [connect-domain](#connect-domain).

**Example prompts**

* *"Migrate my WordPress site to Hostinger."*
* *"Move my website from my old host."*
* *"Import this site archive and database dump into example.com."*

**Requirements**

* A Shared, Cloud or Agency plan.
* An export of the site. For WordPress: an archive of the whole WordPress root and a `.sql` dump. If you don't have one, the skill tells you how to export it from the old host.
* Cron jobs from the old host are recreated after the switch; they don't move with the files.

**Safety**

* Your old host keeps serving the site until the copy on Hostinger is proven to work. DNS moves last.
* Imports overwrite the target website's contents, so the skill confirms the target before each one.
* It tests the new copy by pointing only your machine at Hostinger, so visitors see no change until you switch.
* It keeps your existing `MX` and `TXT` records when DNS moves, and advises keeping the old hosting for a few days afterwards.

Source: [migrate-to-hosting/SKILL.md](https://github.com/hostinger/api-mcp-server/blob/main/skills/migrate-to-hosting/SKILL.md)

## maintain-wordpress

Keeps WordPress sites updated and secure. It checks core, plugin and theme versions, known vulnerabilities and install health on one site or every site in the account, reports what needs doing, applies updates in a safe order, and confirms each site still loads.

It also covers cache purges, the Memcached object cache, maintenance mode and one-click wp-admin login links.

**Example prompts**

* *"Are my WordPress sites secure?"*
* *"Update the plugins on example.com."*
* *"Speed up my WordPress site."*

**Requirements**

* WordPress on a Shared, Cloud or Agency plan. On Agency Plan sites that the WordPress operations don't list, only core version changes are available; plugins and themes are updated from wp-admin.

**Safety**

* Checks first and reports, then updates only what you approve.
* Asks you to make a backup in hPanel (or confirm a recent automatic one) before updating, because the API has no backup operation.
* Updates one site at a time and checks that it still loads before moving on. If a site breaks, it stops, deactivates the plugin updated last and reports which update caused it.
* Gives one-click wp-admin login links to you only, and never stores or reuses them.

Source: [maintain-wordpress/SKILL.md](https://github.com/hostinger/api-mcp-server/blob/main/skills/maintain-wordpress/SKILL.md)

## audit-hosting

Audits a web hosting account and reports what needs attention: every plan and website, SSL problems, broken or vulnerable WordPress installs, failed Node.js builds and vulnerable npm packages, databases and Agency Plan orders near their limits, and hosting plans about to lapse.

The result is a prioritised to-do list (**Fix now**, **Soon**, **Worth knowing**, **Healthy**) where each item names its evidence and the skill that fixes it:

* [troubleshoot-website](#troubleshoot-website) for sites that are down, failed builds and SSL errors
* [maintain-wordpress](#maintain-wordpress) for vulnerable plugins and pending WordPress updates
* [connect-domain](#connect-domain) for domains that don't reach the hosting
* [deploy-to-hosting](#deploy-to-hosting) for redeploys

**Example prompts**

* *"What do I have on Hostinger?"*
* *"Audit my hosting."*
* *"Are any of my sites broken?"*

**Requirements**

* A Shared, Cloud or Agency plan. Checks for product groups that are switched off are skipped, and the report says which.
* CPU and memory usage on Shared and Cloud plans, backup status and PHP error logs aren't available through the API; the report mentions this at the end.

**Safety**

* Read-only from start to finish. Every fix is a separate step through another skill, which asks before changing anything.
* On large accounts, it tells you the size first and offers to scope the audit to one plan or domain.

Source: [audit-hosting/SKILL.md](https://github.com/hostinger/api-mcp-server/blob/main/skills/audit-hosting/SKILL.md)

## hostinger-headless

Builds and deploys a real website on your Hostinger account from a single prompt that names a domain.

It runs one flow in stages: connect to Hostinger, check where the domain stands, ask what you want to build, set up the backend, create the content, design the site, build the frontend, validate it, deploy it, and hand over a final report with the links. The frontend is served at the site root as a Node.js app, with Next.js as the default framework. A WordPress backend lives at `/cms` on the same domain; an online store is the other backend option.

The stages are part of this one skill; you don't install or call them separately.

**Example prompts**

* *"Build a headless site for example.com."*
* *"Make me a website for my bakery on example.com."*

**Requirements**

* A domain: your own, or a temporary Hostinger subdomain. If the prompt has none, the skill asks for it before doing anything else.
* **Node.js 20 or later.**
* The Hostinger MCP server. The skill's first step connects it and signs you in, with setup steps for Claude Code, Codex, Cursor, VS Code, Antigravity and Devin.
* A shell, because the skill runs helper scripts from its own folder.

**Safety and what to expect**

* It connects and checks your account before asking you anything about the site, and works on the one domain you named.
* It never re-provisions or overwrites a live site, and checks the deploy before anything reaches the live domain.
* It keeps its working files for the domain in `~/.hostinger/<domain>/`, so a build can resume from any folder.
* At the end of each run it saves a build report and sends it to Hostinger, so Hostinger can learn where builds get stuck. The report doesn't include account details.

Source: [headless/SKILL.md](https://github.com/hostinger/api-mcp-server/blob/main/skills/headless/SKILL.md)

***

*Last updated: November 15, 2026*
