hostinger-api-mcp 3.10.4 → 3.11.1

package/src/core/tools/all.js

@@ -9,7 +9,7 @@ export default [
       "destructiveHint": true
     },
     "topic": "hosting",
-    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, pass appType and nodeVersion from the project's engines, plus outputDirectory and buildScript if the app has a build step). Git needs GitHub or GitLab connected once in hPanel.",
+    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.",
     "method": "",
     "path": "",
     "inputSchema": {
@@ -38,6 +38,10 @@ export default [
             "directory": {
               "type": "string",
               "description": "Folder under the website's document root to deploy into (static deploys only; default the document root), e.g. my-api"
+            },
+            "installationUuid": {
+              "type": "string",
+              "description": "Git installation that can reach the repository, from hosting_git_list-installations. Only needed when the installation has more than 500 repositories, so the repository cannot be found by listing them."
             }
           },
           "required": [
@@ -76,7 +80,7 @@ export default [
             22,
             24
           ],
-          "description": "Node.js major version (default: detected from an archive, or stored for the site, else 22; set it from the project's engines for a Git deploy)"
+          "description": "Node.js major version (default: detected from an archive, or stored for the site, else detected from the branch's package.json, else 22)"
         },
         "appType": {
           "type": "string",
@@ -87,16 +91,25 @@ export default [
           "description": "Directory with the package.json, relative to the site root (default .)"
         },
         "outputDirectory": {
-          "type": "string",
-          "description": "Build output directory relative to the root directory, e.g. dist"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Build output directory relative to the root directory, e.g. dist. Pass null to clear a stored value."
         },
         "buildScript": {
-          "type": "string",
-          "description": "The package.json script that builds the app, e.g. build"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The package.json script that builds the app, e.g. build. Pass null to clear a stored value."
         },
         "entryFile": {
-          "type": "string",
-          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next."
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next. Pass null to clear a stored value."
         },
         "packageManager": {
           "type": "string",
@@ -8439,7 +8452,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_nodejs_list-environment-variables",

package/src/core/tools/all.ts

@@ -25,7 +25,7 @@ const tools: OpenApiTool[] = [
       "destructiveHint": true
     },
     "topic": "hosting",
-    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, pass appType and nodeVersion from the project's engines, plus outputDirectory and buildScript if the app has a build step). Git needs GitHub or GitLab connected once in hPanel.",
+    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.",
     "method": "",
     "path": "",
     "inputSchema": {
@@ -54,6 +54,10 @@ const tools: OpenApiTool[] = [
             "directory": {
               "type": "string",
               "description": "Folder under the website's document root to deploy into (static deploys only; default the document root), e.g. my-api"
+            },
+            "installationUuid": {
+              "type": "string",
+              "description": "Git installation that can reach the repository, from hosting_git_list-installations. Only needed when the installation has more than 500 repositories, so the repository cannot be found by listing them."
             }
           },
           "required": [
@@ -92,7 +96,7 @@ const tools: OpenApiTool[] = [
             22,
             24
           ],
-          "description": "Node.js major version (default: detected from an archive, or stored for the site, else 22; set it from the project's engines for a Git deploy)"
+          "description": "Node.js major version (default: detected from an archive, or stored for the site, else detected from the branch's package.json, else 22)"
         },
         "appType": {
           "type": "string",
@@ -103,16 +107,25 @@ const tools: OpenApiTool[] = [
           "description": "Directory with the package.json, relative to the site root (default .)"
         },
         "outputDirectory": {
-          "type": "string",
-          "description": "Build output directory relative to the root directory, e.g. dist"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Build output directory relative to the root directory, e.g. dist. Pass null to clear a stored value."
         },
         "buildScript": {
-          "type": "string",
-          "description": "The package.json script that builds the app, e.g. build"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The package.json script that builds the app, e.g. build. Pass null to clear a stored value."
         },
         "entryFile": {
-          "type": "string",
-          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next."
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next. Pass null to clear a stored value."
         },
         "packageManager": {
           "type": "string",
@@ -8455,7 +8468,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_nodejs_list-environment-variables",

package/src/core/tools/hosting.js

@@ -9,7 +9,7 @@ export default [
       "destructiveHint": true
     },
     "topic": "hosting",
-    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, pass appType and nodeVersion from the project's engines, plus outputDirectory and buildScript if the app has a build step). Git needs GitHub or GitLab connected once in hPanel.",
+    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.",
     "method": "",
     "path": "",
     "inputSchema": {
@@ -38,6 +38,10 @@ export default [
             "directory": {
               "type": "string",
               "description": "Folder under the website's document root to deploy into (static deploys only; default the document root), e.g. my-api"
+            },
+            "installationUuid": {
+              "type": "string",
+              "description": "Git installation that can reach the repository, from hosting_git_list-installations. Only needed when the installation has more than 500 repositories, so the repository cannot be found by listing them."
             }
           },
           "required": [
@@ -76,7 +80,7 @@ export default [
             22,
             24
           ],
-          "description": "Node.js major version (default: detected from an archive, or stored for the site, else 22; set it from the project's engines for a Git deploy)"
+          "description": "Node.js major version (default: detected from an archive, or stored for the site, else detected from the branch's package.json, else 22)"
         },
         "appType": {
           "type": "string",
@@ -87,16 +91,25 @@ export default [
           "description": "Directory with the package.json, relative to the site root (default .)"
         },
         "outputDirectory": {
-          "type": "string",
-          "description": "Build output directory relative to the root directory, e.g. dist"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Build output directory relative to the root directory, e.g. dist. Pass null to clear a stored value."
         },
         "buildScript": {
-          "type": "string",
-          "description": "The package.json script that builds the app, e.g. build"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The package.json script that builds the app, e.g. build. Pass null to clear a stored value."
         },
         "entryFile": {
-          "type": "string",
-          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next."
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next. Pass null to clear a stored value."
         },
         "packageManager": {
           "type": "string",
@@ -2749,7 +2762,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_nodejs_list-environment-variables",

package/src/core/tools/hosting.ts

@@ -25,7 +25,7 @@ const tools: OpenApiTool[] = [
       "destructiveHint": true
     },
     "topic": "hosting",
-    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, pass appType and nodeVersion from the project's engines, plus outputDirectory and buildScript if the app has a build step). Git needs GitHub or GitLab connected once in hPanel.",
+    "description": "Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.",
     "method": "",
     "path": "",
     "inputSchema": {
@@ -54,6 +54,10 @@ const tools: OpenApiTool[] = [
             "directory": {
               "type": "string",
               "description": "Folder under the website's document root to deploy into (static deploys only; default the document root), e.g. my-api"
+            },
+            "installationUuid": {
+              "type": "string",
+              "description": "Git installation that can reach the repository, from hosting_git_list-installations. Only needed when the installation has more than 500 repositories, so the repository cannot be found by listing them."
             }
           },
           "required": [
@@ -92,7 +96,7 @@ const tools: OpenApiTool[] = [
             22,
             24
           ],
-          "description": "Node.js major version (default: detected from an archive, or stored for the site, else 22; set it from the project's engines for a Git deploy)"
+          "description": "Node.js major version (default: detected from an archive, or stored for the site, else detected from the branch's package.json, else 22)"
         },
         "appType": {
           "type": "string",
@@ -103,16 +107,25 @@ const tools: OpenApiTool[] = [
           "description": "Directory with the package.json, relative to the site root (default .)"
         },
         "outputDirectory": {
-          "type": "string",
-          "description": "Build output directory relative to the root directory, e.g. dist"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Build output directory relative to the root directory, e.g. dist. Pass null to clear a stored value."
         },
         "buildScript": {
-          "type": "string",
-          "description": "The package.json script that builds the app, e.g. build"
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The package.json script that builds the app, e.g. build. Pass null to clear a stored value."
         },
         "entryFile": {
-          "type": "string",
-          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next."
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next. Pass null to clear a stored value."
         },
         "packageManager": {
           "type": "string",
@@ -2765,7 +2778,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_nodejs_list-environment-variables",

package/src/servers/agency-hosting.js

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 import instructions from '../core/instructions.agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.10.4', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.11.1', tools, instructions });

package/src/servers/agency-hosting.ts

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 import instructions from '../core/instructions.agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.10.4', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.11.1', tools, instructions });

package/src/servers/agent-readiness.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agent-readiness.js';
 
-startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.11.1', tools });

package/src/servers/agent-readiness.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agent-readiness.js';
 
-startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.11.1', tools });

package/src/servers/all.js

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '3.10.4', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '3.11.1', tools, instructions, skills });

package/src/servers/all.ts

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '3.10.4', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '3.11.1', tools, instructions, skills });

package/src/servers/billing.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '3.11.1', tools });

package/src/servers/billing.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '3.11.1', tools });

package/src/servers/dns.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '3.11.1', tools });

package/src/servers/dns.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '3.11.1', tools });

