@hostinger/mcp 3.37.1 → 3.38.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (63) hide show
  1. package/CHANGELOG.md +34 -0
  2. package/README.md +1 -1
  3. package/gemini-extension.json +1 -1
  4. package/package.json +1 -1
  5. package/server.json +2 -2
  6. package/skills/deploy-to-hosting/SKILL.md +1 -1
  7. package/skills/headless/VERSION +3 -3
  8. package/skills/headless/steps/04-content-model/SKILL.md +22 -14
  9. package/src/core/catalog.js +9 -1
  10. package/src/core/catalog.ts +11 -2
  11. package/src/core/instructions.agency-hosting.js +1 -1
  12. package/src/core/instructions.agency-hosting.ts +1 -1
  13. package/src/core/instructions.js +1 -1
  14. package/src/core/instructions.ts +1 -1
  15. package/src/core/runtime.js +2 -1483
  16. package/src/core/runtime.ts +4 -1483
  17. package/src/core/skills.js +6 -6
  18. package/src/core/skills.ts +6 -6
  19. package/src/core/tools/agency-hosting.ts +2 -0
  20. package/src/core/tools/agent-readiness.ts +2 -0
  21. package/src/core/tools/all.js +72 -330
  22. package/src/core/tools/all.ts +74 -330
  23. package/src/core/tools/billing.ts +2 -0
  24. package/src/core/tools/dns.ts +2 -0
  25. package/src/core/tools/domains.ts +2 -0
  26. package/src/core/tools/ecommerce.ts +2 -0
  27. package/src/core/tools/gpu.ts +2 -0
  28. package/src/core/tools/horizons.ts +2 -0
  29. package/src/core/tools/hosting.js +63 -327
  30. package/src/core/tools/hosting.ts +65 -327
  31. package/src/core/tools/mail.ts +2 -0
  32. package/src/core/tools/reach.ts +2 -0
  33. package/src/core/tools/vps.ts +2 -0
  34. package/src/core/tools/wordpress.ts +2 -0
  35. package/src/servers/agency-hosting.js +1 -1
  36. package/src/servers/agency-hosting.ts +1 -1
  37. package/src/servers/agent-readiness.js +1 -1
  38. package/src/servers/agent-readiness.ts +1 -1
  39. package/src/servers/all.js +1 -1
  40. package/src/servers/all.ts +1 -1
  41. package/src/servers/billing.js +1 -1
  42. package/src/servers/billing.ts +1 -1
  43. package/src/servers/dns.js +1 -1
  44. package/src/servers/dns.ts +1 -1
  45. package/src/servers/domains.js +1 -1
  46. package/src/servers/domains.ts +1 -1
  47. package/src/servers/ecommerce.js +1 -1
  48. package/src/servers/ecommerce.ts +1 -1
  49. package/src/servers/gpu.js +1 -1
  50. package/src/servers/gpu.ts +1 -1
  51. package/src/servers/horizons.js +1 -1
  52. package/src/servers/horizons.ts +1 -1
  53. package/src/servers/hosting.js +1 -1
  54. package/src/servers/hosting.ts +1 -1
  55. package/src/servers/mail.js +1 -1
  56. package/src/servers/mail.ts +1 -1
  57. package/src/servers/reach.js +1 -1
  58. package/src/servers/reach.ts +1 -1
  59. package/src/servers/vps.js +1 -1
  60. package/src/servers/vps.ts +1 -1
  61. package/src/servers/wordpress.js +1 -1
  62. package/src/servers/wordpress.ts +1 -1
  63. package/types.d.ts +0 -155
package/CHANGELOG.md CHANGED
@@ -4,6 +4,40 @@ Generated at release time from the diff between the previous and current
4
4
  build. Tool changes are listed individually; everything else is summarised
5
5
  by area.
6
6
 
