hostinger/api-mcp-server/ecommerce
Claude Code and agent skill by hostinger/api-mcp-server
- community
Checking that the SKILL.md file is still in the repository.
Provision a Hostinger Ecommerce backend for the Hostinger Headless flow: ensure the hostinger-ecommerce MCP is connected, create the headless website (frontend host) and a Hostinger Ecommerce STORE with a custom (headless) sales channel, set shipping + payment, and record it all in site.json.
Install
npx vskill@latest install hostinger/api-mcp-server/ecommerceSKILL.md
headless-step-provision-ecommerce
Provision a Hostinger Ecommerce backend for <domain> and prove it is ready. Two distinct things:
- A headless website (
type: "headless_ecommerce") — this is only the **hosting slot for the
storefront you'll build. It installs no store engine** (no /cms, no API on the domain).
- A Hostinger Ecommerce store — a separate object created through the Ecommerce API, with a
custom (headless) sales channel. The storefront reads this store's public Storefront Core V2 API, keyed on the sales channel. This is the real backend.
Out: site.json (store id, custom sales channel id, URLs).
## ⚠️ Prerequisite: thehostinger-ecommerceMCP server must be connectedStore management is not in thehosting/wordpressMCP groups — it's the separate`hostinger-ecommerce` group (ecommerce_*ops, OAuth-backed, no API token needed). Connectregisters it alongsidehostinger, so its tools are normally already in the session. If theyaren't (for example, a tool connected before connect registered both servers), register it now. Thecommand for each tool is in itsconnect/tools/<tool>.md; for Claude Code:```bashclaude mcp add hostinger-ecommerce --scope user -- "<command>" "<launcher>" hostinger-ecommerce-mcp```(Or enable the Ecommerce MCP in the Hostinger Connector.) A newly added MCP server only loadsafter a restart, so pause the run with register, restart, resume fromconnect/SKILL.md: savestate, ask the user to restart the tool and paste the same prompt, and end your turn. Check-state thenresumes at the stage that paused. Never spawn the server yourself or write a JSON-RPC client to reach it.Verify the tools work in-session with a search — e.g. "list stores" →ecommerce_stores_list— before proceeding.The authoritative, always-current build guide isecommerce_miscellaneous_custom-storefront-setup-instructions— read it once per build.
All website-lifecycle calls go through the hosting connector (execute); all store calls through the hostinger-ecommerce MCP.
Step 1 — The headless website (frontend host)
Same lifecycle as ../wordpress/SKILL.md Steps 1–2, but type: "headless_ecommerce":
- Detect:
hosting_websites_list/hosting_websites_list-setups(exact-match the domain).completed
→ adopt. running → record provision.in_progress and wait at the join. failed → stop, point at hPanel. If website_type is not headless (plain WordPress, Node.js, …), stop and tell the user — don't overwrite another kind of site.
- Create (only if no site exists):
hosting_websites_create { order_id, type: "headless_ecommerce", domain }
— omit `domain` for a temporary subdomain: the setup generates one itself and returns it (don't call a separate subdomain op first — there's no need in this flow). The response carries the generated domain; if it differs from the workspace dir, move ~/.hostinger/<old>/ → <new>/ (if <new>/ already exists, stop and ask instead of moving into it) and update brief.md. Don't wait here. At the join, cd "$HOME" && node <skill>/wait.mjs setup <domain> returns once the setup is completed (see Waiting on Hostinger in the top-level SKILL.md). website_type will be headless.
Onboarding handoff — an empty headless shell needs no new website. If the domain already has anempty headless shell (website_type: headless, setuptype: headless_empty, nothing installed —typically created in onboarding), adopt it as the storefront host and skip the create. Aheadless_ecommercewebsite installs no store engine either, so an empty headless shell is the hostyou need — there is no backend to "swap" on the website side. Record itsusername/order_idand gostraight to Step 2 (store + custom sales channel). Never callhosting_websites_createon a domain that alreadyhas a site.
Don't expect/cmsor any API on this domain — it serves the storefront you build (Step 6) anddeploy (Step 8).
Step 2 — Resolve or create the store + custom sales channel
ecommerce_stores_list → reuse an existing store if this build already made one; otherwise create:
This returns store.id (store_*) and a custom sales_channel.id (scha_*) in one call — the custom channel is what the headless storefront is keyed on. (You can also add one later with ecommerce_sales-channels_create { store_id, type:"custom", name }.) Currency comes from country_code (default_currency_code); all prices are minor units (cents).
Step 3 — Store readiness: shipping + payment
A store needs ≥1 shipping zone and ≥1 payment method to check out.
- Shipping:
ecommerce_shipping_set-store { store_id, price }(minor units; 0 = free). - Payment:
ecommerce_payments_enable-manual-method { store_id, title }.
Known gate — free accounts have no payment method, and therefore no checkout. On a **freeaccount** (and any account/store without a paid Hostinger Ecommerce plan),enable-manual-methodreturns HTTP 402, and checkout later fails with400 payment_provider_not_configured. This isexpected, not an error — payment, and therefore checkout, is simply unavailable on the plan. Thecatalog and the storefront still work fully. Never block, stop, loop or retry the build on this:- Recordpayment_enabled: falseinsite.json(setshipping_enabledas usual).- Tell the user in one line that checkout needs a paid Ecommerce plan, and carry straight on.- Treat the 402 as a normal outcome — don't surface it as a failure or re-attempt the call.- Never ask the user for payment credentials.Every downstream stage readssite.json → ecommerce.payment_enabledand, when it isfalse, skipsall checkout wiring and verification (see content-model Step 5, frontend, deploy). A store withpayment_enabled: falseis a complete, valid build — a browsable catalog without checkout.
Step 4 — Verify
ecommerce_stores_metadata { store_id }→has_shippingtrue;has_payment_methods(may be false,
see the gate); read default_currency (decimal_digits, template) here, don't guess.
- Public Storefront V2 answers for the channel (no auth):
GET https://api-ecommerce.hostinger.com/v2/channels/<scha_*>/products?limit=100 → 200 (empty until content-model seeds products — fine here).
GET https://<domain>/returns the Hostinger default page until the storefront is deployed — expected.
Step 5 — Record site.json
No secrets in site.json. After deploy, link the channel to the live domain with ecommerce_sales-channels_update { store_id, sales_channel_id, url } (done in the deploy stage).
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/headless/steps/03-provision/ecommerce/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/hostinger/api-mcp-server/ecommerce)