hostinger-api-mcp 1.60.0 → 1.60.2

package/CHANGELOG.md

@@ -4,6 +4,38 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v1.60.2 — 2026-09-16
+
+### Tools
+
+- Added `hosting_getGitAutoDeploymentSettingsV1` — Get Git auto-deployment settings
+- Added `hosting_updateGitAutoDeploymentSettingsV1` — Update Git auto-deployment settings
+- Added `hosting_deleteGitAutoDeploymentSettingsV1` — Delete Git auto-deployment settings
+- Changed the description of `hosting_listGitInstallationsV1`
+- Changed the description of `hosting_listGitInstallationRepositoriesV1`
+- Changed the description and input schema of `hosting_startNode_jsBuildV1`
+
+### Also in this release
+
+- Documentation: `README.md`
+- Dependencies: `package-lock.json`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Build and packaging: `types.d.ts`
+
+## v1.60.1 — 2026-09-15
+
+### Tools
+
+- Added `hosting_listGitInstallationsV1` — List Git installations
+- Added `hosting_listGitInstallationRepositoriesV1` — List Git installation repositories
+
+### Also in this release
+
+- Documentation: `README.md`
+- Dependencies: `package-lock.json`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Build and packaging: `types.d.ts`
+
 ## v1.60.0 — 2026-09-14
 
 ### Also in this release

package/README.md

@@ -69,14 +69,14 @@ pnpm update -g @hostinger/mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (387 total)
+- `hostinger-api-mcp` — unified server with every tool (392 total)
 - `hostinger-agency-hosting-mcp` — 38 tools for agency-hosting
 - `hostinger-billing-mcp` — 9 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
 - `hostinger-domains-mcp` — 41 tools for domains
 - `hostinger-ecommerce-mcp` — 29 tools for ecommerce
 - `hostinger-horizons-mcp` — 6 tools for horizons
-- `hostinger-hosting-mcp` — 64 tools for hosting
+- `hostinger-hosting-mcp` — 69 tools for hosting
 - `hostinger-mail-mcp` — 38 tools for mail
 - `hostinger-reach-mcp` — 52 tools for reach
 - `hostinger-vps-mcp` — 64 tools for vps
@@ -2038,6 +2038,77 @@ containing secrets (e.g. credential files) — none of these are returned by thi
 - **Method**: `GET`
 - **Path**: `/api/hosting/v1/accounts/{username}/domains/{domain}/files/content`
 
+#### hosting_getGitAutoDeploymentSettingsV1
+
+Returns the Git auto-deployment settings of the website: which repository and branch deploy
+into which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the
+repository link but ignores pushes.
+
+When the website has no auto-deployment configured every field is null. Save settings with
+`Update Git auto-deployment settings`.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings`
+
+#### hosting_updateGitAutoDeploymentSettingsV1
+
+Creates or replaces the Git auto-deployment settings of the website: repository, branch, the
+directory under the document root to deploy into, and `is_enabled`. Send the full set;
+`is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must
+be an installation from `List Git installations` that belongs to the same customer as the
+website.
+
+For PHP and static websites, saving with `is_enabled` true deploys the branch right away and
+every later push to that branch deploys again. For Node.js and Website Builder websites saving
+does not clone anything. On a Node.js website start the first deploy with
+`Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build
+settings stored for the website.
+
+- **Method**: `PUT`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings`
+
+#### hosting_deleteGitAutoDeploymentSettingsV1
+
+Removes the Git auto-deployment settings of the website. Files already deployed stay on the
+website; pushes stop deploying until settings are saved again. Succeeds also when nothing is
+configured.
+
+- **Method**: `DELETE`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings`
+
+#### hosting_listGitInstallationsV1
+
+Lists the Git provider accounts the customer has connected. Only installations with status
+`active` are returned unless the `status` filter says otherwise.
+
+An empty list means the customer has no active installation. Check `status=suspended` and
+`status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be
+connected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App,
+Import Git Repository); this endpoint then lists the new installation.
+
+Use `uuid` as the path parameter of `List Git installation repositories`, and as
+`installation_uuid` in `Start Node.js build` with `source_type` `git` and in
+`Update Git auto-deployment settings`.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/git/installations`
+
+#### hosting_listGitInstallationRepositoriesV1
+
+Lists the repositories the Git installation can access, read live from the provider. Works
+for github and gitlab installations. Use an active installation: a suspended or pending one
+is still queried and the call fails with whatever the provider answers. The list is cut at
+the first 500 repositories in the order the provider returns them; when the account has
+more, name the repository directly instead of searching this list.
+
+`owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of
+`Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the
+installation does not belong to the customer. Limited to 10 calls per minute per API client
+(429 above that).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/git/installations/{uuid}/repositories`
+
 #### hosting_listNodeJSBuildsV1
 
 Retrieve a paginated list of Node.js build processes for a specific website.
