hostinger-api-mcp 1.44.0 → 1.45.1

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.44.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.45.1', 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.44.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.45.1', 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.44.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.45.1', 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.44.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.45.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: '1.44.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.45.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: '1.44.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.45.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: '1.44.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.45.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: '1.44.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.45.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: '1.44.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.45.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: '1.44.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.45.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: '1.44.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.45.1', tools });

package/types.d.ts

@@ -872,6 +872,51 @@ resources are removed in the background.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Retrieve a paginated list of Agency Plan websites (H5G, Builder, and Horizons) accessible to
+the authenticated client.
+
+This endpoint returns websites from your hosting accounts as well as
+websites from other client hosting accounts that have shared access
+with you.
+
+The response shape differs per platform — see the `platform` field on each item.
+
+Use `website_types` to list only websites of a given detected type, e.g. only
+WordPress websites (`website_types=wordpress`) or only Node.js websites
+(`website_types=nodejs`). Combine with `order_ids`, `states`, or `domain` for more
+targeted results.
+   */
+  "agency-hosting_listAgencyPlanWebsitesV1": {
+    params: {
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+      /**
+       * Filter by order IDs. Accepts a comma-separated list.
+       */
+      order_ids?: array;
+      /**
+       * Filter by website state. Accepts a comma-separated list.
+       */
+      states?: array;
+      /**
+       * Filter by detected website type, e.g. wordpress,nodejs. Accepts a comma-separated list.
+       */
+      website_types?: array;
+      /**
+       * Filter by domain name (case-insensitive substring match)
+       */
+      domain?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Lists active and recently completed asynchronous processes for an Agency Plan website.
 
@@ -2660,7 +2705,7 @@ Use the domain and is_assigned filters to find databases assigned to a specific
        */
       per_page?: number;
       /**
-       * Filter by domain name (exact match)
+       * Filter by domain name (case-insensitive substring match)
        */
       domain?: string;
       /**
@@ -3251,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.
 
@@ -3728,8 +3702,11 @@ website detected on the underlying platform (`wordpress`, `builder`,
 `vhost_type`, `username`, and `root_directory`, only apply to
 CloudLinux websites and are null for other platforms.
 
-Use the available query parameters to filter results by username,
-order ID, enabled status, or domain name for more targeted results.
+Use `website_types` to list only websites of a given detected type, e.g. only
+WordPress websites (`website_types=wordpress`) or only Node.js websites
+(`website_types=nodejs`). Combine with the other available query parameters to
+filter by username, order ID, enabled status, or domain name for more targeted
+results.
    */
   "hosting_listWebsitesV1": {
     params: {
@@ -3754,9 +3731,13 @@ order ID, enabled status, or domain name for more targeted results.
        */
       is_enabled?: boolean;
       /**
-       * Filter by domain name (exact match)
+       * Filter by domain name (case-insensitive substring match)
        */
       domain?: string;
+      /**
+       * Filter by detected website type, e.g. wordpress,nodejs. Accepts a comma-separated list.
+       */
+      website_types?: array;
     };
     response: any; // Response structure will depend on the API
   };
@@ -7476,7 +7457,7 @@ Each installation includes a `valid` flag and, when invalid, a
        */
       username?: string;
       /**
-       * Filter by domain name (exact match)
+       * Filter by domain name (case-insensitive substring match)
        */
       domain?: string;
       /**
@@ -7928,7 +7909,7 @@ domain. Optionally filter by domain to scope the check.
   "hosting_checkIfWooCommerceIsInstalledV1": {
     params: {
       /**
-       * Filter by domain name (exact match)
+       * Filter by domain name (case-insensitive substring match)
        */
       domain?: string;
     };