hostinger-api-mcp 3.11.0 → 3.12.0

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.11.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '3.12.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: '3.11.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.12.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: '3.11.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.12.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: '3.11.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.12.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: '3.11.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.12.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: '3.11.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.12.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: '3.11.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.12.0', tools });

package/types.d.ts

@@ -5,7 +5,7 @@
 
 export interface APITools {
   /**
-   * Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, pass appType and nodeVersion from the project's engines, plus outputDirectory and buildScript if the app has a build step). Git needs GitHub or GitLab connected once in hPanel.
+   * Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.
    */
   "hosting_deploy": {
     params: {
@@ -38,7 +38,7 @@ export interface APITools {
        */
       databaseDump?: string;
       /**
-       * Node.js major version (default: detected from an archive, or stored for the site, else 22; set it from the project's engines for a Git deploy)
+       * Node.js major version (default: detected from an archive, or stored for the site, else detected from the branch's package.json, else 22)
        */
       nodeVersion?: number;
       /**
@@ -50,17 +50,17 @@ export interface APITools {
        */
       rootDirectory?: string;
       /**
-       * Build output directory relative to the root directory, e.g. dist
+       * Build output directory relative to the root directory, e.g. dist. Pass null to clear a stored value.
        */
-      outputDirectory?: string;
+      outputDirectory?: string | null;
       /**
-       * The package.json script that builds the app, e.g. build
+       * The package.json script that builds the app, e.g. build. Pass null to clear a stored value.
        */
-      buildScript?: string;
+      buildScript?: string | null;
       /**
-       * Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next.
+       * Entry file of a server app. Relative to the root directory for express, fastify, hono, react-router and other; for a compiled (TypeScript) app give the built file, e.g. dist/server.js, because detection guesses a root-level file. Relative to the output directory for nest, nuxt, nitro, astro and svelte-kit (main.js, not dist/main.js). Ignored for next. Pass null to clear a stored value.
        */
-      entryFile?: string;
+      entryFile?: string | null;
       /**
        * Package manager used to install dependencies
        */
@@ -6707,7 +6707,8 @@ steps yet returns an empty list.
 progress.
 
 This describes how the campaign was set up and how far it has got. For opens, clicks and
-unsubscribes use the campaign statistics endpoint.
+unsubscribes use the campaign statistics endpoint. The email content is not included: pass
+`template_uuid` to the get email template endpoint to read its HTML.
    */
   "reach_campaigns_get": {
     params: {
@@ -8231,12 +8232,56 @@ full address: Reach adds the profile's connected sending domain itself.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Disconnect an eCommerce store from the profile.
+
+Reach stops receiving the store's customers and orders, and its products and coupons are
+removed from Reach; contacts and past orders stay. Take `store_id` from the list eCommerce
+stores endpoint; for a store that is `connected_to_other_profile`, call this with that
+profile. Also succeeds when the store is not connected to this profile, so success is not
+proof that anything was disconnected. Confirm the store and the plan with the customer
+before calling.
+   */
+  "reach_integrations_disconnect-ecommerce-store": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Hostinger eCommerce store ID, as returned by the eCommerce stores list
+       */
+      storeId: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Get all of the customer's Hostinger eCommerce stores, each with its `store_id` and
+`connection_status` for the profile in the path.
+
+A store is connected to at most one profile. `connected_to_other_profile` does not name that
+profile - call this for each profile to find it. The list is empty, not an error, when the
+eCommerce service cannot be reached. Pass `store_id` to the disconnect eCommerce store
+endpoint. Connecting an AI Website Builder site connects the store selling on it.
+   */
+  "reach_integrations_list-ecommerce-stores": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Get a list of the email templates in a profile, most recently updated first.
 
 Templates are the reusable email bodies a campaign is built from. The list is not paginated
-and only the metadata is returned - the template content itself is not exposed. Use the
-`uuid` of a template as the `template_uuid` when creating a campaign.
+and only the metadata is returned, without the HTML content. Use the `uuid` of a template
+as the `template_uuid` when creating a campaign. To read one template's HTML use the get
+email template endpoint, and only when the content itself is needed.
    */
   "reach_templates_list-email": {
     params: {
@@ -8275,6 +8320,109 @@ the markup self-contained.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Get one email template of the profile with its full HTML in `template_content`.
+
+A campaign's email content is its template: to read what a campaign sends, get the campaign
+and pass its `template_uuid` here. The HTML can be large, so fetch it only when the content
+itself is needed, never to browse or pick templates - the list email templates endpoint does
+that without content. Personalization tags such as `{{name}}` come back unrendered.
+   */
+  "reach_templates_email": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Template uuid parameter
+       */
+      templateUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Get the websites connected to the profile, each with its `domain` and `platform_type`.
+
+A domain is connected to at most one profile, so to find which plan a site is on, call this
+for each profile. Only connected sites are listed, not every website the customer owns, and
+eCommerce stores are not included - use the list eCommerce stores endpoint for those. Pass
+`domain` to the disconnect WordPress site or disconnect AI Website Builder site endpoint.
+   */
+  "reach_integrations_list-connected-websites": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Connect an AI Website Builder site the customer built manually to the profile, so its
+subscribers flow into Reach.
+
+Fails with not found when the customer owns no AI Website Builder site with that domain.
+Fails with `DOMAIN_ALREADY_EXISTS` when the domain is connected to any profile - to move a
+site to another plan, disconnect it from the old profile first - and with
+`WEBSITE_CONNECTION_ALREADY_EXISTS` when this profile already has an AI Website Builder site.
+The eCommerce store selling on the site, if it is not connected anywhere, is connected too.
+WordPress sites and sites made with the agentic AI Website Builder cannot be connected here.
+   */
+  "reach_integrations_connect-ai-website-builder-site": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * domain parameter
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Disconnect an AI Website Builder site from the profile; the site stops sending subscribers
+to Reach.
+
+Take `domain` from the list connected websites endpoint. Works for a site that was already
+deleted in the builder. Fails with not found when the domain is not connected to this
+profile. Contacts and any connected eCommerce store stay. The site stays disconnected until
+it is connected again, so confirm the site and the plan with the customer before calling.
+   */
+  "reach_integrations_disconnect-ai-website-builder-site": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Disconnect a WordPress site from the profile.
+
+The Reach plugin on the site stops sending subscribers and store data, and the site's
+products and coupons are removed from Reach; contacts and past orders stay. Take `domain`
+from the list connected websites endpoint. Fails with not found when the domain is not
+connected to this profile. This cannot be undone through the API - the customer reconnects
+from the WordPress plugin - so confirm the site and the plan with the customer before calling.
+   */
+  "reach_integrations_disconnect-wordpress-site": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve all available data centers.