7
+ ## v3.38.1 — 2026-11-11
8
+
9
+ ### Also in this release
10
+
11
+ - Dependencies: `package-lock.json`
12
+ - Bundled agent skills: `skills/headless/VERSION`, `skills/headless/steps/04-content-model/SKILL.md`
13
+ - Other files: `src/core/skills.js`, `src/core/skills.ts`
14
+
15
+ ## v3.38.0 — 2026-11-11
16
+
17
+ ### Operations
18
+
19
+ - Removed `hosting_import-wordpress-website`
20
+ - Removed `hosting_deploy-wordpress-plugin`
21
+ - Removed `hosting_deploy-wordpress-theme`
22
+ - Removed `hosting_deploy-js-application`
23
+ - Removed `hosting_deploy-static-website`
24
+ - Removed `hosting_list-js-deployments`
25
+ - Removed `hosting_show-js-deployment-logs`
26
+ - `execute` no longer runs 2 operations that `hosting_cache_clear` replaced: `hosting_cache_clear-website`, `hosting_cdn_purge-cache`
27
+ - `execute` no longer runs 3 operations that `hosting_websites_get-settings` replaced: `hosting_cache_status`, `hosting_cdn_status`, `hosting_ssl_status`
28
+ - `execute` no longer runs 5 operations that `hosting_websites_update-settings` replaced: `hosting_cache_toggle-cacheless`, `hosting_cache_toggle-website`, `hosting_cdn_disable`, `hosting_cdn_enable`, `hosting_ssl_toggle-https-redirect`
29
+ - `execute` no longer runs 6 operations that `hosting_get-deployment` replaced: `hosting_git_auto-deployment-settings`, `hosting_nodejs_list-builds`, `hosting_nodejs_build-settings`, `hosting_nodejs_analyse-failed-build`, `hosting_nodejs_build`, `hosting_nodejs_build-logs`
30
+ - `execute` no longer runs 8 operations that `hosting_deploy` replaced: `hosting_nodejs_start-build`, `hosting_nodejs_update-build-settings`, `hosting_nodejs_build-settings-from-archive`, `hosting_nodejs_build-settings-from-repository`, `hosting_websites_deploy-static-site-archive`, `wordpress_installations_import-website`, `wordpress_plugins_deploy`, `wordpress_themes_deploy`
31
+
32
+ ### Also in this release
33
+
34
+ - Documentation: `README.md`
35
+ - Bundled agent skills: `skills/deploy-to-hosting/SKILL.md`, `skills/headless/VERSION`
36
+ - Request handling and authentication: 4 files
37
+ - Server instructions: 4 files
38
+ - Other files: `src/core/skills.js`, `src/core/skills.ts`
39
+ - Build and packaging: `types.d.ts`
40
+
7
41
  ## v3.37.1 — 2026-11-10
8
42
 
9
43
  ### Operations
package/README.md CHANGED
@@ -244,7 +244,7 @@ Every server exposes three tools:
244
244
 
245
245
  The operations `search` offers, by binary:
246
246
 
247
- Operations that newer tools replace are hidden from `search`, and not documented, in every binary that also offers the replacing tool. They keep working through `execute` until they are removed.
247
+ Operations that newer tools replace are hidden from `search`, and not documented, in every binary that also offers the replacing tool. Some keep working through `execute` until they are removed. Others only run inside the tool that replaced them: `execute` refuses them and names that tool.
248
248
 
249
249
  ### `hostinger-agency-hosting-mcp`
250
250
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hostinger-api-mcp",
3
- "version": "3.37.1",
3
+ "version": "3.38.1",
4
4
  "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
