hostinger-api-mcp 1.6.2 → 1.7.0

package/src/core/tools/agency-hosting.ts

@@ -14,6 +14,74 @@ export interface OpenApiTool extends Tool {
 }
 
 const tools: OpenApiTool[] = [
+  {
+    "name": "agencyHosting_deployNodeStaticWebsite",
+    "topic": "agency-hosting",
+    "description": "Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the Agency Plan website (e.g., example.com)"
+        },
+        "archivePath": {
+          "type": "string",
+          "description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
+        },
+        "removeArchive": {
+          "type": "boolean",
+          "description": "Whether to remove the local archive file after successful deployment (default: true)"
+        }
+      },
+      "required": [
+        "domain",
+        "archivePath"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "deploy-node-static.template.js",
+    "templateFileTS": "deploy-node-static.template.ts",
+    "handlerMethod": "handleNodeStaticDeploy",
+    "group": "agency-hosting"
+  },
+  {
+    "name": "agencyHosting_deployPhpApplication",
+    "topic": "agency-hosting",
+    "description": "Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the Agency Plan website (e.g., example.com)"
+        },
+        "archivePath": {
+          "type": "string",
+          "description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
+        },
+        "removeArchive": {
+          "type": "boolean",
+          "description": "Whether to remove the local archive file after successful deployment (default: true)"
+        }
+      },
+      "required": [
+        "domain",
+        "archivePath"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "deploy-php-app.template.js",
+    "templateFileTS": "deploy-php-app.template.ts",
+    "handlerMethod": "handlePhpAppDeploy",
+    "group": "agency-hosting"
+  },
   {
     "name": "agency-hosting_listAvailableDatacentersForAnAgencyPlanOrderV1",
     "description": "Lists the datacenters available for provisioning a new website on the given Agency Plan\nhosting order.\n\nEach datacenter includes a `pinger_url` you can ping from the client to measure round-trip\nlatency; comparing the results across datacenters lets you pick the nearest one (lowest\nping) before choosing its `code` as the `datacenter_code` when creating a website setup.",

package/src/core/tools/all.js

@@ -1,5 +1,73 @@
 // Auto-generated tool list for group: all
 export default [
+  {
+    "name": "agencyHosting_deployNodeStaticWebsite",
+    "topic": "agency-hosting",
+    "description": "Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the Agency Plan website (e.g., example.com)"
+        },
+        "archivePath": {
+          "type": "string",
+          "description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
+        },
+        "removeArchive": {
+          "type": "boolean",
+          "description": "Whether to remove the local archive file after successful deployment (default: true)"
+        }
+      },
+      "required": [
+        "domain",
+        "archivePath"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "deploy-node-static.template.js",
+    "templateFileTS": "deploy-node-static.template.ts",
+    "handlerMethod": "handleNodeStaticDeploy",
+    "group": "agency-hosting"
+  },
+  {
+    "name": "agencyHosting_deployPhpApplication",
+    "topic": "agency-hosting",
+    "description": "Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the Agency Plan website (e.g., example.com)"
+        },
+        "archivePath": {
+          "type": "string",
+          "description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
+        },
+        "removeArchive": {
+          "type": "boolean",
+          "description": "Whether to remove the local archive file after successful deployment (default: true)"
+        }
+      },
+      "required": [
+        "domain",
+        "archivePath"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "deploy-php-app.template.js",
+    "templateFileTS": "deploy-php-app.template.ts",
+    "handlerMethod": "handlePhpAppDeploy",
+    "group": "agency-hosting"
+  },
   {
     "name": "hosting_importWordpressWebsite",
     "topic": "hosting",

package/src/core/tools/all.ts

@@ -14,6 +14,74 @@ export interface OpenApiTool extends Tool {
 }
 
 const tools: OpenApiTool[] = [
+  {
+    "name": "agencyHosting_deployNodeStaticWebsite",
+    "topic": "agency-hosting",
+    "description": "Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the Agency Plan website (e.g., example.com)"
+        },
+        "archivePath": {
+          "type": "string",
+          "description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
+        },
+        "removeArchive": {
+          "type": "boolean",
+          "description": "Whether to remove the local archive file after successful deployment (default: true)"
+        }
+      },
+      "required": [
+        "domain",
+        "archivePath"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "deploy-node-static.template.js",
+    "templateFileTS": "deploy-node-static.template.ts",
+    "handlerMethod": "handleNodeStaticDeploy",
+    "group": "agency-hosting"
+  },
+  {
+    "name": "agencyHosting_deployPhpApplication",
+    "topic": "agency-hosting",
+    "description": "Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the Agency Plan website (e.g., example.com)"
+        },
+        "archivePath": {
+          "type": "string",
+          "description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
+        },
+        "removeArchive": {
+          "type": "boolean",
+          "description": "Whether to remove the local archive file after successful deployment (default: true)"
+        }
+      },
+      "required": [
+        "domain",
+        "archivePath"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "deploy-php-app.template.js",
+    "templateFileTS": "deploy-php-app.template.ts",
+    "handlerMethod": "handlePhpAppDeploy",
+    "group": "agency-hosting"
+  },
   {
     "name": "hosting_importWordpressWebsite",
     "topic": "hosting",

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.6.2', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.7.0', 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.6.2', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.7.0', tools });

package/types.d.ts

@@ -4,6 +4,48 @@
  */
 
 export interface APITools {
+  /**
+   * Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.
+   */
+  "agencyHosting_deployNodeStaticWebsite": {
+    params: {
+      /**
+       * Domain name of the Agency Plan website (e.g., example.com)
+       */
+      domain: string;
+      /**
+       * Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)
+       */
+      archivePath: string;
+      /**
+       * Whether to remove the local archive file after successful deployment (default: true)
+       */
+      removeArchive?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.
+   */
+  "agencyHosting_deployPhpApplication": {
+    params: {
+      /**
+       * Domain name of the Agency Plan website (e.g., example.com)
+       */
+      domain: string;
+      /**
+       * Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)
+       */
+      archivePath: string;
+      /**
+       * Whether to remove the local archive file after successful deployment (default: true)
+       */
+      removeArchive?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. The username will be automatically resolved from the domain.
    */