hostinger-api-mcp 2.7.2 → 2.8.0

package/CHANGELOG.md

@@ -4,6 +4,32 @@ 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.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
+
+- Changed the description and input schema of `wordpress_installations_install`
+
+### Also in this release
+
+- Documentation: `README.md`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Build and packaging: `types.d.ts`
+
 ## v2.7.2 — 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
@@ -2510,19 +2510,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.
@@ -4534,6 +4563,9 @@ takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered
 by username and domain to track progress. When the installation appears in
 that list, WordPress is ready.
 
+Returns 422 when the account already uses all the databases its plan allows,
+unless `database.name` is an existing database on the account.
+
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations`
 

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "2.7.2",
+  "version": "2.8.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.2",
+  "version": "2.8.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.2",
+  "version": "2.8.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "2.7.2",
+      "version": "2.8.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.2
+ * Generated from OpenAPI spec version 1.59.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.2
+ * Generated from OpenAPI spec version 1.59.0
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -8138,12 +8138,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 +8166,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",
@@ -15472,7 +15564,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -15540,7 +15632,7 @@ export default [
         },
         "database": {
           "type": "object",
-          "description": "Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -15548,7 +15640,7 @@ export default [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

package/src/core/tools/all.ts

@@ -8152,12 +8152,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 +8180,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",
@@ -15486,7 +15578,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -15554,7 +15646,7 @@ const tools: OpenApiTool[] = [
         },
         "database": {
           "type": "object",
-          "description": "Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -15562,7 +15654,7 @@ const tools: OpenApiTool[] = [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

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/core/tools/wordpress.js

@@ -255,7 +255,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -323,7 +323,7 @@ export default [
         },
         "database": {
           "type": "object",
-          "description": "Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -331,7 +331,7 @@ export default [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

package/src/core/tools/wordpress.ts

@@ -269,7 +269,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -337,7 +337,7 @@ const tools: OpenApiTool[] = [
         },
         "database": {
           "type": "object",
-          "description": "Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -345,7 +345,7 @@ const tools: OpenApiTool[] = [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

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.2', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.8.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.2', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.8.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.2', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.8.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.2', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '2.8.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.2', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '2.8.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.2', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.8.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.2', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.8.0', tools });

package/types.d.ts

@@ -4717,18 +4717,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 +4749,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.
 
@@ -9045,6 +9100,9 @@ job has been queued, not that WordPress is ready. Installation typically
 takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered
 by username and domain to track progress. When the installation appears in
 that list, WordPress is ready.
+
+Returns 422 when the account already uses all the databases its plan allows,
+unless `database.name` is an existing database on the account.
    */
   "wordpress_installations_install": {
     params: {
@@ -9085,7 +9143,7 @@ that list, WordPress is ready.
        */
       credentials: object;
       /**
-       * Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.
+       * Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.
        */
       database?: object;
     };