hostinger-api-mcp 2.7.3 → 2.9.0

package/CHANGELOG.md

@@ -4,6 +4,34 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v2.9.0 — 2026-10-07
+
+### Operations
+
+- Changed the description and input schema of `horizons_websites_publish`
+- Changed the description of `horizons_websites_get`
+
+### 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`
+
+## v2.8.0 — 2026-10-06
+
+### Operations
+
+- Added `hosting_websites_start-setup` — Start website setup
+- Changed the description and input schema of `hosting_websites_list-setups`
+
+### 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`
+
 ## v2.7.3 — 2026-10-05
 
 ### Operations

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 over every operation (407 total)
+- `hostinger-api-mcp` — unified server over every operation (408 total)
 - `hostinger-agency-hosting-mcp` — 42 operations for agency-hosting
 - `hostinger-billing-mcp` — 9 operations for billing
 - `hostinger-dns-mcp` — 8 operations for dns
 - `hostinger-domains-mcp` — 42 operations for domains
 - `hostinger-ecommerce-mcp` — 29 operations for ecommerce
 - `hostinger-horizons-mcp` — 6 operations for horizons
-- `hostinger-hosting-mcp` — 79 operations for hosting
+- `hostinger-hosting-mcp` — 80 operations for hosting
 - `hostinger-mail-mcp` — 38 operations for mail
 - `hostinger-reach-mcp` — 52 operations for reach
 - `hostinger-vps-mcp` — 64 operations for vps
@@ -1747,6 +1747,9 @@ Publish a Hostinger Horizons website so its latest changes go live.\n
 Use this tool when the user asks to publish, deploy or make their website live.\n
 This tool starts the publish process and returns the URL the website will be live on.
 Publishing happens asynchronously and takes a few minutes.\n
+Set `is_template` only when the user explicitly asks to share the website as a template:
+true adds a "Use template" banner to its published pages that copies the website into the
+visitor's own account, and false removes it. Leave it out to keep the current setting.\n
 After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing
 that the website is being published and you should provide the published URL to the user immediately.
 
@@ -1758,6 +1761,10 @@ that the website is being published and you should provide the published URL to
 Get the link for the user to open their website in Hostinger Horizons interface.\n
 Use this tool when the user wants the link to an existing website, or when you need its
 website URL before or after editing it.\n
+`is_in_progress` is true while changes are being generated or the website is being published;
+wait until it is false before publishing. `published_at` is when the website was last published,
+`is_template` is whether its published pages show the "Use template" banner, and
+`has_ecommerce_store` is whether it has an online store.\n
 Websites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons
 interface in the provided website URL.
 
@@ -2510,19 +2517,48 @@ close or merge it before patching again. Available on Business and Cloud Hosting
 #### hosting_websites_list-setups
 
 Returns the website setups started in the last 24 hours for the hosting accounts
-accessible to the authenticated client, newest first.
-
-Meant for polling right after creating a website: the website shows up in the
-websites list before its server-side setup has finished, and while the setup is
-`running` endpoints that operate on that website may respond with `404` or `409`.
-Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for
-`status: completed` before uploading files, deploying or creating databases.
+accessible to the authenticated client, newest first. Narrow the list with the
+`order_id`, `subscription_id` or `domain` filters.
+
+Meant for polling right after creating a website or starting a website setup: the
+website shows up in the websites list before its server-side setup has finished, and
+while the setup is `running` endpoints that operate on that website may respond with
+`404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and
+wait for `status: completed` before uploading files, deploying or creating databases.
 `failed` means the setup stopped before finishing or has not reported progress for
 over an hour. Setups older than 24 hours are not listed.
 
+`type` is the website type the setup was started with (`wordpress`, `headless_wordpress`,
+`headless_ecommerce`, `headless_pocketbase`), or `null` for an empty website.
+
 - **Method**: `GET`
 - **Path**: `/api/hosting/v1/onboardings`
 
+#### hosting_websites_start-setup
+
+Starts a website setup on a Web or Cloud hosting order and returns the created setup
+right away; the website itself is provisioned asynchronously. Poll the list website
+setups endpoint with the `domain` filter every 10 to 15 seconds and wait for
+`status: completed` before uploading files, deploying or creating databases.
+
+Omit `type` for an empty website. `type: wordpress` installs WordPress in the website
+root with the admin user, email and password from `wordpress`, the domain as the site
+title, and `en_US` when `wordpress.language` is omitted. The headless types
+(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless
+website; `headless_wordpress` additionally installs WordPress into the `cms` directory
+of the website root with generated credentials.
+
+Omit `domain` to set the website up on a generated temporary free subdomain.
+
+The order must already have a hosting account: to create the first website on a new
+hosting plan use the create website endpoint, which takes the `datacenter_code`.
+Returns 404 when the order does not exist or is not accessible to the authenticated
+client, and 409 with a `Retry-After` header while a setup for the same domain is still
+running.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/orders/{order_id}/onboardings`
+
 #### hosting_orders_list
 
 Retrieve a paginated list of orders accessible to the authenticated client.

