hostinger-api-mcp 1.45.0 → 1.45.2

package/README.md

@@ -69,14 +69,14 @@ pnpm update -g hostinger-api-mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (351 total)
+- `hostinger-api-mcp` — unified server with every tool (350 total)
 - `hostinger-agency-hosting-mcp` — 38 tools for agency-hosting
 - `hostinger-billing-mcp` — 9 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
 - `hostinger-domains-mcp` — 40 tools for domains
 - `hostinger-ecommerce-mcp` — 14 tools for ecommerce
 - `hostinger-horizons-mcp` — 2 tools for horizons
-- `hostinger-hosting-mcp` — 57 tools for hosting
+- `hostinger-hosting-mcp` — 56 tools for hosting
 - `hostinger-mail-mcp` — 38 tools for mail
 - `hostinger-reach-mcp` — 45 tools for reach
 - `hostinger-vps-mcp` — 62 tools for vps
@@ -1841,35 +1841,6 @@ the `Get Node.js Build Logs` endpoint.
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds`
 
-#### hosting_createNodeJSBuildFromArchiveV1
-
-Upload a project archive, auto-detect build settings, and immediately start a Node.js build.
-
-WARNING: on success this overwrites the website's existing contents and cannot be
-undone — verify this is intended before calling this endpoint.
-
-This is the recommended single-step approach for deploying a Node.js application.
-The archive is uploaded to the website's file storage, build settings are auto-detected
-from the package.json inside the archive, and the build process starts automatically.
-Optional override fields take precedence over auto-detected values.
-Maximum archive size is 50MB.
-
-Before archiving, exclude `node_modules/` and any build output directories
-(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build
-process runs the install step automatically, and including them unnecessarily
-increases the archive size. This also helps keep the archive well under the 50MB limit.
-
-Example (zip):
-```
-zip -r archive.zip . --exclude "node_modules/*" --exclude "dist/*"
-```
-
-The returned build `uuid` can be used to poll progress and retrieve logs via
-the `Get Node.js Build Logs` endpoint.
-
-- **Method**: `POST`
-- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive`
-
 #### hosting_getNode_jsBuildSettingsFromArchiveV1
 
 Auto-detect Node.js build settings from a package.json inside an archive already on the server.

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.45.0",
+  "version": "1.45.2",
   "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": "1.45.0",