5
5
  "mcpServers": {
6
6
  "hostinger": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hostinger/mcp",
3
- "version": "3.37.1",
3
+ "version": "3.38.1",
4
4
  "mcpName": "io.github.hostinger/hostinger-api-mcp",
5
5
  "description": "MCP server for Hostinger API",
6
6
  "repository": {
package/server.json CHANGED
@@ -17,12 +17,12 @@
17
17
  "url": "https://github.com/hostinger/api-mcp-server",
18
18
  "source": "github"
19
19
  },
20
- "version": "3.37.1",
20
+ "version": "3.38.1",
21
21
  "packages": [
22
22
  {
23
23
  "registryType": "npm",
24
24
  "identifier": "@hostinger/mcp",
25
- "version": "3.37.1",
25
+ "version": "3.38.1",
26
26
  "transport": {
27
27
  "type": "stdio"
28
28
  },
@@ -112,7 +112,7 @@ Agency Plan sites have no Git operations; deploy archives.
112
112
 
113
113
  1. `hosting_nodejs_list-environment-variables` for the current keys. Values come back as `********`; never send those back.
114
114
  2. Build the full set: every current key plus the new ones, with real values from the project's `.env` or the user. When the real value of an existing key is unknown, ask — do not drop it.
115
- 3. Send it once; the app restarts. Values baked in at build time (Next.js `NEXT_PUBLIC_*`, Vite `VITE_*`) need a new `hosting_nodejs_start-build`.
115
+ 3. Send it once; the app restarts. Values baked in at build time (Next.js `NEXT_PUBLIC_*`, Vite `VITE_*`) need a new build: deploy again with `hosting_deploy`; for local files uploaded to the hosted server, run `hosting_nodejs_start-build` again as in step 2.
116
116
 
117
117
  Keys use uppercase letters, digits and underscores. Never commit `.env` files or repeat secret values back to the user.
118
118
 
@@ -1,3 +1,3 @@
1
- version=3.37.1
2
- commit=bad30f9d4ff6
3
- built=2026-11-10
1
+ version=3.38.1
2
+ commit=0c534731bebc
3
+ built=2026-11-11
@@ -170,30 +170,38 @@ Source every image in a few batched calls, not a search and a fetch per photo:
170
170
  "sourdough bread", "bakery interior", "Lisbon street").
171
171
  - With an `UNSPLASH_ACCESS_KEY` in the environment, use the official API, one call per theme:
172
172
  `GET https://api.unsplash.com/search/photos?query=<theme>&orientation=landscape&per_page=20` with
173
- header `Authorization: Client-ID <key>`. Each result's `urls.raw` is the file, `alt_description`
174
- what it shows and `user.name` the photographer; for each photo you keep, also `GET` its
173
+ header `Authorization: Client-ID <key>`. Each result's `urls.raw` is the file (its `photo-…`
174
+ part, before `?`, is the `<file id>`), `id` the `<page id>`, `alt_description` what it shows and
175
+ `user.name` the photographer; for each photo you keep, also `GET` its
175
176
  `links.download_location` (same header), as the API terms require.
176
177
  - Without a key, open the theme's search page `https://unsplash.com/s/photos/<theme-with-dashes>`
177
- with your **web-fetch tool**, once per theme, and ask it to list every free photo on the page with
178
- its `images.unsplash.com/photo-<…>` URL quoted exactly (the part before `?`), the photo page
179
- link, the alt text and the photographer. One fetch returns 10–20 candidates. Skip the
180
- `plus.unsplash.com/premium_photo-…` results: they are Unsplash+ and not free. Fetch the themes in
181
- parallel when your tool allows several calls at once. Fall back to a web search limited to
182
- `unsplash.com` plus a fetch of one photo page (`https://unsplash.com/photos/<…>`) only for a
183
- subject no search page covers.
178
+ with your **web-fetch tool**, once per theme, with this prompt (a short fixed answer keeps the
179
+ fetch fast):
180
+
181
+ ```text
182
+ List up to 12 free photos on this page, one line each, in this exact format and nothing else:
183
+ <file id> | <page id> | <alt text> | <photographer>
184
+ <file id> is the photo-… part of its images.unsplash.com URL, copied exactly, before any "?".
185
+ <page id> is the part after unsplash.com/photos/ in its photo page link.
186
+ Skip plus.unsplash.com/premium_photo-… results: they are Unsplash+ and not free.
187
+ ```
188
+
189
+ Fetch the themes in parallel when your tool allows several calls at once. Fall back to a web
190
+ search limited to `unsplash.com` plus a fetch of one photo page (`https://unsplash.com/photos/<…>`)
191
+ only for a subject no search page covers.
184
192
  - Every other `unsplash.com` request (curl on any page, `/photos/<id>/download`, `/napi/…`,
185
193
  `/oembed`) hits a bot challenge: a `307` to `/.within.website` (Anubis) or a 401. If your fetch
186
194
  tool gets the challenge page too, stop: no user-agent spoofing or other workarounds. On a
187
195
  WordPress backend where Option A hasn't already failed, offer it; otherwise ask the user for an
188
196
  `UNSPLASH_ACCESS_KEY` or record the gap (step 5).
189
- 2. **Check them all in one command.** Pick a candidate per image brief from the alt text, then in one
197
+ 2. **Check them all in one command.** Pick a candidate per image brief from its alt text, then in one
190
198
  shell command request each web-size URL
191
- (`https://images.unsplash.com/photo-<…>?w=1600&q=80&fm=jpg&fit=max`, query string replaced) and
199
+ (`https://images.unsplash.com/<file id>?w=1600&q=80&fm=jpg&fit=max`, query string replaced) and
192
200
  confirm 200 `image/jpeg`, and save a small preview (`?w=500`) of each into one folder, e.g.:
193
201
 
194
202
  ```bash
195
203
  mkdir -p ~/.hostinger/<domain>/media/previews && cd ~/.hostinger/<domain>/media/previews && \
196
- for id in photo-<a> photo-<b>; do
204
+ for id in <file id> <file id>; do
197
205
  curl -s -o /dev/null -w "$id %{http_code} %{content_type}\n" "https://images.unsplash.com/$id?w=1600&q=80&fm=jpg&fit=max"
198
206
  curl -s -o "$id.jpg" "https://images.unsplash.com/$id?w=500&q=60&fm=jpg&fit=max"
199
207
  done
@@ -211,8 +219,8 @@ Source every image in a few batched calls, not a search and a fetch per photo:
211
219
  `content.json` instead: `url`, `alt`, `filename`, and the credit as `caption`):
212
220
 
213
221
  ```markdown
214
- Image: https://images.unsplash.com/photo-<…>?w=1600&q=80&fm=jpg&fit=max
215
- Image credit: <Photographer> — https://unsplash.com/photos/<id> (Unsplash License)
222
+ Image: https://images.unsplash.com/<file id>?w=1600&q=80&fm=jpg&fit=max
223
+ Image credit: <Photographer> — https://unsplash.com/photos/<page id> (Unsplash License)
216
224
  Image alt: <what the photo shows>
217
225
  Image file: <site>-<subject>.jpg
218
226
  ```
@@ -3,7 +3,9 @@
3
3
  // runtime supplies the catalog and the function that performs a call.
4
4
  // Keep in sync with catalog.ts and with api-remote-mcp's PHP implementation.
5
5
  // Both servers honour `hidden`: search skips the entry, execute and multi-execute still run
6
- // it. Each server has its own list (generators.mcp.hiddenFile and generators.remote-mcp.hiddenFile).
6
+ // it. They also honour `internal` (always hidden too): execute and multi-execute refuse the entry,
7
+ // naming its `replacedBy`, while the tool that replaced it still calls it. Each server has its own
8
+ // lists (generators.mcp.hiddenFile and generators.remote-mcp.hiddenFile).
7
9
 
8
10
  export const DEFAULT_SEARCH_LIMIT = 5;
9
11
  export const MAX_SEARCH_LIMIT = 20;
@@ -130,6 +132,12 @@ export function findOperation(operations, name, params) {
130
132
  if (typeof name !== 'string' || !operations.has(name)) {
131
133
  throw new ToolInputError(`Unknown operation "${name}". Use search to find operations.`);
132
134
  }
135
+ const replaced = operations.get(name);
136
+ if (replaced.internal === true) {
137
+ throw new ToolInputError(replaced.replacedBy
138
+ ? `Operation ${name} was replaced by ${replaced.replacedBy} and can no longer be run directly. Use ${replaced.replacedBy} instead.`
139
+ : `Operation ${name} can no longer be run directly. Use search to find its replacement.`);
140
+ }
133
141
  if (params === null || typeof params !== 'object' || Array.isArray(params)) {
134
142
  throw new ToolInputError('params must be an object');
135
143
  }
@@ -1,7 +1,9 @@
1
1
  // Typed mirror of catalog.js. Keep both files, and api-remote-mcp's PHP
2
2
  // implementation, behaviourally identical. Both servers honour `hidden`: search skips the
3
- // entry, execute and multi-execute still run it. Each server has its own list
4
- // (the files generators.mcp.hiddenFile and generators.remote-mcp.hiddenFile point to).
3
+ // entry, execute and multi-execute still run it. They also honour `internal` (always hidden
4
+ // too): execute and multi-execute refuse the entry, naming its `replacedBy`, while the tool that
5
+ // replaced it still calls it. Each server has its own lists (the files generators.mcp.hiddenFile
6
+ // and generators.remote-mcp.hiddenFile point to).
5
7
 
6
8
  export const DEFAULT_SEARCH_LIMIT = 5;
7
9
  export const MAX_SEARCH_LIMIT = 20;
@@ -15,6 +17,8 @@ export interface CatalogOperation {
15
17
  description?: string;
16
18
  group?: string;
17
19
  hidden?: boolean;
20
+ internal?: boolean;
21
+ replacedBy?: string;
18
22
  annotations?: { readOnlyHint?: boolean; destructiveHint?: boolean; [key: string]: unknown };
19
23
  inputSchema: { type: 'object'; properties?: Record<string, unknown>; required?: string[]; [key: string]: unknown };
20
24
  }
@@ -151,6 +155,11 @@ export function findOperation<T extends CatalogOperation>(operations: Map<string
151
155
  if (!op) {
152
156
  throw new ToolInputError(`Unknown operation "${String(name)}". Use search to find operations.`);
153
157
  }
158
+ if (op.internal === true) {
159
+ throw new ToolInputError(op.replacedBy
160
+ ? `Operation ${op.name} was replaced by ${op.replacedBy} and can no longer be run directly. Use ${op.replacedBy} instead.`
161
+ : `Operation ${op.name} can no longer be run directly. Use search to find its replacement.`);
162
+ }
154
163
  if (params === null || typeof params !== 'object' || Array.isArray(params)) {
155
164
  throw new ToolInputError('params must be an object');
156
165
  }
@@ -1,2 +1,2 @@
1
1
  // Auto-generated server instructions
2
- export default "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or hosting_nodejs_start-build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ export default "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
@@ -1,3 +1,3 @@
1
1
  // Auto-generated server instructions
2
- const instructions: string = "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or hosting_nodejs_start-build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ const instructions: string = "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
3
3
  export default instructions;
@@ -1,2 +1,2 @@
1
1
  // Auto-generated server instructions
2
- export default "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or hosting_nodejs_start-build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nDeploying a website (this server only)\n- hosting_deploy replaces the upload, archive-deploy, build, WordPress import/plugin/theme and Git operations named above. Give it a local directory (it detects static/PHP, Node.js, a WordPress site, plugin or theme and packs it itself), a local archive with `type`, or `git: { repository, branch }`. Do not run those operations by hand.\n- A Node.js deploy returns a buildUuid at once and builds on the server. Poll hosting_get-deployment with the domain, pausing longer each time, until the build state is completed or failed. A failed build comes back with its logs and analysis: fix the cause and deploy again. It replaces the build, log and settings operations.\n- Static, PHP, plugin and theme deploys are complete when hosting_deploy returns. A WordPress site import only starts: its files are extracted and the site is ready a few minutes later.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ export default "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nDeploying a website (this server only)\n- hosting_deploy replaces the upload, archive-deploy, build, WordPress import/plugin/theme and Git operations named above. Give it a local directory (it detects static/PHP, Node.js, a WordPress site, plugin or theme and packs it itself), a local archive with `type`, or `git: { repository, branch }`. Do not run those operations by hand.\n- A Node.js deploy returns a buildUuid at once and builds on the server. Poll hosting_get-deployment with the domain, pausing longer each time, until the build state is completed or failed. A failed build comes back with its logs and analysis: fix the cause and deploy again. It replaces the build, log and settings operations.\n- Static, PHP, plugin and theme deploys are complete when hosting_deploy returns. A WordPress site import only starts: its files are extracted and the site is ready a few minutes later.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
@@ -1,3 +1,3 @@
1
1
  // Auto-generated server instructions
2
- const instructions: string = "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or hosting_nodejs_start-build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nDeploying a website (this server only)\n- hosting_deploy replaces the upload, archive-deploy, build, WordPress import/plugin/theme and Git operations named above. Give it a local directory (it detects static/PHP, Node.js, a WordPress site, plugin or theme and packs it itself), a local archive with `type`, or `git: { repository, branch }`. Do not run those operations by hand.\n- A Node.js deploy returns a buildUuid at once and builds on the server. Poll hosting_get-deployment with the domain, pausing longer each time, until the build state is completed or failed. A failed build comes back with its logs and analysis: fix the cause and deploy again. It replaces the build, log and settings operations.\n- Static, PHP, plugin and theme deploys are complete when hosting_deploy returns. A WordPress site import only starts: its files are extracted and the site is ready a few minutes later.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ const instructions: string = "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.\n- A Node.js deploy or build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- The Hostinger CLI deploys a website in one command and links the directory: `hostinger up <dir> --domain <domain> --format json` (`--yes` replaces content, `--create` makes a site, `--dry-run` shows the plan). It never prompts without a terminal.\n\nDeploying a website (this server only)\n- hosting_deploy replaces the upload, archive-deploy, build, WordPress import/plugin/theme and Git operations named above. Give it a local directory (it detects static/PHP, Node.js, a WordPress site, plugin or theme and packs it itself), a local archive with `type`, or `git: { repository, branch }`. Do not run those operations by hand.\n- A Node.js deploy returns a buildUuid at once and builds on the server. Poll hosting_get-deployment with the domain, pausing longer each time, until the build state is completed or failed. A failed build comes back with its logs and analysis: fix the cause and deploy again. It replaces the build, log and settings operations.\n- Static, PHP, plugin and theme deploys are complete when hosting_deploy returns. A WordPress site import only starts: its files are extracted and the site is ready a few minutes later.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by `product` and `since`. For what is coming (the roadmap), call it with `status: upcoming`. It needs no API token.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
3
3
  export default instructions;