package/src/servers/domains.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '3.11.1', tools });

package/src/servers/domains.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '3.11.1', tools });

package/src/servers/ecommerce.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '3.11.1', tools });

package/src/servers/ecommerce.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '3.11.1', tools });

package/src/servers/horizons.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '3.11.1', tools });

package/src/servers/horizons.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '3.11.1', tools });

package/src/servers/hosting.js

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '3.10.4', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '3.11.1', tools, instructions });

package/src/servers/hosting.ts

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '3.10.4', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '3.11.1', tools, instructions });

package/src/servers/mail.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '3.11.1', tools });

package/src/servers/mail.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '3.11.1', tools });

package/src/servers/reach.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.11.1', tools });

package/src/servers/reach.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.11.1', tools });

package/src/servers/vps.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.11.1', tools });

package/src/servers/vps.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.11.1', tools });

package/src/servers/wordpress.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.11.1', tools });

package/src/servers/wordpress.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '3.10.4', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.11.1', tools });

package/types.d.ts

@@ -5,7 +5,7 @@
 
 export interface APITools {
   /**
-   * Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, pass appType and nodeVersion from the project's engines, plus outputDirectory and buildScript if the app has a build step). Git needs GitHub or GitLab connected once in hPanel.
+   * Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.
    */
   "hosting_deploy": {
     params: {
@@ -38,7 +38,7 @@ export interface APITools {
        */
       databaseDump?: string;
       /**
-       * Node.js major version (default: detected from an archive, or stored for the site, else 22; set it from the project's engines for a Git deploy)
+       * Node.js major version (default: detected from an archive, or stored for the site, else detected from the branch's package.json, else 22)
        */
       nodeVersion?: number;
       /**
@@ -50,17 +50,17 @@ export interface APITools {
        */
       rootDirectory?: string;
       /**
-       * Build output directory relative to the root directory, e.g. dist
+       * Build output directory relative to the root directory, e.g. dist. Pass null to clear a stored value.
        */
-      outputDirectory?: string;
+      outputDirectory?: string | null;
       /**
-       * The package.json script that builds the app, e.g. build
+       * The package.json script that builds the app, e.g. build. Pass null to clear a stored value.
        */
-      buildScript?: string;
+      buildScript?: string | null;
       /**
-       * Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next.
+       * Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next. Pass null to clear a stored value.
        */
-      entryFile?: string;
+      entryFile?: string | null;
       /**
        * Package manager used to install dependencies
        */