package/gemini-extension.json

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

package/src/core/runtime.js

@@ -64,7 +64,7 @@ const GetSkillRequestSchema = z.object({
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.58.3
+ * Generated from OpenAPI spec version 1.60.0
  */
 class MCPServer {
   constructor({ name, version, tools, instructions, skills = [] }) {

package/src/core/runtime.ts

@@ -94,7 +94,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.58.3
+ * Generated from OpenAPI spec version 1.60.0
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -5770,7 +5770,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
+    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nSet `is_template` only when the user explicitly asks to share the website as a template:\ntrue adds a \"Use template\" banner to its published pages that copies the website into the\nvisitor's own account, and false removes it. Leave it out to keep the current setting.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
     "method": "POST",
     "path": "/api/horizons/v1/websites/{websiteId}/publish",
     "inputSchema": {
@@ -5779,6 +5779,10 @@ export default [
         "websiteId": {
           "type": "string",
           "description": "The website ID"
+        },
+        "is_template": {
+          "type": "boolean",
+          "description": "Set to true to publish the website as a template: its published pages show a \"Use template\" banner\nthat copies the website into the visitor's own account. Set to false to remove the banner.\nLeave it out to keep the current setting."
         }
       },
       "required": [
@@ -5800,7 +5804,7 @@ export default [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
+    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\n`is_in_progress` is true while changes are being generated or the website is being published;\nwait until it is false before publishing. `published_at` is when the website was last published,\n`is_template` is whether its published pages show the \"Use template\" banner, and\n`has_ecommerce_store` is whether it has an online store.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
     "method": "GET",
     "path": "/api/horizons/v1/websites/{websiteId}",
     "inputSchema": {
@@ -8138,12 +8142,20 @@ export default [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first.\n\nMeant for polling right after creating a website: the website shows up in the\nwebsites list before its server-side setup has finished, and while the setup is\n`running` endpoints that operate on that website may respond with `404` or `409`.\nPoll this endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.",
+    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first. Narrow the list with the\n`order_id`, `subscription_id` or `domain` filters.\n\nMeant for polling right after creating a website or starting a website setup: the\nwebsite shows up in the websites list before its server-side setup has finished, and\nwhile the setup is `running` endpoints that operate on that website may respond with\n`404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and\nwait for `status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.\n\n`type` is the website type the setup was started with (`wordpress`, `headless_wordpress`,\n`headless_ecommerce`, `headless_pocketbase`), or `null` for an empty website.",
     "method": "GET",
     "path": "/api/hosting/v1/onboardings",
     "inputSchema": {
       "type": "object",
       "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Order ID"
+        },
+        "subscription_id": {
+          "type": "string",
+          "description": "Filter by hosting order subscription ID"
+        },
         "domain": {
           "type": "string",
           "description": "Filter by domain name (exact match)"
@@ -8158,6 +8170,90 @@ export default [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_websites_start-setup",
+    "title": "Start website setup",
+    "annotations": {
+      "title": "Start website setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "method": "POST",
+    "path": "/api/hosting/v1/orders/{order_id}/onboardings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Hosting order ID. List orders to find available IDs."
+        },
+        "type": {
+          "type": "string",
+          "description": "Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials.",
+          "enum": [
+            "wordpress",
+            "headless_wordpress",
+            "headless_ecommerce",
+            "headless_pocketbase"
+          ]
+        },
+        "domain": {
+          "type": "string",
+          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "wordpress": {
+          "type": "object",
+          "description": "WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.",
+          "properties": {
+            "language": {
+              "type": "string",
+              "description": "WordPress locale, for example `en_US` or `lt_LT`. Defaults to `en_US` when omitted."
+            },
+            "is_ai_builder": {
+              "type": "boolean",
+              "description": "When `true`, installs the Hostinger AI theme (`hostinger-ai-theme`). Defaults to `false` when omitted."
+            },
+            "admin": {
+              "type": "object",
+              "description": "WordPress administrator account",
+              "properties": {
+                "user": {
+                  "type": "string",
+                  "description": "WordPress admin username (letters, numbers, and underscore)"
+                },
+                "password": {
+                  "type": "string",
+                  "description": "WordPress admin password (8-50 characters, mixed case, a digit, and not compromised)"
+                },
+                "email": {
+                  "type": "string",
+                  "description": "WordPress admin email address"
+                }
+              },
+              "required": [
+                "user",
+                "password",
+                "email"
+              ]
+            }
+          },
+          "required": [
+            "admin"
+          ]
+        }
+      },
+      "required": [
+        "order_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_orders_list",
     "title": "List orders",

package/src/core/tools/all.ts

@@ -5784,7 +5784,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
+    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nSet `is_template` only when the user explicitly asks to share the website as a template:\ntrue adds a \"Use template\" banner to its published pages that copies the website into the\nvisitor's own account, and false removes it. Leave it out to keep the current setting.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
     "method": "POST",
     "path": "/api/horizons/v1/websites/{websiteId}/publish",
     "inputSchema": {
@@ -5793,6 +5793,10 @@ const tools: OpenApiTool[] = [
         "websiteId": {
           "type": "string",
           "description": "The website ID"
+        },
+        "is_template": {
+          "type": "boolean",
+          "description": "Set to true to publish the website as a template: its published pages show a \"Use template\" banner\nthat copies the website into the visitor's own account. Set to false to remove the banner.\nLeave it out to keep the current setting."
         }
       },
       "required": [
@@ -5814,7 +5818,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
+    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\n`is_in_progress` is true while changes are being generated or the website is being published;\nwait until it is false before publishing. `published_at` is when the website was last published,\n`is_template` is whether its published pages show the \"Use template\" banner, and\n`has_ecommerce_store` is whether it has an online store.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
     "method": "GET",
     "path": "/api/horizons/v1/websites/{websiteId}",
     "inputSchema": {
@@ -8152,12 +8156,20 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first.\n\nMeant for polling right after creating a website: the website shows up in the\nwebsites list before its server-side setup has finished, and while the setup is\n`running` endpoints that operate on that website may respond with `404` or `409`.\nPoll this endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.",
+    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first. Narrow the list with the\n`order_id`, `subscription_id` or `domain` filters.\n\nMeant for polling right after creating a website or starting a website setup: the\nwebsite shows up in the websites list before its server-side setup has finished, and\nwhile the setup is `running` endpoints that operate on that website may respond with\n`404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and\nwait for `status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.\n\n`type` is the website type the setup was started with (`wordpress`, `headless_wordpress`,\n`headless_ecommerce`, `headless_pocketbase`), or `null` for an empty website.",
     "method": "GET",
     "path": "/api/hosting/v1/onboardings",
     "inputSchema": {
       "type": "object",
       "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Order ID"
+        },
+        "subscription_id": {
+          "type": "string",
+          "description": "Filter by hosting order subscription ID"
+        },
         "domain": {
           "type": "string",
           "description": "Filter by domain name (exact match)"
@@ -8172,6 +8184,90 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_websites_start-setup",
+    "title": "Start website setup",
+    "annotations": {
+      "title": "Start website setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "method": "POST",
+    "path": "/api/hosting/v1/orders/{order_id}/onboardings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Hosting order ID. List orders to find available IDs."
+        },
+        "type": {
+          "type": "string",
+          "description": "Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials.",
+          "enum": [
+            "wordpress",
+            "headless_wordpress",
+            "headless_ecommerce",
+            "headless_pocketbase"
+          ]
+        },
+        "domain": {
+          "type": "string",
+          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "wordpress": {
+          "type": "object",
+          "description": "WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.",
+          "properties": {
+            "language": {
+              "type": "string",
+              "description": "WordPress locale, for example `en_US` or `lt_LT`. Defaults to `en_US` when omitted."
+            },
+            "is_ai_builder": {
+              "type": "boolean",
+              "description": "When `true`, installs the Hostinger AI theme (`hostinger-ai-theme`). Defaults to `false` when omitted."
+            },
+            "admin": {
+              "type": "object",
+              "description": "WordPress administrator account",
+              "properties": {
+                "user": {
+                  "type": "string",
+                  "description": "WordPress admin username (letters, numbers, and underscore)"
+                },
+                "password": {
+                  "type": "string",
+                  "description": "WordPress admin password (8-50 characters, mixed case, a digit, and not compromised)"
+                },
+                "email": {
+                  "type": "string",
+                  "description": "WordPress admin email address"
+                }
+              },
+              "required": [
+                "user",
+                "password",
+                "email"
+              ]
+            }
+          },
+          "required": [
+            "admin"
+          ]
+        }
+      },
+      "required": [
+        "order_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_orders_list",
     "title": "List orders",

package/src/core/tools/horizons.js

@@ -168,7 +168,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
+    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nSet `is_template` only when the user explicitly asks to share the website as a template:\ntrue adds a \"Use template\" banner to its published pages that copies the website into the\nvisitor's own account, and false removes it. Leave it out to keep the current setting.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
     "method": "POST",
     "path": "/api/horizons/v1/websites/{websiteId}/publish",
     "inputSchema": {
@@ -177,6 +177,10 @@ export default [
         "websiteId": {
           "type": "string",
           "description": "The website ID"
+        },
+        "is_template": {
+          "type": "boolean",
+          "description": "Set to true to publish the website as a template: its published pages show a \"Use template\" banner\nthat copies the website into the visitor's own account. Set to false to remove the banner.\nLeave it out to keep the current setting."
         }
       },
       "required": [
@@ -198,7 +202,7 @@ export default [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
+    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\n`is_in_progress` is true while changes are being generated or the website is being published;\nwait until it is false before publishing. `published_at` is when the website was last published,\n`is_template` is whether its published pages show the \"Use template\" banner, and\n`has_ecommerce_store` is whether it has an online store.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
     "method": "GET",
     "path": "/api/horizons/v1/websites/{websiteId}",
     "inputSchema": {

package/src/core/tools/horizons.ts

@@ -182,7 +182,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
+    "description": "Publish a Hostinger Horizons website so its latest changes go live.\\n\nUse this tool when the user asks to publish, deploy or make their website live.\\n\nThis tool starts the publish process and returns the URL the website will be live on.\nPublishing happens asynchronously and takes a few minutes.\\n\nSet `is_template` only when the user explicitly asks to share the website as a template:\ntrue adds a \"Use template\" banner to its published pages that copies the website into the\nvisitor's own account, and false removes it. Leave it out to keep the current setting.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat the website is being published and you should provide the published URL to the user immediately.",
     "method": "POST",
     "path": "/api/horizons/v1/websites/{websiteId}/publish",
     "inputSchema": {
@@ -191,6 +191,10 @@ const tools: OpenApiTool[] = [
         "websiteId": {
           "type": "string",
           "description": "The website ID"
+        },
+        "is_template": {
+          "type": "boolean",
+          "description": "Set to true to publish the website as a template: its published pages show a \"Use template\" banner\nthat copies the website into the visitor's own account. Set to false to remove the banner.\nLeave it out to keep the current setting."
         }
       },
       "required": [
@@ -212,7 +216,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
+    "description": "Get the link for the user to open their website in Hostinger Horizons interface.\\n\nUse this tool when the user wants the link to an existing website, or when you need its\nwebsite URL before or after editing it.\\n\n`is_in_progress` is true while changes are being generated or the website is being published;\nwait until it is false before publishing. `published_at` is when the website was last published,\n`is_template` is whether its published pages show the \"Use template\" banner, and\n`has_ecommerce_store` is whether it has an online store.\\n\nWebsites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons\ninterface in the provided website URL.",
     "method": "GET",
     "path": "/api/horizons/v1/websites/{websiteId}",
     "inputSchema": {

package/src/core/tools/hosting.js

@@ -2615,12 +2615,20 @@ export default [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first.\n\nMeant for polling right after creating a website: the website shows up in the\nwebsites list before its server-side setup has finished, and while the setup is\n`running` endpoints that operate on that website may respond with `404` or `409`.\nPoll this endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.",
+    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first. Narrow the list with the\n`order_id`, `subscription_id` or `domain` filters.\n\nMeant for polling right after creating a website or starting a website setup: the\nwebsite shows up in the websites list before its server-side setup has finished, and\nwhile the setup is `running` endpoints that operate on that website may respond with\n`404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and\nwait for `status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.\n\n`type` is the website type the setup was started with (`wordpress`, `headless_wordpress`,\n`headless_ecommerce`, `headless_pocketbase`), or `null` for an empty website.",
     "method": "GET",
     "path": "/api/hosting/v1/onboardings",
     "inputSchema": {
       "type": "object",
       "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Order ID"
+        },
+        "subscription_id": {
+          "type": "string",
+          "description": "Filter by hosting order subscription ID"
+        },
         "domain": {
           "type": "string",
           "description": "Filter by domain name (exact match)"
@@ -2635,6 +2643,90 @@ export default [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_websites_start-setup",
+    "title": "Start website setup",
+    "annotations": {
+      "title": "Start website setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "method": "POST",
+    "path": "/api/hosting/v1/orders/{order_id}/onboardings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Hosting order ID. List orders to find available IDs."
+        },
+        "type": {
+          "type": "string",
+          "description": "Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials.",
+          "enum": [
+            "wordpress",
+            "headless_wordpress",
+            "headless_ecommerce",
+            "headless_pocketbase"
+          ]
+        },
+        "domain": {
+          "type": "string",
+          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "wordpress": {
+          "type": "object",
+          "description": "WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.",
+          "properties": {
+            "language": {
+              "type": "string",
+              "description": "WordPress locale, for example `en_US` or `lt_LT`. Defaults to `en_US` when omitted."
+            },
+            "is_ai_builder": {
+              "type": "boolean",
+              "description": "When `true`, installs the Hostinger AI theme (`hostinger-ai-theme`). Defaults to `false` when omitted."
+            },
+            "admin": {
+              "type": "object",
+              "description": "WordPress administrator account",
+              "properties": {
+                "user": {
+                  "type": "string",
+                  "description": "WordPress admin username (letters, numbers, and underscore)"
+                },
+                "password": {
+                  "type": "string",
+                  "description": "WordPress admin password (8-50 characters, mixed case, a digit, and not compromised)"
+                },
+                "email": {
+                  "type": "string",
+                  "description": "WordPress admin email address"
+                }
+              },
+              "required": [
+                "user",
+                "password",
+                "email"
+              ]
+            }
+          },
+          "required": [
+            "admin"
+          ]
+        }
+      },
+      "required": [
+        "order_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_orders_list",
     "title": "List orders",

package/src/core/tools/hosting.ts

@@ -2629,12 +2629,20 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first.\n\nMeant for polling right after creating a website: the website shows up in the\nwebsites list before its server-side setup has finished, and while the setup is\n`running` endpoints that operate on that website may respond with `404` or `409`.\nPoll this endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.",
+    "description": "Returns the website setups started in the last 24 hours for the hosting accounts\naccessible to the authenticated client, newest first. Narrow the list with the\n`order_id`, `subscription_id` or `domain` filters.\n\nMeant for polling right after creating a website or starting a website setup: the\nwebsite shows up in the websites list before its server-side setup has finished, and\nwhile the setup is `running` endpoints that operate on that website may respond with\n`404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and\nwait for `status: completed` before uploading files, deploying or creating databases.\n`failed` means the setup stopped before finishing or has not reported progress for\nover an hour. Setups older than 24 hours are not listed.\n\n`type` is the website type the setup was started with (`wordpress`, `headless_wordpress`,\n`headless_ecommerce`, `headless_pocketbase`), or `null` for an empty website.",
     "method": "GET",
     "path": "/api/hosting/v1/onboardings",
     "inputSchema": {
       "type": "object",
       "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Order ID"
+        },
+        "subscription_id": {
+          "type": "string",
+          "description": "Filter by hosting order subscription ID"
+        },
         "domain": {
           "type": "string",
           "description": "Filter by domain name (exact match)"
@@ -2649,6 +2657,90 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_websites_start-setup",
+    "title": "Start website setup",
+    "annotations": {
+      "title": "Start website setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "method": "POST",
+    "path": "/api/hosting/v1/orders/{order_id}/onboardings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Hosting order ID. List orders to find available IDs."
+        },
+        "type": {
+          "type": "string",
+          "description": "Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials.",
+          "enum": [
+            "wordpress",
+            "headless_wordpress",
+            "headless_ecommerce",
+            "headless_pocketbase"
+          ]
+        },
+        "domain": {
+          "type": "string",
+          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "wordpress": {
+          "type": "object",
+          "description": "WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.",
+          "properties": {
+            "language": {
+              "type": "string",
+              "description": "WordPress locale, for example `en_US` or `lt_LT`. Defaults to `en_US` when omitted."
+            },
+            "is_ai_builder": {
+              "type": "boolean",
+              "description": "When `true`, installs the Hostinger AI theme (`hostinger-ai-theme`). Defaults to `false` when omitted."
+            },
+            "admin": {
+              "type": "object",
+              "description": "WordPress administrator account",
+              "properties": {
+                "user": {
+                  "type": "string",
+                  "description": "WordPress admin username (letters, numbers, and underscore)"
+                },
+                "password": {
+                  "type": "string",
+                  "description": "WordPress admin password (8-50 characters, mixed case, a digit, and not compromised)"
+                },
+                "email": {
+                  "type": "string",
+                  "description": "WordPress admin email address"
+                }
+              },
+              "required": [
+                "user",
+                "password",
+                "email"
+              ]
+            }
+          },
+          "required": [
+            "admin"
+          ]
+        }
+      },
+      "required": [
+        "order_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_orders_list",
     "title": "List orders",

package/src/servers/agency-hosting.js

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.7.3', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.9.0', tools, instructions });

package/src/servers/agency-hosting.ts

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.7.3', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.9.0', tools, instructions });

package/src/servers/all.js

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '2.7.3', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.9.0', tools, instructions, skills });

package/src/servers/all.ts

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '2.7.3', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.9.0', tools, instructions, skills });

package/src/servers/billing.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '2.7.3', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '2.9.0', tools });

package/src/servers/billing.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '2.7.3', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '2.9.0', tools });

package/src/servers/dns.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '2.7.3', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '2.9.0', tools });

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: '2.7.3', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '2.9.0', tools });

package/src/servers/hosting.js

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '2.7.3', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '2.9.0', tools, instructions });

package/src/servers/hosting.ts

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '2.7.3', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '2.9.0', tools, instructions });

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: '2.7.3', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.9.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: '2.7.3', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.9.0', tools });

package/types.d.ts

@@ -3191,6 +3191,9 @@ and do not generate code yourself in the chat.
 Use this tool when the user asks to publish, deploy or make their website live.\n
 This tool starts the publish process and returns the URL the website will be live on.
 Publishing happens asynchronously and takes a few minutes.\n
+Set `is_template` only when the user explicitly asks to share the website as a template:
+true adds a "Use template" banner to its published pages that copies the website into the
+visitor's own account, and false removes it. Leave it out to keep the current setting.\n
 After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing
 that the website is being published and you should provide the published URL to the user immediately.
    */
@@ -3200,6 +3203,12 @@ that the website is being published and you should provide the published URL to
        * The website ID
        */
       websiteId: string;
+      /**
+       * Set to true to publish the website as a template: its published pages show a "Use template" banner
+that copies the website into the visitor's own account. Set to false to remove the banner.
+Leave it out to keep the current setting.
+       */
+      is_template?: boolean;
     };
     response: any; // Response structure will depend on the API
   };
@@ -3208,6 +3217,10 @@ that the website is being published and you should provide the published URL to
    * Get the link for the user to open their website in Hostinger Horizons interface.\n
 Use this tool when the user wants the link to an existing website, or when you need its
 website URL before or after editing it.\n
+`is_in_progress` is true while changes are being generated or the website is being published;
+wait until it is false before publishing. `published_at` is when the website was last published,
+`is_template` is whether its published pages show the "Use template" banner, and
+`has_ecommerce_store` is whether it has an online store.\n
 Websites can be edited with the `Edit website` tool, or by the user in Hostinger Horizons
 interface in the provided website URL.
    */
@@ -4717,18 +4730,30 @@ close or merge it before patching again. Available on Business and Cloud Hosting
 
   /**
    * Returns the website setups started in the last 24 hours for the hosting accounts
-accessible to the authenticated client, newest first.
-
-Meant for polling right after creating a website: the website shows up in the
-websites list before its server-side setup has finished, and while the setup is
-`running` endpoints that operate on that website may respond with `404` or `409`.
-Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for
-`status: completed` before uploading files, deploying or creating databases.
+accessible to the authenticated client, newest first. Narrow the list with the
+`order_id`, `subscription_id` or `domain` filters.
+
+Meant for polling right after creating a website or starting a website setup: the
+website shows up in the websites list before its server-side setup has finished, and
+while the setup is `running` endpoints that operate on that website may respond with
+`404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and
+wait for `status: completed` before uploading files, deploying or creating databases.
 `failed` means the setup stopped before finishing or has not reported progress for
 over an hour. Setups older than 24 hours are not listed.
+
+`type` is the website type the setup was started with (`wordpress`, `headless_wordpress`,
+`headless_ecommerce`, `headless_pocketbase`), or `null` for an empty website.
    */
   "hosting_websites_list-setups": {
     params: {
+      /**
+       * Order ID
+       */
+      order_id?: number;
+      /**
+       * Filter by hosting order subscription ID
+       */
+      subscription_id?: string;
       /**
        * Filter by domain name (exact match)
        */
@@ -4737,6 +4762,49 @@ over an hour. Setups older than 24 hours are not listed.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Starts a website setup on a Web or Cloud hosting order and returns the created setup
+right away; the website itself is provisioned asynchronously. Poll the list website
+setups endpoint with the `domain` filter every 10 to 15 seconds and wait for
+`status: completed` before uploading files, deploying or creating databases.
+
+Omit `type` for an empty website. `type: wordpress` installs WordPress in the website
+root with the admin user, email and password from `wordpress`, the domain as the site
+title, and `en_US` when `wordpress.language` is omitted. The headless types
+(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless
+website; `headless_wordpress` additionally installs WordPress into the `cms` directory
+of the website root with generated credentials.
+
+Omit `domain` to set the website up on a generated temporary free subdomain.
+
+The order must already have a hosting account: to create the first website on a new
+hosting plan use the create website endpoint, which takes the `datacenter_code`.
+Returns 404 when the order does not exist or is not accessible to the authenticated
+client, and 409 with a `Retry-After` header while a setup for the same domain is still
+running.
+   */
+  "hosting_websites_start-setup": {
+    params: {
+      /**
+       * Hosting order ID. List orders to find available IDs.
+       */
+      order_id: number;
+      /**
+       * Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials.
+       */
+      type?: string;
+      /**
+       * Customer-owned domain. Cannot start with "www.". Omit or `null` to set the website up on a generated temporary free subdomain.
+       */
+      domain?: string;
+      /**
+       * WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.
+       */
+      wordpress?: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a paginated list of orders accessible to the authenticated client.