hostinger/api-mcp-server/ecommerce

Claude Code and agent skill by hostinger/api-mcp-server

Trust tier 2
  • community
LLM review pending
Source check pending

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/ecommerce

SKILL.md

headless-step-provision-ecommerce

Provision a Hostinger Ecommerce backend for <domain> and prove it is ready. Two distinct things:

  1. 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).

  1. 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: the hostinger-ecommerce MCP server must be connected
Store management is not in the hosting/wordpress MCP groups — it's the separate
`hostinger-ecommerce` group (ecommerce_* ops, OAuth-backed, no API token needed). Connect
registers it alongside hostinger, so its tools are normally already in the session. If they
aren't (for example, a tool connected before connect registered both servers), register it now. The
command for each tool is in its connect/tools/<tool>.md; for Claude Code:
```bash
claude 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 loads
after a restart, so pause the run with register, restart, resume from connect/SKILL.md: save
state, ask the user to restart the tool and paste the same prompt, and end your turn. Check-state then
resumes 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 is ecommerce_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":

  1. 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.

  1. 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 an
empty headless shell (website_type: headless, setup type: headless_empty, nothing installed —
typically created in onboarding), adopt it as the storefront host and skip the create. A
headless_ecommerce website installs no store engine either, so an empty headless shell is the host
you need — there is no backend to "swap" on the website side. Record its username/order_id and go
straight to Step 2 (store + custom sales channel). Never call hosting_websites_create on a domain that already
has a site.
Don't expect /cms or any API on this domain — it serves the storefront you build (Step 6) and
deploy (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:

json
{ "operation": "ecommerce_stores_create",
"params": { "name": "<store name>", "country_code": "US", "company_email": "<email>",
"company_name": "<store name>", "language": "en",
"sales_channel": { "type": "custom", "external_id": "<slug>-headless" } } }

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 **free
account** (and any account/store without a paid Hostinger Ecommerce plan), enable-manual-method
returns HTTP 402, and checkout later fails with 400 payment_provider_not_configured. This is
expected, not an error — payment, and therefore checkout, is simply unavailable on the plan. The
catalog and the storefront still work fully. Never block, stop, loop or retry the build on this:
- Record payment_enabled: false in site.json (set shipping_enabled as 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 reads site.json → ecommerce.payment_enabled and, when it is false, skips
all checkout wiring and verification (see content-model Step 5, frontend, deploy). A store with
payment_enabled: false is a complete, valid build — a browsable catalog without checkout.

Step 4 — Verify

  • ecommerce_stores_metadata { store_id } → has_shipping true; 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

json
{
"backend": "ecommerce",
"website_type": "headless",
"order_id": 1007223428,
"username": "u…",
"ecommerce": {
"store_id": "store_…",
"sales_channel": { "id": "scha_…", "type": "custom", "external_id": "…-headless" },
"currency": "usd",
"payment_enabled": false,
"shipping_enabled": true
},
"urls": {
"site": "https://<domain>",
"storefront_api": "https://api-ecommerce.hostinger.com/v2/channels/<scha_*>",
"store_admin": "https://ecommerce.hostinger.com/store/<store_*>"
},
"provisioned_at": "…",
"verified_at": "…"
}

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

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
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/hostinger/api-mcp-server/ecommerce/badge)](https://verified-skill.com/skills/hostinger/api-mcp-server/ecommerce)

Something wrong with this skill or its page? Tell us.