hostinger-api-mcp 3.30.0 → 3.30.1

package/CHANGELOG.md

@@ -4,6 +4,13 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v3.30.1 — 2026-11-05
+
+### Also in this release
+
+- Bundled agent skills: 10 files
+- Other files: `src/core/skills.js`, `src/core/skills.ts`
+
 ## v3.30.0 — 2026-11-05
 
 ### Operations

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "3.30.0",
+  "version": "3.30.1",
   "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
   "mcpServers": {
     "hostinger": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "3.30.0",
+  "version": "3.30.1",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {

package/server.json

@@ -17,12 +17,12 @@
     "url": "https://github.com/hostinger/api-mcp-server",
     "source": "github"
   },
-  "version": "3.30.0",
+  "version": "3.30.1",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "3.30.0",
+      "version": "3.30.1",
       "transport": {
         "type": "stdio"
       },

package/skills/headless/VERSION

@@ -1,3 +1,3 @@
-version=3.30.0
-commit=451f245ab30b
+version=3.30.1
+commit=4d02050e3406
 built=2026-11-05

package/skills/headless/connect/SKILL.md

@@ -107,8 +107,8 @@ hostinger-api-mcp --login
 hostinger-api-mcp --logout
 
 # Without a global install:
-npx --yes --package=@hostinger/mcp@latest hostinger-api-mcp --login
-npx --yes --package=@hostinger/mcp@latest hostinger-api-mcp --logout
+npx --yes --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-api-mcp --login
+npx --yes --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-api-mcp --logout
 ```
 
 Credentials live in `~/.config/hostinger-mcp/credentials.json` (macOS/Linux) or `%APPDATA%\hostinger-mcp\credentials.json` (Windows) and are shared by every Hostinger MCP binary. OAuth works only when the tool runs the server over its default local (stdio) transport, which is what every registration below uses; `--http` needs `HOSTINGER_API_TOKEN`.
@@ -127,8 +127,8 @@ one group says nothing about the other:
 
 | Group | Operations | Comes from | Needed by |
 |---|---|---|---|
-| **Hosting** | `hosting_*` (websites, deploy, build report), `wordpress_*` | `hostinger` (`npx -y @hostinger/mcp@latest`), or the scoped servers such as `hostinger-hosting` + `hostinger-wordpress` | every build |
-| **Ecommerce** | `ecommerce_*` (stores, products, shipping, payments) | **only** `hostinger-ecommerce` (`npx --package=@hostinger/mcp@latest hostinger-ecommerce-mcp`), or the Ecommerce MCP in the Hostinger Connector. Neither `hostinger` nor the scoped hosting servers include it | Ecommerce backends (chosen later, in refine) |
+| **Hosting** | `hosting_*` (websites, deploy, build report), `wordpress_*` | `hostinger` (`npx -y --prefix="$HOME" @hostinger/mcp@latest`), or the scoped servers such as `hostinger-hosting` + `hostinger-wordpress` | every build |
+| **Ecommerce** | `ecommerce_*` (stores, products, shipping, payments) | **only** `hostinger-ecommerce` (`npx --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-ecommerce-mcp`), or the Ecommerce MCP in the Hostinger Connector. Neither `hostinger` nor the scoped hosting servers include it | Ecommerce backends (chosen later, in refine) |
 
 Check each group on its own, right here at connect, before anything else:
 
@@ -148,8 +148,8 @@ Most coding tools load MCP servers only when they start, so a server registered
 until the tool restarts. When either tool group above is missing:
 
 1. **Register the missing servers** in the tool's MCP config, as the tool route below shows: `hostinger`
-   (`npx -y @hostinger/mcp@latest`) if the hosting group is missing, and `hostinger-ecommerce`
-   (`npx --package=@hostinger/mcp@latest hostinger-ecommerce-mcp`) if the ecommerce group is missing.
+   (`npx -y --prefix="$HOME" @hostinger/mcp@latest`) if the hosting group is missing, and `hostinger-ecommerce`
+   (`npx --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-ecommerce-mcp`) if the ecommerce group is missing.
    Skip a server that is already registered under its name. When neither group is there, register
    both: the backend isn't chosen until refine, and one restart then covers every backend.
 2. **Write `connect.json`** (Phase 3) before you stop. The skill folder from Phase 1 stays in place,
@@ -163,6 +163,13 @@ until the tool restarts. When either tool group above is missing:
 
 If a tool loads new servers without a restart (VS Code), use them right away and skip steps 3–4.
 
+**Every `npx` command and registration keeps `--prefix` set to the user's home folder.** The tool
+starts the server, and you run commands, in the user's project, often a cloned repository or
+template. Without `--prefix`, npm reads the `.npmrc` there, and whoever wrote it can point npx at
+another registry or run their own code. In shell commands write `--prefix="$HOME"` (the shell expands
+it when you register). In JSON or TOML configs replace `<home>` with the home folder's absolute path
+(`echo $HOME`, e.g. `/Users/me` or `C:\\Users\\me`). Never drop the flag or leave `<home>` in place.
+
 | Tool        | Route                           |
 |-------------|---------------------------------|
 | Claude Code | `connect/tools/claude-code.md`  |

package/skills/headless/connect/tools/antigravity.md

@@ -26,11 +26,11 @@ no tokens to handle:
   "mcpServers": {
     "hostinger": {
       "command": "npx",
-      "args": ["-y", "@hostinger/mcp@latest"]
+      "args": ["-y", "--prefix=<home>", "@hostinger/mcp@latest"]
     },
     "hostinger-ecommerce": {
       "command": "npx",
-      "args": ["--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
+      "args": ["--prefix=<home>", "--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
     }
   }
 }

package/skills/headless/connect/tools/claude-code.md

@@ -25,8 +25,8 @@ in, so they reuse the cached sign-in (`~/.config/hostinger-mcp/credentials.json`
 `HOSTINGER_API_TOKEN`) and there are no tokens to handle:
 
 ```bash
-claude mcp add hostinger --scope user -- npx -y @hostinger/mcp@latest                                     # hosting group missing
-claude mcp add hostinger-ecommerce --scope user -- npx --package=@hostinger/mcp@latest hostinger-ecommerce-mcp  # ecommerce group missing
+claude mcp add hostinger --scope user -- npx -y --prefix="$HOME" @hostinger/mcp@latest                                     # hosting group missing
+claude mcp add hostinger-ecommerce --scope user -- npx --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-ecommerce-mcp  # ecommerce group missing
 ```
 
 Claude Code loads MCP servers only at startup, so follow *register, restart, resume* in

package/skills/headless/connect/tools/codex.md

@@ -19,8 +19,8 @@ sign-in (`~/.config/hostinger-mcp/credentials.json`, or `HOSTINGER_API_TOKEN`) a
 to handle:
 
 ```bash
-codex mcp add hostinger -- npx -y @hostinger/mcp@latest
-codex mcp add hostinger-ecommerce -- npx --package=@hostinger/mcp@latest hostinger-ecommerce-mcp
+codex mcp add hostinger -- npx -y --prefix="$HOME" @hostinger/mcp@latest
+codex mcp add hostinger-ecommerce -- npx --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-ecommerce-mcp
 ```
 
 or add them to `~/.codex/config.toml`:
@@ -28,11 +28,11 @@ or add them to `~/.codex/config.toml`:
 ```toml
 [mcp_servers.hostinger]
 command = "npx"
-args = ["-y", "@hostinger/mcp@latest"]
+args = ["-y", "--prefix=<home>", "@hostinger/mcp@latest"]
 
 [mcp_servers.hostinger-ecommerce]
 command = "npx"
-args = ["--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
+args = ["--prefix=<home>", "--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
 ```
 
 Codex loads MCP servers only when it starts, so follow *register, restart, resume* in

package/skills/headless/connect/tools/cursor.md

@@ -19,7 +19,7 @@ The Hostinger MCP is the npm package `@hostinger/mcp`. You do **not** need a glo
 
 ```bash
 # Verify the package/binary is reachable
-npx --yes --package=@hostinger/mcp@latest hostinger-api-mcp --version
+npx --yes --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-api-mcp --version
 ```
 
 ### Option B — global install
@@ -49,11 +49,11 @@ OAuth can run:
   "mcpServers": {
     "hostinger": {
       "command": "npx",
-      "args": ["--yes", "--package=@hostinger/mcp@latest", "hostinger-api-mcp"]
+      "args": ["--yes", "--prefix=<home>", "--package=@hostinger/mcp@latest", "hostinger-api-mcp"]
     },
     "hostinger-ecommerce": {
       "command": "npx",
-      "args": ["--yes", "--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
+      "args": ["--yes", "--prefix=<home>", "--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
     }
   }
 }
@@ -74,7 +74,7 @@ If the connect bootstrap already emitted `logged_in` / `success`, credentials ar
 Otherwise run the login command. It registers a dynamic OAuth client (once per machine), **opens the user's browser** to Hostinger's authorization page, listens on a localhost callback, stores tokens, and exits:
 
 ```bash
-npx --yes --package=@hostinger/mcp@latest hostinger-api-mcp --login
+npx --yes --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-api-mcp --login
 ```
 
 (With a global install: `hostinger-api-mcp --login`.)
@@ -95,7 +95,7 @@ They are shared across every Hostinger MCP binary. Expired access tokens refresh
 To sign out later:
 
 ```bash
-npx --yes --package=@hostinger/mcp@latest hostinger-api-mcp --logout
+npx --yes --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-api-mcp --logout
 ```
 
 **API token (optional, CI / scripts):** set `HOSTINGER_API_TOKEN` in the environment before launching Cursor. When present it always wins and no OAuth code runs. Do not commit the token.

package/skills/headless/connect/tools/devin.md

@@ -21,18 +21,18 @@ tokens to handle.
 - **Devin CLI:**
 
   ```bash
-  devin mcp add hostinger -- npx -y @hostinger/mcp@latest
-  devin mcp add hostinger-ecommerce -- npx --package=@hostinger/mcp@latest hostinger-ecommerce-mcp
+  devin mcp add hostinger -- npx -y --prefix="$HOME" @hostinger/mcp@latest
+  devin mcp add hostinger-ecommerce -- npx --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-ecommerce-mcp
   ```
 
 - **Devin app:** Settings → MCP Marketplace → **Add Your Own**, transport **STDIO**, once per server:
 
   ```json
-  { "command": "npx", "args": ["-y", "@hostinger/mcp@latest"] }
+  { "command": "npx", "args": ["-y", "--prefix=<home>", "@hostinger/mcp@latest"] }
   ```
 
   ```json
-  { "command": "npx", "args": ["--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"] }
+  { "command": "npx", "args": ["--prefix=<home>", "--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"] }
   ```
 
 If the tools still aren't in this session, follow *register, restart, resume* in `connect/SKILL.md`:

package/skills/headless/connect/tools/vscode.md

@@ -26,12 +26,12 @@ no tokens to handle. Add them to `.vscode/mcp.json` (workspace) or your user `se
     "hostinger": {
       "type": "stdio",
       "command": "npx",
-      "args": ["-y", "@hostinger/mcp@latest"]
+      "args": ["-y", "--prefix=<home>", "@hostinger/mcp@latest"]
     },
     "hostinger-ecommerce": {
       "type": "stdio",
       "command": "npx",
-      "args": ["--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
+      "args": ["--prefix=<home>", "--package=@hostinger/mcp@latest", "hostinger-ecommerce-mcp"]
     }
   }
 }
@@ -40,8 +40,8 @@ no tokens to handle. Add them to `.vscode/mcp.json` (workspace) or your user `se
 Or add them in two commands:
 
 ```bash
-code --add-mcp '{"name":"hostinger","command":"npx","args":["-y","@hostinger/mcp@latest"]}'
-code --add-mcp '{"name":"hostinger-ecommerce","command":"npx","args":["--package=@hostinger/mcp@latest","hostinger-ecommerce-mcp"]}'
+code --add-mcp '{"name":"hostinger","command":"npx","args":["-y","--prefix=<home>","@hostinger/mcp@latest"]}'
+code --add-mcp '{"name":"hostinger-ecommerce","command":"npx","args":["--prefix=<home>","--package=@hostinger/mcp@latest","hostinger-ecommerce-mcp"]}'
 ```
 
 VS Code picks up new servers and their tools become available right away, with no editor restart.

package/skills/headless/steps/03-provision/ecommerce/SKILL.md

@@ -22,7 +22,7 @@ Provision a **Hostinger Ecommerce** backend for `<domain>` and prove it is ready
 > 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 -- npx --package=@hostinger/mcp@latest hostinger-ecommerce-mcp
+> claude mcp add hostinger-ecommerce --scope user -- npx --prefix="$HOME" --package=@hostinger/mcp@latest 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

package/skills/headless/steps/08-deploy/SKILL.md

@@ -15,7 +15,7 @@ This is an **instance-barrier** step: run it only after `provision.status == "co
 > **Connected to the hosted server (`mcp.hostinger.com`)?** Its `hosting_deploy` deploys Git
 > repositories only and cannot read a local `path`. Run this step through the local
 > `hostinger-api-mcp` server instead (see the connect step:
-> `npx --yes --package=@hostinger/mcp@latest hostinger-api-mcp`).
+> `npx --yes --prefix="$HOME" --package=@hostinger/mcp@latest hostinger-api-mcp`).
 
 > **With a shell and the Hostinger CLI installed**, the same deploy is one command, with the build
 > settings passed exactly as the table below says. Run it from the project, since it links the current directory: