hostinger-api-mcp 1.31.0 → 1.33.0

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

package/types.d.ts

@@ -4565,6 +4565,10 @@ and a confirmation email will be sent.
    * Get a list of all contact segments.
 
 This endpoint returns a list of contact segments that can be used to organize contacts.
+
+**Deprecated.** This endpoint cannot target a profile, so it always falls back to
+the client's default profile and cannot list the segments of any other profile. Use
+`GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments` instead.
    */
   "reach_listSegmentsV1": {
     params: {
@@ -4578,6 +4582,10 @@ This endpoint returns a list of contact segments that can be used to organize co
 
 This endpoint allows creating a new contact segment that can be used to organize contacts.
 The segment can be configured with specific criteria like email, name, subscription status, etc.
+
+**Deprecated.** This endpoint cannot target a profile, so it always falls back to
+the client's default profile and cannot create segments in any other profile. Use
+`POST /api/reach/v1/profiles/{profileUuid}/segmentation/segments` instead.
    */
   "reach_createANewContactSegmentV1": {
     params: {
@@ -4597,6 +4605,25 @@ The segment can be configured with specific criteria like email, name, subscript
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Count the contacts currently matching a segment without listing them.
+
+Cheaper than paging through the segment contacts endpoint when only the size is needed.
+   */
+  "reach_countProfileSegmentContactsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Segment uuid parameter
+       */
+      segmentUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve contacts associated with a specific segment for a given profile.
 
@@ -4625,11 +4652,144 @@ identified by its UUID, scoped to a specific profile.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Get a single segment of a profile, including the conditions that define it.
+
+To retrieve the contacts currently matching those conditions, use the segment contacts
+endpoint instead.
+   */
+  "reach_getProfileSegmentDetailsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Segment uuid parameter
+       */
+      segmentUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Rename a segment and/or replace the conditions that define it.
+
+`name` is always required. Omit `conditions` to rename without touching the conditions;
+supply them and they replace the existing set entirely rather than being merged into it.
+Contacts are never modified, but which of them match the segment can change immediately.
+   */
+  "reach_updateAProfileSegmentV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Segment uuid parameter
+       */
+      segmentUuid: string;
+      /**
+       * name parameter
+       */
+      name: string;
+      /**
+       * Replaces the existing conditions entirely. Omit to keep the current ones.
+       */
+      conditions?: array;
+      /**
+       * How to combine multiple conditions. Required when conditions are given.
+       */
+      logic?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Delete a segment.
+
+Only the segment definition is removed. The contacts that matched it are left untouched.
+   */
+  "reach_deleteAProfileSegmentV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Segment uuid parameter
+       */
+      segmentUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Get a paginated list of the segments defined in a profile.
+
+Each entry carries the number of contacts currently matching it, which is recalculated on
+read rather than stored. Use `count_type` to count either every matching contact or only
+the subscribed ones.
+   */
+  "reach_listProfileSegmentsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Which matching contacts to count for each segment
+       */
+      count_type?: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Create a segment in a profile.
+
+A segment is a saved set of conditions rather than a fixed list, so its membership changes
+as contacts change. Creating one does not modify any contact.
+   */
+  "reach_createAProfileSegmentV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * name parameter
+       */
+      name: string;
+      /**
+       * Conditions a contact must satisfy to fall into the segment
+       */
+      conditions: array;
+      /**
+       * How to combine multiple conditions
+       */
+      logic: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve contacts associated with a specific segment.
 
 This endpoint allows you to fetch and filter contacts that belong to a particular segment,
 identified by its UUID.
+
+**Deprecated.** This endpoint cannot target a profile, so it always falls back to
+the client's default profile and cannot read segments of any other profile. Use
+`GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}/contacts` instead.
    */
   "reach_listSegmentContactsV1": {
     params: {
@@ -4654,6 +4814,10 @@ identified by its UUID.
 
 This endpoint retrieves information about a single segment identified by UUID.
 Segments are used to organize and group contacts based on specific criteria.
+
+**Deprecated.** This endpoint cannot target a profile, so it always falls back to
+the client's default profile and cannot read segments of any other profile. Use
+`GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}` instead.
    */
   "reach_getSegmentDetailsV1": {
     params: {
@@ -4665,6 +4829,185 @@ Segments are used to organize and group contacts based on specific criteria.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Assign a tag to a single contact.
+
+Unlike the bulk endpoint this is applied immediately rather than queued. Assigning a tag
+the contact already carries succeeds without duplicating it.
+   */
+  "reach_assignAContactToATagV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Tag uuid parameter
+       */
+      tagUuid: string;
+      /**
+       * Contact uuid parameter
+       */
+      contactUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Remove a tag from a single contact.
+
+Unlike the bulk endpoint this is applied immediately rather than queued. Neither the tag
+nor the contact is deleted.
+   */
+  "reach_removeAContactFromATagV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Tag uuid parameter
+       */
+      tagUuid: string;
+      /**
+       * Contact uuid parameter
+       */
+      contactUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Assign a tag to many contacts at once.
+
+Pass `contact_uuids` to target specific contacts, or `all_contacts` to target every contact
+in the profile. The work is queued, so a success response means it was accepted rather than
+finished. Contacts that already carry the tag are left alone.
+   */
+  "reach_assignContactsToATagV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Tag uuid parameter
+       */
+      tagUuid: string;
+      /**
+       * Contacts to apply the change to. Required unless all_contacts is true.
+       */
+      contact_uuids?: array;
+      /**
+       * Apply to every contact in the profile
+       */
+      all_contacts?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Remove a tag from many contacts at once.
+
+Pass `contact_uuids` to target specific contacts, or `all_contacts` to target every contact
+in the profile. The work is queued, so a success response means it was accepted rather than
+finished. The tag itself and the contacts are not deleted.
+   */
+  "reach_removeContactsFromATagV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Tag uuid parameter
+       */
+      tagUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Delete a tag and remove it from every contact carrying it.
+
+The contacts themselves are not deleted. This is idempotent: deleting a tag that does not
+exist in the profile still succeeds.
+   */
+  "reach_deleteATagV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Tag uuid parameter
+       */
+      tagUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Rename a tag.
+
+The contacts assigned to the tag are unaffected. Names are unique within a profile, so
+renaming a tag to a name that is already taken is rejected.
+   */
+  "reach_renameATagV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Tag uuid parameter
+       */
+      tagUuid: string;
+      /**
+       * New tag name
+       */
+      value: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Get all tags defined in a profile.
+
+Tags are the way contacts are grouped in Reach, and can be used to filter the contact
+list or to build segments.
+   */
+  "reach_listProfileTagsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Create tags in a profile.
+
+Names that already exist in the profile are not duplicated: the existing tag is returned
+instead, so the call is safe to repeat. Every tag in the request is returned, whether it
+was created now or already existed.
+   */
+  "reach_createOrFindTagsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * names parameter
+       */
+      names: array;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve the DNS configuration status for a profile's domain.