hostinger-api-mcp 3.24.3 → 3.25.1

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.24.3', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.25.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.24.3', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '3.25.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.24.3', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '3.25.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.24.3', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '3.25.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.24.3', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.25.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.24.3', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.25.1', tools });

package/types.d.ts

@@ -153,6 +153,94 @@ export interface APITools {
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * List the extra domains of a website: its parked (alias) domains, which show the same site under another domain name, and its subdomains (e.g. blog.example.com), with each one's root directory. parked items have domain (a domain name or an IP address) and type (domain or ip); subdomains items have domain (the full name), subdomain (the prefix) and root_directory. A list that cannot be read comes back as { error } and the other is still returned. To add or remove one use hosting_websites_add-domain or hosting_websites_remove-domain. Works for Shared and Cloud hosting websites.
+   */
+  "hosting_websites_list-domains": {
+    params: {
+      /**
+       * Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Add a domain to an existing website: type parked adds a parked (alias) domain, a second domain name (or an IP address) that shows the same site; type subdomain creates a subdomain such as blog.example.com with its own directory. For a parked domain the domain must be owned by the account or already point to the website: check a domain from outside the account with hosting_domains_verify-ownership first. www belongs to the main domain: do not add it as a subdomain. To create a new website use hosting_websites_create instead. Works for Shared and Cloud hosting websites.
+   */
+  "hosting_websites_add-domain": {
+    params: {
+      /**
+       * Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)
+       */
+      domain: string;
+      /**
+       * parked: an alias domain that shows the same website; subdomain: a subdomain of the website's domain.
+       */
+      type: string;
+      /**
+       * For parked: the domain name or IP address to park (e.g., example.net). For subdomain: the prefix (e.g., blog) or the full name (e.g., blog.example.com).
+       */
+      name: string;
+      /**
+       * Subdomains only: the subdomain's directory relative to the website root.
+       */
+      directory?: string;
+      /**
+       * Subdomains only: serve the subdomain from the website's public directory instead of its own directory.
+       */
+      usePublicDirectory?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Remove a parked (alias) domain or a subdomain from a website. Pass its name as hosting_websites_list-domains shows it: a parked domain, or a subdomain's full name or prefix; the tool finds which one it is. To delete a whole website use hosting_websites_delete. Works for Shared and Cloud hosting websites.
+   */
+  "hosting_websites_remove-domain": {
+    params: {
+      /**
+       * Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)
+       */
+      domain: string;
+      /**
+       * The parked domain (e.g., example.net) or the subdomain, as its full name (e.g., blog.example.com) or prefix (e.g., blog), to remove.
+       */
+      name: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Renamed to hosting_websites_create. This name still runs so older skills keep working, and will be removed in a future release.
+   */
+  "hosting_websites_start-setup": {
+    params: {
+      /**
+       * Hosting order ID. List orders to find available IDs.
+       */
+      order_id: number;
+      /**
+       * Website type, as hosting_websites_create takes it.
+       */
+      type?: string;
+      /**
+       * Domain for the website, as hosting_websites_create takes it.
+       */
+      domain?: string;
+      /**
+       * Datacenter code, as hosting_websites_create takes it.
+       */
+      datacenter_code?: string;
+      /**
+       * WordPress install settings, as hosting_websites_create takes them.
+       */
+      wordpress?: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * 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. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For plain PHP applications that should be extracted as-is, use agency-hosting_deploy-php-application instead. The website UID is automatically resolved from the domain.
    */
@@ -5274,11 +5362,11 @@ nothing: WordPress can be added later through
 `POST /api/hosting/v1/accounts/{username}/wordpress/installations`
 (`wordpress_installations_install`) with `type: headless`.
 
-Omit `domain` to set the website up on a generated temporary free subdomain. To know the
-free subdomain before the call, so a timed-out call can be looked up and retried on the
-same domain, generate one through `POST /api/hosting/v1/domains/free-subdomains`
-(`hosting_domains_generate-free-subdomain`) and send it as `domain`. It is accepted for
-24 hours, only from the client that generated it.
+Omit `domain` to set the website up on a generated temporary free subdomain; the created
+setup returns it as `domain`. REST clients that need to know the free subdomain before the
+call, so a timed-out call can be looked up and retried on the same domain, can generate
+one through `POST /api/hosting/v1/domains/free-subdomains` and send it as `domain`. It is
+accepted for 24 hours, only from the client that generated it.
 
 When the order has no hosting account yet, the setup creates one first, in the datacenter
 given by `datacenter_code` or the order's default datacenter when it is omitted.
@@ -5286,7 +5374,7 @@ Returns 404 when the order does not exist or is not accessible to the authentica
 client, and 409 with a `Retry-After` header while a setup for the same domain is still
 running.
    */
-  "hosting_websites_start-setup": {
+  "hosting_websites_create": {
     params: {
       /**
        * Hosting order ID. List orders to find available IDs.
@@ -5297,7 +5385,7 @@ running.
        */
       type?: string;
       /**
-       * Customer-owned domain, or a free subdomain you generated through `POST /api/hosting/v1/domains/free-subdomains` (`hosting_domains_generate-free-subdomain`) in the last 24 hours. Cannot start with "www." and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain.
+       * Customer-owned domain. Omit or `null` to set the website up on a generated temporary free subdomain. Cannot start with "www." and can have at most one subdomain level, e.g. `blog.example.com`. A free subdomain generated through `POST /api/hosting/v1/domains/free-subdomains` in the last 24 hours is also accepted.
        */
       domain?: string;
       /**
@@ -5734,7 +5822,7 @@ completed` before uploading files, deploying or creating databases. While the se
 `running`, endpoints that operate on the website may respond with `404` or `409`.
 `is_enabled` on the websites list reflects suspension, not readiness.
    */
-  "hosting_websites_create": {
+  "hosting_websites_create-deprecated": {
     params: {
       /**
        * Domain name for the website. Cannot start with "www." and can have at most one subdomain level, e.g. `blog.example.com`.
@@ -10295,12 +10383,12 @@ database files that have been uploaded to the website's directory.
 
 The website must already exist before calling this endpoint. To create a new
 website first, use POST /api/hosting/v1/orders/{order_id}/onboardings
-(`hosting_websites_start-setup`) and poll GET /api/hosting/v1/onboardings
+(`hosting_websites_create`) and poll GET /api/hosting/v1/onboardings
 (`hosting_websites_list-setups`) with the `domain` filter until its `status` is
 `completed`.
 
 Send `type: headless` to turn a headless website (for example one created by
-`hosting_websites_start-setup` with `type: headless_empty`) into a headless WordPress
+`hosting_websites_create` with `type: headless_empty`) into a headless WordPress
 website: WordPress is installed into the `cms` directory with the Hostinger headless
 MU plugin and the website is marked as a headless WordPress website. `directory` is
 not allowed with it. The target website must already be headless: the headless
@@ -10340,7 +10428,7 @@ unless `database.name` is an existing database on the account.
        */
       language?: string;
       /**
-       * Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_start-setup`) with `type: headless_empty`; any other website is rejected with 422.
+       * Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_create`) with `type: headless_empty`; any other website is rejected with 422.
        */
       type?: string;
       /**