+  "version": "1.45.2",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {

package/server.json

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

package/src/core/runtime.js

@@ -29,7 +29,7 @@ const SECURITY_SCHEMES = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.42.0
+ * Generated from OpenAPI spec version 1.42.2
  */
 class MCPServer {
   constructor({ name, version, tools }) {

package/src/core/runtime.ts

@@ -52,7 +52,7 @@ const SECURITY_SCHEMES: Record<string, SecurityScheme> = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.42.0
+ * Generated from OpenAPI spec version 1.42.2
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -4928,100 +4928,6 @@ export default [
     ],
     "group": "hosting"
   },
-  {
-    "name": "hosting_createNodeJSBuildFromArchiveV1",
-    "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
-    "method": "POST",
-    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
-    "inputSchema": {
-      "type": "object",
-      "properties": {
-        "username": {
-          "type": "string",
-          "description": "username parameter"
-        },
-        "domain": {
-          "type": "string",
-          "description": "Domain name"
-        },
-        "archive": {
-          "type": "string",
-          "description": "Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB"
-        },
-        "node_version": {
-          "type": "integer",
-          "description": "Node.js version override (auto-detected from package.json if omitted)",
-          "enum": [
-            18,
-            20,
-            22,
-            24
-          ]
-        },
-        "app_type": {
-          "type": "string",
-          "description": "Node.js application type override",
-          "enum": [
-            "create-react-app",
-            "gatsby",
-            "vite",
-            "angular",
-            "react",
-            "vue",
-            "parcel",
-            "next",
-            "nuxt",
-            "nest",
-            "express",
-            "fastify",
-            "astro",
-            "svelte",
-            "svelte-kit",
-            "hono",
-            "react-router",
-            "nitro",
-            "other"
-          ]
-        },
-        "root_directory": {
-          "type": "string",
-          "description": "Application root directory override (where package.json is located) relative to public_html"
-        },
-        "output_directory": {
-          "type": "string",
-          "description": "Build output directory override relative to the root directory"
-        },
-        "build_script": {
-          "type": "string",
-          "description": "Build script override"
-        },
-        "entry_file": {
-          "type": "string",
-          "description": "Main entry point file override"
-        },
-        "package_manager": {
-          "type": "string",
-          "description": "Package manager override",
-          "enum": [
-            "npm",
-            "yarn",
-            "pnpm"
-          ]
-        }
-      },
-      "required": [
-        "username",
-        "domain",
-        "archive"
-      ]
-    },
-    "security": [
-      {
-        "apiToken": []
-      }
-    ],
-    "group": "hosting"
-  },
   {
     "name": "hosting_getNode_jsBuildSettingsFromArchiveV1",
     "description": "Auto-detect Node.js build settings from a package.json inside an archive already on the server.\n\nUse this before calling `Start Node.js Build` to preview what settings will be used,\nor to let the user review and override values (framework, node version, root directory,\noutput directory, build script) before committing to a build.\n\nThe archive must already be present on the website's file storage. Use the\n`Generate Upload URL` endpoint to obtain credentials and upload the archive first.\nTo upload an archive and start a build in one step without inspecting settings first,\nuse the `Create Node.js Build from Archive` endpoint instead.",

package/src/core/tools/all.ts

@@ -4942,100 +4942,6 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
-  {
-    "name": "hosting_createNodeJSBuildFromArchiveV1",
-    "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
-    "method": "POST",
-    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
-    "inputSchema": {
-      "type": "object",
-      "properties": {
-        "username": {
-          "type": "string",
-          "description": "username parameter"
-        },
-        "domain": {
-          "type": "string",
-          "description": "Domain name"
-        },
-        "archive": {
-          "type": "string",
-          "description": "Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB"
-        },
-        "node_version": {
-          "type": "integer",
-          "description": "Node.js version override (auto-detected from package.json if omitted)",
-          "enum": [
-            18,
-            20,
-            22,
-            24
-          ]
-        },
-        "app_type": {
-          "type": "string",
-          "description": "Node.js application type override",
-          "enum": [
-            "create-react-app",
-            "gatsby",
-            "vite",
-            "angular",
-            "react",
-            "vue",
-            "parcel",
-            "next",
-            "nuxt",
-            "nest",
-            "express",
-            "fastify",
-            "astro",
-            "svelte",
-            "svelte-kit",
-            "hono",
-            "react-router",
-            "nitro",
-            "other"
-          ]
-        },
-        "root_directory": {
-          "type": "string",
-          "description": "Application root directory override (where package.json is located) relative to public_html"
-        },
-        "output_directory": {
-          "type": "string",
-          "description": "Build output directory override relative to the root directory"
-        },
-        "build_script": {
-          "type": "string",
-          "description": "Build script override"
-        },
-        "entry_file": {
-          "type": "string",
-          "description": "Main entry point file override"
-        },
-        "package_manager": {
-          "type": "string",
-          "description": "Package manager override",
-          "enum": [
-            "npm",
-            "yarn",
-            "pnpm"
-          ]
-        }
-      },
-      "required": [
-        "username",
-        "domain",
-        "archive"
-      ]
-    },
-    "security": [
-      {
-        "apiToken": []
-      }
-    ],
-    "group": "hosting"
-  },
   {
     "name": "hosting_getNode_jsBuildSettingsFromArchiveV1",
     "description": "Auto-detect Node.js build settings from a package.json inside an archive already on the server.\n\nUse this before calling `Start Node.js Build` to preview what settings will be used,\nor to let the user review and override values (framework, node version, root directory,\noutput directory, build script) before committing to a build.\n\nThe archive must already be present on the website's file storage. Use the\n`Generate Upload URL` endpoint to obtain credentials and upload the archive first.\nTo upload an archive and start a build in one step without inspecting settings first,\nuse the `Create Node.js Build from Archive` endpoint instead.",

package/src/core/tools/hosting.js

@@ -1340,100 +1340,6 @@ export default [
     ],
     "group": "hosting"
   },
-  {
-    "name": "hosting_createNodeJSBuildFromArchiveV1",
-    "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
-    "method": "POST",
-    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
-    "inputSchema": {
-      "type": "object",
-      "properties": {
-        "username": {
-          "type": "string",
-          "description": "username parameter"
-        },
-        "domain": {
-          "type": "string",
-          "description": "Domain name"
-        },
-        "archive": {
-          "type": "string",
-          "description": "Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB"
-        },
-        "node_version": {
-          "type": "integer",
-          "description": "Node.js version override (auto-detected from package.json if omitted)",
-          "enum": [
-            18,
-            20,
-            22,
-            24
-          ]
-        },
-        "app_type": {
-          "type": "string",
-          "description": "Node.js application type override",
-          "enum": [
-            "create-react-app",
-            "gatsby",
-            "vite",
-            "angular",
-            "react",
-            "vue",
-            "parcel",
-            "next",
-            "nuxt",
-            "nest",
-            "express",
-            "fastify",
-            "astro",
-            "svelte",
-            "svelte-kit",
-            "hono",
-            "react-router",
-            "nitro",
-            "other"
-          ]
-        },
-        "root_directory": {
-          "type": "string",
-          "description": "Application root directory override (where package.json is located) relative to public_html"
-        },
-        "output_directory": {
-          "type": "string",
-          "description": "Build output directory override relative to the root directory"
-        },
-        "build_script": {
-          "type": "string",
-          "description": "Build script override"
-        },
-        "entry_file": {
-          "type": "string",
-          "description": "Main entry point file override"
-        },
-        "package_manager": {
-          "type": "string",
-          "description": "Package manager override",
-          "enum": [
-            "npm",
-            "yarn",
-            "pnpm"
-          ]
-        }
-      },
-      "required": [
-        "username",
-        "domain",
-        "archive"
-      ]
-    },
-    "security": [
-      {
-        "apiToken": []
-      }
-    ],
-    "group": "hosting"
-  },
   {
     "name": "hosting_getNode_jsBuildSettingsFromArchiveV1",
     "description": "Auto-detect Node.js build settings from a package.json inside an archive already on the server.\n\nUse this before calling `Start Node.js Build` to preview what settings will be used,\nor to let the user review and override values (framework, node version, root directory,\noutput directory, build script) before committing to a build.\n\nThe archive must already be present on the website's file storage. Use the\n`Generate Upload URL` endpoint to obtain credentials and upload the archive first.\nTo upload an archive and start a build in one step without inspecting settings first,\nuse the `Create Node.js Build from Archive` endpoint instead.",

package/src/core/tools/hosting.ts

@@ -1354,100 +1354,6 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
-  {
-    "name": "hosting_createNodeJSBuildFromArchiveV1",
-    "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
-    "method": "POST",
-    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
-    "inputSchema": {
-      "type": "object",
-      "properties": {
-        "username": {
-          "type": "string",
-          "description": "username parameter"
-        },
-        "domain": {
-          "type": "string",
-          "description": "Domain name"
-        },
-        "archive": {
-          "type": "string",
-          "description": "Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB"
-        },
-        "node_version": {
-          "type": "integer",
-          "description": "Node.js version override (auto-detected from package.json if omitted)",
-          "enum": [
-            18,
-            20,
-            22,
-            24
-          ]
-        },
-        "app_type": {
-          "type": "string",
-          "description": "Node.js application type override",
-          "enum": [
-            "create-react-app",
-            "gatsby",
-            "vite",
-            "angular",
-            "react",
-            "vue",
-            "parcel",
-            "next",
-            "nuxt",
-            "nest",
-            "express",
-            "fastify",
-            "astro",
-            "svelte",
-            "svelte-kit",
-            "hono",
-            "react-router",
-            "nitro",
-            "other"
-          ]
-        },
-        "root_directory": {
-          "type": "string",
-          "description": "Application root directory override (where package.json is located) relative to public_html"
-        },
-        "output_directory": {
-          "type": "string",
-          "description": "Build output directory override relative to the root directory"
-        },
-        "build_script": {
-          "type": "string",
-          "description": "Build script override"
-        },
-        "entry_file": {
-          "type": "string",
-          "description": "Main entry point file override"
-        },
-        "package_manager": {
-          "type": "string",
-          "description": "Package manager override",
-          "enum": [
-            "npm",
-            "yarn",
-            "pnpm"
-          ]
-        }
-      },
-      "required": [
-        "username",
-        "domain",
-        "archive"
-      ]
-    },
-    "security": [
-      {
-        "apiToken": []
-      }
-    ],
-    "group": "hosting"
-  },
   {
     "name": "hosting_getNode_jsBuildSettingsFromArchiveV1",
     "description": "Auto-detect Node.js build settings from a package.json inside an archive already on the server.\n\nUse this before calling `Start Node.js Build` to preview what settings will be used,\nor to let the user review and override values (framework, node version, root directory,\noutput directory, build script) before committing to a build.\n\nThe archive must already be present on the website's file storage. Use the\n`Generate Upload URL` endpoint to obtain credentials and upload the archive first.\nTo upload an archive and start a build in one step without inspecting settings first,\nuse the `Create Node.js Build from Archive` endpoint instead.",

package/src/servers/agency-hosting.js

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

package/src/servers/agency-hosting.ts

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

package/src/servers/all.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.45.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.45.2', tools });

package/src/servers/all.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.45.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.45.2', tools });

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: '1.45.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.45.2', tools });

package/src/servers/hosting.js

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

package/src/servers/hosting.ts

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

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: '1.45.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.45.2', 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: '1.45.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.45.2', tools });

package/types.d.ts

@@ -3296,77 +3296,6 @@ the `Get Node.js Build Logs` endpoint.
     response: any; // Response structure will depend on the API
   };
 
