hostinger-api-mcp 1.30.0 → 1.32.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 (291 total)
+- `hostinger-api-mcp` — unified server with every tool (308 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` — 12 tools for reach
+- `hostinger-reach-mcp` — 29 tools for reach
 - `hostinger-vps-mcp` — 62 tools for vps
 - `hostinger-wordpress-mcp` — 35 tools for wordpress
 
@@ -2132,9 +2132,55 @@ Delete a contact with the specified UUID.
 
 This endpoint permanently removes a contact from the email marketing system.
 
+**Deprecated.** This endpoint cannot target a profile, so it always falls back to the
+client's default profile and cannot delete contacts of any other profile. Use
+`DELETE /api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}` instead.
+
 - **Method**: `DELETE`
 - **Path**: `/api/reach/v1/contacts/{uuid}`
 
+#### reach_deleteAContactFieldV1
+
+Delete a custom contact field.
+
+Every value contacts hold for the field is deleted with it, and for the choice types so
+are its options. The contacts themselves are not affected.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields/{fieldUuid}`
+
+#### reach_updateAContactFieldV1
+
+Rename a custom contact field and, for the choice types, replace its option set.
+
+Options carrying a uuid are kept and relabelled, options without one are created, and any
+existing option left out of the list is deleted along with the values contacts hold for
+it. The field type and slug cannot be changed.
+
+- **Method**: `PATCH`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields/{fieldUuid}`
+
+#### reach_listContactFieldsV1
+
+Get the custom contact fields defined in a profile.
+
+Custom fields let you store your own attributes on contacts. The returned uuids are what
+you pass to the contact update endpoint to set values, and choice fields also list the
+options available to pick from.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields`
+
+#### reach_createAContactFieldV1
+
+Define a new custom contact field in a profile.
+
+The `slug` is derived from the label and, like the field type, cannot be changed later.
+Use the returned uuid to set values on contacts.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields`
+
 #### reach_listContactGroupsV1
 
 Get a list of all contact groups.
@@ -2151,6 +2197,11 @@ Get a list of contacts, optionally filtered by group and subscription status.
 This endpoint returns a paginated list of contacts with their basic information.
 You can filter contacts by group UUID and subscription status.
 
+**Deprecated.** This endpoint cannot target a profile, so it always falls back to the
+client's default profile and cannot list contacts of any other profile. Use
+`GET /api/reach/v1/profiles/{profileUuid}/contacts` instead, which also replaces the
+group filter with a tag filter.
+
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/contacts`
 
@@ -2166,6 +2217,73 @@ the contact will be created with a pending status and a confirmation email will
 - **Method**: `POST`
 - **Path**: `/api/reach/v1/contacts`
 
+#### reach_getContactDetailsV1
+
+Get the full details of a single contact.
+
+Alongside the contact's own attributes this returns the tags assigned to it and the
+values it holds for the profile's custom contact fields.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}`
+
+#### reach_deleteAProfileContactV1
+
+Permanently delete a contact from a profile.
+
+The contact is removed together with its custom field values and tag assignments.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}`
+
+#### reach_updateAContactV1
+
+Update a contact's attributes and custom field values.
+
+Only the properties present in the request body are changed, so a partial body is enough
+to change a single attribute. Sending a property as `null` clears it.
+
+The response carries the contact's core attributes. Read back its tags, custom field
+values, source and note with `GET /api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}`.
+
+- **Method**: `PATCH`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}`
+
+#### reach_createContactsInBulkV1
+
+Create many contacts in a profile in a single call.
+
+The contacts are imported in the background, so a success response means the import was
+accepted rather than finished. Contacts whose email already exists in the profile are
+left as they are. If double opt-in is enabled, new contacts start off pending and are
+sent a confirmation email.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/bulk`
+
+#### reach_listProfileContactsV1
+
+Get a paginated list of contacts belonging to a profile.
+
+Contacts can be filtered by subscription status, by tag, and by an email search term.
+The `meta.total` field of the response is the number of contacts matching the filters,
+so calling this endpoint without filters gives the profile's total contact count.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts`
+
+#### reach_createNewContactsV1
+
+Create a new contact in the email marketing system.
+
+This endpoint allows you to create a new contact with basic information like name, email, and surname.
+
+If double opt-in is enabled, the contact will be created with a pending status
+and a confirmation email will be sent.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts`
+
 #### reach_listSegmentsV1
 
 Get a list of all contact segments.
@@ -2215,17 +2333,88 @@ Segments are used to organize and group contacts based on specific criteria.
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/segmentation/segments/{segmentUuid}`
 
-#### reach_createNewContactsV1
+#### reach_assignAContactToATagV1
 
-Create a new contact in the email marketing system.
+Assign a tag to a single contact.
 
-This endpoint allows you to create a new contact with basic information like name, email, and surname.
+Unlike the bulk endpoint this is applied immediately rather than queued. Assigning a tag
+the contact already carries succeeds without duplicating it.
 
-If double opt-in is enabled, the contact will be created with a pending status
-and a confirmation email will be sent.
+- **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}/contacts`
+- **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
 

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.30.0",
+  "version": "1.32.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.30.0",
+  "version": "1.32.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.30.0",
+  "version": "1.32.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "hostinger-api-mcp",
-      "version": "1.30.0",
+      "version": "1.32.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.27.0
+ * Generated from OpenAPI spec version 1.29.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.27.0
+ * Generated from OpenAPI spec version 1.29.0
  */
 class MCPServer {
   private readonly name: string;