hostinger-api-mcp 1.31.0 → 1.33.0

package/README.md

@@ -49,7 +49,7 @@ pnpm update -g hostinger-api-mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (300 total)
+- `hostinger-api-mcp` — unified server with every tool (314 total)
 - `hostinger-agency-hosting-mcp` — 27 tools for agency-hosting
 - `hostinger-billing-mcp` — 9 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
@@ -58,7 +58,7 @@ This package installs the following MCP server commands:
 - `hostinger-horizons-mcp` — 2 tools for horizons
 - `hostinger-hosting-mcp` — 48 tools for hosting
 - `hostinger-mail-mcp` — 38 tools for mail
-- `hostinger-reach-mcp` — 21 tools for reach
+- `hostinger-reach-mcp` — 35 tools for reach
 - `hostinger-vps-mcp` — 62 tools for vps
 - `hostinger-wordpress-mcp` — 35 tools for wordpress
 
@@ -2290,6 +2290,10 @@ 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.
+
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/segmentation/segments`
 
@@ -2300,9 +2304,22 @@ Create a new contact segment.
 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.
+
 - **Method**: `POST`
 - **Path**: `/api/reach/v1/segmentation/segments`
 
+#### reach_countProfileSegmentContactsV1
+
+Count the contacts currently matching a segment without listing them.
+
+Cheaper than paging through the segment contacts endpoint when only the size is needed.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}/count`
+
 #### reach_listProfileSegmentContactsV1
 
 Retrieve contacts associated with a specific segment for a given profile.
@@ -2313,6 +2330,57 @@ identified by its UUID, scoped to a specific profile.
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}/contacts`
 
+#### reach_getProfileSegmentDetailsV1
+
+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.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}`
+
+#### reach_updateAProfileSegmentV1
+
+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.
+
+- **Method**: `PUT`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}`
+
+#### reach_deleteAProfileSegmentV1
+
+Delete a segment.
+
+Only the segment definition is removed. The contacts that matched it are left untouched.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}`
+
+#### reach_listProfileSegmentsV1
+
+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.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments`
+
+#### reach_createAProfileSegmentV1
+
+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.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments`
+
 #### reach_listSegmentContactsV1
 
 Retrieve contacts associated with a specific segment.
@@ -2320,6 +2388,10 @@ 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.
+
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/segmentation/segments/{segmentUuid}/contacts`
 
@@ -2330,9 +2402,96 @@ Get details of a specific segment.
 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.
+
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/segmentation/segments/{segmentUuid}`
 
+#### reach_assignAContactToATagV1
+
+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.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts/{contactUuid}`
+
+#### reach_removeAContactFromATagV1
+
+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.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts/{contactUuid}`
+
+#### reach_assignContactsToATagV1
+
+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.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts`
+
+#### reach_removeContactsFromATagV1
+
+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.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts`
+
+#### reach_deleteATagV1
+
+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.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}`
+
+#### reach_renameATagV1
+
+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.
+
+- **Method**: `PATCH`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}`
+
+#### reach_listProfileTagsV1
+
+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.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags`
+
+#### reach_createOrFindTagsV1
+
+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.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/tags`
+
 #### reach_getProfileDomainDNSStatusV1
 
 Retrieve the DNS configuration status for a profile's domain.

package/gemini-extension.json

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

package/src/core/runtime.js

@@ -29,7 +29,7 @@ const SECURITY_SCHEMES = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.28.0
+ * Generated from OpenAPI spec version 1.30.0
  */
 class MCPServer {
   constructor({ name, version, tools }) {

package/src/core/runtime.ts

@@ -52,7 +52,7 @@ const SECURITY_SCHEMES: Record<string, SecurityScheme> = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.28.0
+ * Generated from OpenAPI spec version 1.30.0
  */
 class MCPServer {
   private readonly name: string;