-  /**
-   * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.
-
-WARNING: on success this overwrites the website's existing contents and cannot be
-undone — verify this is intended before calling this endpoint.
-
-This is the recommended single-step approach for deploying a Node.js application.
-The archive is uploaded to the website's file storage, build settings are auto-detected
-from the package.json inside the archive, and the build process starts automatically.
-Optional override fields take precedence over auto-detected values.
-Maximum archive size is 50MB.
-
-Before archiving, exclude `node_modules/` and any build output directories
-(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build
-process runs the install step automatically, and including them unnecessarily
-increases the archive size. This also helps keep the archive well under the 50MB limit.
-
-Example (zip):
-```
-zip -r archive.zip . --exclude "node_modules/*" --exclude "dist/*"
-```
-
-The returned build `uuid` can be used to poll progress and retrieve logs via
-the `Get Node.js Build Logs` endpoint.
-   */
-  "hosting_createNodeJSBuildFromArchiveV1": {
-    params: {
-      /**
-       * username parameter
-       */
-      username: string;
-      /**
-       * Domain name
-       */
-      domain: string;
-      /**
-       * Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB
-       */
-      archive: string;
-      /**
-       * Node.js version override (auto-detected from package.json if omitted)
-       */
-      node_version?: number;
-      /**
-       * Node.js application type override
-       */
-      app_type?: string;
-      /**
-       * Application root directory override (where package.json is located) relative to public_html
-       */
-      root_directory?: string;
-      /**
-       * Build output directory override relative to the root directory
-       */
-      output_directory?: string;
-      /**
-       * Build script override
-       */
-      build_script?: string;
-      /**
-       * Main entry point file override
-       */
-      entry_file?: string;
-      /**
-       * Package manager override
-       */
-      package_manager?: string;
-    };
-    response: any; // Response structure will depend on the API
-  };
-
   /**
    * Auto-detect Node.js build settings from a package.json inside an archive already on the server.