Terminal
Terminal/Skill
Builds a website on Hostinger from a prompt: provisions hosting and a domain, optionally adds a store or WordPress blog, deploys and checks it.
By Hostinger
Works with
npx skills add hostinger/api-mcp-server --skill hostinger-headlessThis skill turns a prompt into a live website on Hostinger. Its job is to own the full run: check the account, provision hosting and a domain, seed the backend (an ecommerce store when the intent calls for selling), build the frontend, deploy it, and verify the result.
The frontend is built ad-hoc to the user's intent — there is no template library. The backend pieces are real Hostinger products: web hosting (static or Node.js), domains and DNS, Hostinger Ecommerce with its public Storefront API and hosted checkout, and WordPress as a headless CMS/blog backend read through the public WP REST API.
entry/skill.md.hostinger-hosting-mcp) rather than improvising around it.Resolve by intent first, disk second — never let an empty directory override what the user is asking for. Check iterate first (it's decided by an unambiguous on-disk signal):
iterate — a .hostinger/site.json is present in the project: the site is already deployed through this skill and the user wants changes. Reuse the recorded domain/site details; apply only the delta the new intent needs (edit frontend → redeploy; add a store → run references/STORE.md then redeploy). Never re-provision an existing site.connect — a frontend project already on disk (or brought in as a zip/export/URL) that is not yet on Hostinger, with language like "deploy this / host this on Hostinger / connect this project". Emptiness of the CWD at trigger time is not a create signal when a design is brought in from elsewhere.create — a new site from a prompt with nothing brought in: "build me a store / portfolio / site…".If signals conflict, ask the user — don't guess.
references/SETUP.md) — plan check, then provision the website on a free subdomain (or the user's own domain) and wait until it's ready.references/STORE.md, only when commerce is needed) — resolve or create the store and its custom sales channel, seed products/shipping/payment, and note the sales_channel_id for the frontend.references/WORDPRESS.md, only when owner-managed content is needed) — install WordPress on a dedicated subdomain, wait until it's ready, and hand the owner a wp-admin login link. The frontend reads it through the public WP REST API.references/STORE.md (catalog fetched at runtime from the public Storefront API, cart in localStorage, client-side checkout — never embed an API token in the site). For content runs, follow the frontend contract in references/WORDPRESS.md (posts fetched at runtime from the WP REST API, rendered HTML bodies, graceful empty states). When the app needs MySQL, follow references/DATABASE.md (which host each runtime connects to, credentials via env vars or a server-side config file, never in the frontend).references/DEPLOYMENT.md) — archive and deploy via the matching hosting operation, polling build logs for Node.js runs..hostinger/site.json into the project: { "domain", "username", "type": "static"|"nodejs", "sales_channel_id"?, "store_id"?, "cms_domain"? }. This is what makes future runs resolve as iterate.Run non-interactively wherever possible. The exceptions that must involve the user: the paid-plan confirmation, anything that costs money (a domain purchase, a new subscription), and picking between genuinely equal options the prompt doesn't decide.
| What | Path |
|---|---|
| Plan check + website/domain provisioning | references/SETUP.md |
| Store: seed the backend + the frontend API contract | references/STORE.md |
| WordPress: headless CMS/blog backend + the frontend read contract | references/WORDPRESS.md |
| Deploy: static vs Node.js, archive rules, logs, verify | references/DEPLOYMENT.md |
| Database + runtime: MySQL host per runtime, env vars, what to poll, runtime logs | references/DATABASE.md |
The inputSchema returned by search is authoritative for request shapes — read it before calling. Two live sources supersede anything written here when they disagree:
ecommerce_miscellaneous_custom-storefront-setup-instructions returns the current storefront integration guide from the server — execute it at the start of any store run.