@@ -2056,13 +2127,17 @@ Start a Node.js build process using files already present on the website's file
 WARNING: on success this overwrites the website's existing contents and cannot be
 undone — verify this is intended before calling this endpoint.
 
-The `source_type` must be `archive` and `source_options.archive_path` must point to an
-existing archive file on the server (relative to the website document root).
-Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.
-
-To auto-detect build settings from an archive before starting, first call the
+With `source_type` `archive`, `source_options.archive_path` must point to an existing
+archive file on the server (relative to the website document root). Use the
+`Generate Upload URL` endpoint to obtain credentials and upload the archive first. To
+auto-detect build settings from an archive before starting, first call the
 `Get Node.js Build Settings from Archive` endpoint.
 
+With `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and
+`installation_uuid`. Take the installation from `List Git installations` and the owner and
+repository from `List Git installation repositories`; the branch is cloned at its current
+head. The installation must belong to the same customer as the website.
+
 The returned build `uuid` can be used to poll progress and retrieve logs via
 the `Get Node.js Build Logs` endpoint.
 

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.60.0",
+  "version": "1.60.2",
   "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.60.0",
+  "version": "1.60.2",
   "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.60.0",
+  "version": "1.60.2",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "1.60.0",
+      "version": "1.60.2",
       "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.52.0
+ * Generated from OpenAPI spec version 1.52.2
  */
 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.52.0
+ * Generated from OpenAPI spec version 1.52.2
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -6716,6 +6716,213 @@ export default [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_getGitAutoDeploymentSettingsV1",
+    "title": "Get Git auto-deployment settings",
+    "annotations": {
+      "title": "Get Git auto-deployment settings",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "description": "Returns the Git auto-deployment settings of the website: which repository and branch deploy\ninto which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the\nrepository link but ignores pushes.\n\nWhen the website has no auto-deployment configured every field is null. Save settings with\n`Update Git auto-deployment settings`.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_updateGitAutoDeploymentSettingsV1",
+    "title": "Update Git auto-deployment settings",
+    "annotations": {
+      "title": "Update Git auto-deployment settings",
+      "readOnlyHint": false,
+      "destructiveHint": true,
+      "idempotentHint": true
+    },
+    "description": "Creates or replaces the Git auto-deployment settings of the website: repository, branch, the\ndirectory under the document root to deploy into, and `is_enabled`. Send the full set;\n`is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must\nbe an installation from `List Git installations` that belongs to the same customer as the\nwebsite.\n\nFor PHP and static websites, saving with `is_enabled` true deploys the branch right away and\nevery later push to that branch deploys again. For Node.js and Website Builder websites saving\ndoes not clone anything. On a Node.js website start the first deploy with\n`Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build\nsettings stored for the website.",
+    "method": "PUT",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "installation_uuid": {
+          "type": "string",
+          "description": "Active Git installation from `List Git installations`"
+        },
+        "owner": {
+          "type": "string",
+          "description": "Repository owner login, as returned by `List Git installation repositories`. GitLab group\npaths use slashes."
+        },
+        "repository": {
+          "type": "string",
+          "description": "Repository name without the .git suffix"
+        },
+        "branch": {
+          "type": "string",
+          "description": "Branch to deploy"
+        },
+        "directory": {
+          "type": "string",
+          "description": "Subdirectory under the website document root to deploy into. Empty, null or omitted means\nthe document root."
+        },
+        "is_enabled": {
+          "type": "boolean",
+          "description": "Whether pushes to the branch deploy automatically"
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "installation_uuid",
+        "owner",
+        "repository",
+        "branch"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_deleteGitAutoDeploymentSettingsV1",
+    "title": "Delete Git auto-deployment settings",
+    "annotations": {
+      "title": "Delete Git auto-deployment settings",
+      "readOnlyHint": false,
+      "destructiveHint": true,
+      "idempotentHint": true
+    },
+    "description": "Removes the Git auto-deployment settings of the website. Files already deployed stay on the\nwebsite; pushes stop deploying until settings are saved again. Succeeds also when nothing is\nconfigured.",
+    "method": "DELETE",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_listGitInstallationsV1",
+    "title": "List Git installations",
+    "annotations": {
+      "title": "List Git installations",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "description": "Lists the Git provider accounts the customer has connected. Only installations with status\n`active` are returned unless the `status` filter says otherwise.\n\nAn empty list means the customer has no active installation. Check `status=suspended` and\n`status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be\nconnected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App,\nImport Git Repository); this endpoint then lists the new installation.\n\nUse `uuid` as the path parameter of `List Git installation repositories`, and as\n`installation_uuid` in `Start Node.js build` with `source_type` `git` and in\n`Update Git auto-deployment settings`.",
+    "method": "GET",
+    "path": "/api/hosting/v1/git/installations",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "provider": {
+          "type": "string",
+          "description": "Filter by Git provider",
+          "enum": [
+            "github",
+            "gitlab",
+            "bitbucket"
+          ]
+        },
+        "status": {
+          "type": "string",
+          "description": "Filter by installation status",
+          "enum": [
+            "pending",
+            "active",
+            "suspended"
+          ]
+        }
+      },
+      "required": []
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_listGitInstallationRepositoriesV1",
+    "title": "List Git installation repositories",
+    "annotations": {
+      "title": "List Git installation repositories",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "description": "Lists the repositories the Git installation can access, read live from the provider. Works\nfor github and gitlab installations. Use an active installation: a suspended or pending one\nis still queried and the call fails with whatever the provider answers. The list is cut at\nthe first 500 repositories in the order the provider returns them; when the account has\nmore, name the repository directly instead of searching this list.\n\n`owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of\n`Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the\ninstallation does not belong to the customer. Limited to 10 calls per minute per API client\n(429 above that).",
+    "method": "GET",
+    "path": "/api/hosting/v1/git/installations/{uuid}/repositories",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "uuid": {
+          "type": "string",
+          "description": "Git installation UUID from the List Git installations endpoint"
+        }
+      },
+      "required": [
+        "uuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listNodeJSBuildsV1",
     "title": "List NodeJS builds",
@@ -6781,7 +6988,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Start a Node.js build process using files already present on the website's file storage.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nThe `source_type` must be `archive` and `source_options.archive_path` must point to an\nexisting archive file on the server (relative to the website document root).\nUse the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.\n\nTo auto-detect build settings from an archive before starting, first call the\n`Get Node.js Build Settings from Archive` endpoint.\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
+    "description": "Start a Node.js build process using files already present on the website's file storage.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nWith `source_type` `archive`, `source_options.archive_path` must point to an existing\narchive file on the server (relative to the website document root). Use the\n`Generate Upload URL` endpoint to obtain credentials and upload the archive first. To\nauto-detect build settings from an archive before starting, first call the\n`Get Node.js Build Settings from Archive` endpoint.\n\nWith `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and\n`installation_uuid`. Take the installation from `List Git installations` and the owner and\nrepository from `List Git installation repositories`; the branch is cloned at its current\nhead. The installation must belong to the same customer as the website.\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds",
     "inputSchema": {
@@ -6857,18 +7064,35 @@ export default [
         },
         "source_type": {
           "type": "string",
-          "description": "The source type of the files",
+          "description": "Where the files come from: `archive` (an uploaded archive on the website) or `git`\n(a branch of a repository reachable through a Git installation).",
           "enum": [
-            "archive"
+            "archive",
+            "git"
           ]
         },
         "source_options": {
           "type": "object",
-          "description": "Source-specific options",
+          "description": "Source-specific options. For `archive` send `archive_path`. For `git` send `owner`,\n`repository`, `branch` and `installation_uuid`, taken from `List Git installations`\nand `List Git installation repositories`.",
           "properties": {
             "archive_path": {
               "type": "string",
               "description": "The path to the archive file relative to the document root of the vhost (required if source is \"archive\")"
+            },
+            "owner": {
+              "type": "string",
+              "description": "Repository owner login (required if source is \"git\"). GitLab group paths use\nslashes."
+            },
+            "repository": {
+              "type": "string",
+              "description": "Repository name without the .git suffix (required if source is \"git\")"
+            },
+            "branch": {
+              "type": "string",
+              "description": "Branch to build (required if source is \"git\")"
+            },
+            "installation_uuid": {
+              "type": "string",
+              "description": "Git installation used to access the repository (required if source is \"git\")"
             }
           }
         }