hostinger-api-mcp 1.35.4 → 1.35.6

package/README.md

@@ -224,14 +224,14 @@ This MCP server provides the following tools:
 
 ### `hostinger-agency-hosting-mcp`
 
-#### agencyHosting_deployNodeStaticWebsite
+#### agency-hosting_deployNodeStaticWebsite
 
 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**: `custom`
 - **Path**: `custom`
 
-#### agencyHosting_deployPhpApplication
+#### agency-hosting_deployPhpApplication
 
 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.
 

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.35.4",
+  "version": "1.35.6",
   "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.35.4",
+  "version": "1.35.6",
   "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.35.4",
+  "version": "1.35.6",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "hostinger-api-mcp",
-      "version": "1.35.4",
+      "version": "1.35.6",
       "transport": {
         "type": "stdio"
       },

package/src/core/runtime.js

@@ -197,9 +197,9 @@ class MCPServer {
 
   async executeCustomTool(tool, params) {
     switch (tool.name) {
-      case 'agencyHosting_deployNodeStaticWebsite':
+      case 'agency-hosting_deployNodeStaticWebsite':
         return await this.handleNodeStaticDeploy(params);
-      case 'agencyHosting_deployPhpApplication':
+      case 'agency-hosting_deployPhpApplication':
         return await this.handlePhpAppDeploy(params);
       case 'hosting_importWordpressWebsite':
         return await this.handleWordpressWebsiteImport(params);

package/src/core/runtime.ts

@@ -227,9 +227,9 @@ class MCPServer {
 
   private async executeCustomTool(tool: OpenApiTool, params: Record<string, any>): Promise<any> {
     switch (tool.name) {
-      case 'agencyHosting_deployNodeStaticWebsite':
+      case 'agency-hosting_deployNodeStaticWebsite':
         return await this.handleNodeStaticDeploy(params);
-      case 'agencyHosting_deployPhpApplication':
+      case 'agency-hosting_deployPhpApplication':
         return await this.handlePhpAppDeploy(params);
       case 'hosting_importWordpressWebsite':
         return await this.handleWordpressWebsiteImport(params);

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

@@ -1,7 +1,7 @@
 // Auto-generated tool list for group: agency-hosting
 export default [
   {
-    "name": "agencyHosting_deployNodeStaticWebsite",
+    "name": "agency-hosting_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": "",
@@ -35,7 +35,7 @@ export default [
     "group": "agency-hosting"
   },
   {
-    "name": "agencyHosting_deployPhpApplication",
+    "name": "agency-hosting_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": "",

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

@@ -15,7 +15,7 @@ export interface OpenApiTool extends Tool {
 
 const tools: OpenApiTool[] = [
   {
-    "name": "agencyHosting_deployNodeStaticWebsite",
+    "name": "agency-hosting_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": "",
@@ -49,7 +49,7 @@ const tools: OpenApiTool[] = [
     "group": "agency-hosting"
   },
   {
-    "name": "agencyHosting_deployPhpApplication",
+    "name": "agency-hosting_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": "",

package/src/core/tools/all.js

@@ -1,7 +1,7 @@
 // Auto-generated tool list for group: all
 export default [
   {
-    "name": "agencyHosting_deployNodeStaticWebsite",
+    "name": "agency-hosting_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": "",
@@ -35,7 +35,7 @@ export default [
     "group": "agency-hosting"
   },
   {
-    "name": "agencyHosting_deployPhpApplication",
+    "name": "agency-hosting_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": "",

package/src/core/tools/all.ts

@@ -15,7 +15,7 @@ export interface OpenApiTool extends Tool {
 
 const tools: OpenApiTool[] = [
   {
-    "name": "agencyHosting_deployNodeStaticWebsite",
+    "name": "agency-hosting_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": "",
@@ -49,7 +49,7 @@ const tools: OpenApiTool[] = [
     "group": "agency-hosting"
   },
   {
-    "name": "agencyHosting_deployPhpApplication",
+    "name": "agency-hosting_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": "",

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

package/types.d.ts

@@ -7,7 +7,7 @@ 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": {
+  "agency-hosting_deployNodeStaticWebsite": {
     params: {
       /**
        * Domain name of the Agency Plan website (e.g., example.com)
@@ -28,7 +28,7 @@ export interface APITools {
   /**
    * 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": {
+  "agency-hosting_deployPhpApplication": {
     params: {
       /**
        * Domain name of the Agency Plan website (e.g., example.com)