hostinger-api-mcp 3.24.3 → 3.25.1

package/src/core/tools/hosting.js

@@ -349,6 +349,177 @@ export default [
     "handlerMethod": "handleHostingCacheClear",
     "group": "hosting"
   },
+  {
+    "name": "hosting_websites_list-domains",
+    "title": "List website parked (alias) domains and subdomains",
+    "annotations": {
+      "title": "List website parked (alias) domains and subdomains",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "topic": "hosting",
+    "description": "List the extra domains of a website: its parked (alias) domains, which show the same site under another domain name, and its subdomains (e.g. blog.example.com), with each one's root directory. parked items have domain (a domain name or an IP address) and type (domain or ip); subdomains items have domain (the full name), subdomain (the prefix) and root_directory. A list that cannot be read comes back as { error } and the other is still returned. To add or remove one use hosting_websites_add-domain or hosting_websites_remove-domain. Works for Shared and Cloud hosting websites.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)"
+        }
+      },
+      "required": [
+        "domain"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "replacesHidden": true,
+    "templateFile": "list-domains.template.js",
+    "templateFileTS": "list-domains.template.ts",
+    "handlerMethod": "handleHostingWebsitesListDomains",
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_websites_add-domain",
+    "title": "Add a parked (alias) domain or subdomain to a website",
+    "annotations": {
+      "title": "Add a parked (alias) domain or subdomain to a website",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "topic": "hosting",
+    "description": "Add a domain to an existing website: type parked adds a parked (alias) domain, a second domain name (or an IP address) that shows the same site; type subdomain creates a subdomain such as blog.example.com with its own directory. For a parked domain the domain must be owned by the account or already point to the website: check a domain from outside the account with hosting_domains_verify-ownership first. www belongs to the main domain: do not add it as a subdomain. To create a new website use hosting_websites_create instead. Works for Shared and Cloud hosting websites.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)"
+        },
+        "type": {
+          "type": "string",
+          "enum": [
+            "parked",
+            "subdomain"
+          ],
+          "description": "parked: an alias domain that shows the same website; subdomain: a subdomain of the website's domain."
+        },
+        "name": {
+          "type": "string",
+          "description": "For parked: the domain name or IP address to park (e.g., example.net). For subdomain: the prefix (e.g., blog) or the full name (e.g., blog.example.com)."
+        },
+        "directory": {
+          "type": "string",
+          "description": "Subdomains only: the subdomain's directory relative to the website root."
+        },
+        "usePublicDirectory": {
+          "type": "boolean",
+          "description": "Subdomains only: serve the subdomain from the website's public directory instead of its own directory."
+        }
+      },
+      "required": [
+        "domain",
+        "type",
+        "name"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "replacesHidden": true,
+    "templateFile": "add-domain.template.js",
+    "templateFileTS": "add-domain.template.ts",
+    "handlerMethod": "handleHostingWebsitesAddDomain",
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_websites_remove-domain",
+    "title": "Remove a parked (alias) domain or subdomain from a website",
+    "annotations": {
+      "title": "Remove a parked (alias) domain or subdomain from a website",
+      "readOnlyHint": false,
+      "destructiveHint": true
+    },
+    "topic": "hosting",
+    "description": "Remove a parked (alias) domain or a subdomain from a website. Pass its name as hosting_websites_list-domains shows it: a parked domain, or a subdomain's full name or prefix; the tool finds which one it is. To delete a whole website use hosting_websites_delete. Works for Shared and Cloud hosting websites.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)"
+        },
+        "name": {
+          "type": "string",
+          "description": "The parked domain (e.g., example.net) or the subdomain, as its full name (e.g., blog.example.com) or prefix (e.g., blog), to remove."
+        }
+      },
+      "required": [
+        "domain",
+        "name"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "replacesHidden": true,
+    "templateFile": "remove-domain.template.js",
+    "templateFileTS": "remove-domain.template.ts",
+    "handlerMethod": "handleHostingWebsitesRemoveDomain",
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_websites_start-setup",
+    "title": "Start website setup (renamed to hosting_websites_create)",
+    "annotations": {
+      "title": "Start website setup (renamed to hosting_websites_create)",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "topic": "hosting",
+    "description": "Renamed to hosting_websites_create. This name still runs so older skills keep working, and will be removed in a future release.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Hosting order ID. List orders to find available IDs."
+        },
+        "type": {
+          "type": "string",
+          "description": "Website type, as hosting_websites_create takes it."
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain for the website, as hosting_websites_create takes it."
+        },
+        "datacenter_code": {
+          "type": "string",
+          "description": "Datacenter code, as hosting_websites_create takes it."
+        },
+        "wordpress": {
+          "type": "object",
+          "description": "WordPress install settings, as hosting_websites_create takes them."
+        }
+      },
+      "required": [
+        "order_id"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "start-setup.template.js",
+    "templateFileTS": "start-setup.template.ts",
+    "handlerMethod": "handleHostingWebsitesStartSetup",
+    "group": "hosting",
+    "hidden": true
+  },
   {
     "name": "hosting_import-wordpress-website",
     "title": "Import WordPress website",
@@ -1629,7 +1800,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_list-website-parked",
@@ -1664,7 +1836,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_create-website-parked",
@@ -1704,7 +1877,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_delete-website-parked",
@@ -1745,7 +1919,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_list-website-subdomains",
@@ -1780,7 +1955,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_create-website-subdomain",
@@ -1828,7 +2004,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_delete-website-subdomain",
@@ -1869,7 +2046,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_verify-ownership",
@@ -3546,14 +3724,14 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_websites_start-setup",
+    "name": "hosting_websites_create",
     "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 (`hosting_websites_list-setups`) with the `domain` filter every 10 to 15\nseconds and wait for `status: completed` before uploading files, deploying or creating\ndatabases.\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_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)\ncreate a headless website; `headless_wordpress` additionally installs WordPress into the\n`cms` directory of the website root with generated credentials. `headless_empty` installs\nnothing: WordPress can be added later through\n`POST /api/hosting/v1/accounts/{username}/wordpress/installations`\n(`wordpress_installations_install`) with `type: headless`.\n\nOmit `domain` to set the website up on a generated temporary free subdomain. To know the\nfree subdomain before the call, so a timed-out call can be looked up and retried on the\nsame domain, generate one through `POST /api/hosting/v1/domains/free-subdomains`\n(`hosting_domains_generate-free-subdomain`) and send it as `domain`. It is accepted for\n24 hours, only from the client that generated it.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\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.",
+    "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 (`hosting_websites_list-setups`) with the `domain` filter every 10 to 15\nseconds and wait for `status: completed` before uploading files, deploying or creating\ndatabases.\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_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)\ncreate a headless website; `headless_wordpress` additionally installs WordPress into the\n`cms` directory of the website root with generated credentials. `headless_empty` installs\nnothing: WordPress can be added later through\n`POST /api/hosting/v1/accounts/{username}/wordpress/installations`\n(`wordpress_installations_install`) with `type: headless`.\n\nOmit `domain` to set the website up on a generated temporary free subdomain; the created\nsetup returns it as `domain`. REST clients that need to know the free subdomain before the\ncall, so a timed-out call can be looked up and retried on the same domain, can generate\none through `POST /api/hosting/v1/domains/free-subdomains` and send it as `domain`. It is\naccepted for 24 hours, only from the client that generated it.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\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": {
@@ -3576,7 +3754,7 @@ export default [
         },
         "domain": {
           "type": "string",
-          "description": "Customer-owned domain, or a free subdomain you generated through `POST /api/hosting/v1/domains/free-subdomains` (`hosting_domains_generate-free-subdomain`) in the last 24 hours. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain."
+          "description": "Customer-owned domain. Omit or `null` to set the website up on a generated temporary free subdomain. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. A free subdomain generated through `POST /api/hosting/v1/domains/free-subdomains` in the last 24 hours is also accepted."
         },
         "datacenter_code": {
           "type": "string",
@@ -4271,7 +4449,7 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_websites_create",
+    "name": "hosting_websites_create-deprecated",
     "title": "Create website",
     "annotations": {
       "title": "Create website",
@@ -4307,7 +4485,8 @@ export default [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_websites_deploy-static-site-archive",

package/src/core/tools/hosting.ts

@@ -366,6 +366,177 @@ const tools: OpenApiTool[] = [
     "handlerMethod": "handleHostingCacheClear",
     "group": "hosting"
   },
+  {
+    "name": "hosting_websites_list-domains",
+    "title": "List website parked (alias) domains and subdomains",
+    "annotations": {
+      "title": "List website parked (alias) domains and subdomains",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "topic": "hosting",
+    "description": "List the extra domains of a website: its parked (alias) domains, which show the same site under another domain name, and its subdomains (e.g. blog.example.com), with each one's root directory. parked items have domain (a domain name or an IP address) and type (domain or ip); subdomains items have domain (the full name), subdomain (the prefix) and root_directory. A list that cannot be read comes back as { error } and the other is still returned. To add or remove one use hosting_websites_add-domain or hosting_websites_remove-domain. Works for Shared and Cloud hosting websites.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)"
+        }
+      },
+      "required": [
+        "domain"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "replacesHidden": true,
+    "templateFile": "list-domains.template.js",
+    "templateFileTS": "list-domains.template.ts",
+    "handlerMethod": "handleHostingWebsitesListDomains",
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_websites_add-domain",
+    "title": "Add a parked (alias) domain or subdomain to a website",
+    "annotations": {
+      "title": "Add a parked (alias) domain or subdomain to a website",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "topic": "hosting",
+    "description": "Add a domain to an existing website: type parked adds a parked (alias) domain, a second domain name (or an IP address) that shows the same site; type subdomain creates a subdomain such as blog.example.com with its own directory. For a parked domain the domain must be owned by the account or already point to the website: check a domain from outside the account with hosting_domains_verify-ownership first. www belongs to the main domain: do not add it as a subdomain. To create a new website use hosting_websites_create instead. Works for Shared and Cloud hosting websites.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)"
+        },
+        "type": {
+          "type": "string",
+          "enum": [
+            "parked",
+            "subdomain"
+          ],
+          "description": "parked: an alias domain that shows the same website; subdomain: a subdomain of the website's domain."
+        },
+        "name": {
+          "type": "string",
+          "description": "For parked: the domain name or IP address to park (e.g., example.net). For subdomain: the prefix (e.g., blog) or the full name (e.g., blog.example.com)."
+        },
+        "directory": {
+          "type": "string",
+          "description": "Subdomains only: the subdomain's directory relative to the website root."
+        },
+        "usePublicDirectory": {
+          "type": "boolean",
+          "description": "Subdomains only: serve the subdomain from the website's public directory instead of its own directory."
+        }
+      },
+      "required": [
+        "domain",
+        "type",
+        "name"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "replacesHidden": true,
+    "templateFile": "add-domain.template.js",
+    "templateFileTS": "add-domain.template.ts",
+    "handlerMethod": "handleHostingWebsitesAddDomain",
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_websites_remove-domain",
+    "title": "Remove a parked (alias) domain or subdomain from a website",
+    "annotations": {
+      "title": "Remove a parked (alias) domain or subdomain from a website",
+      "readOnlyHint": false,
+      "destructiveHint": true
+    },
+    "topic": "hosting",
+    "description": "Remove a parked (alias) domain or a subdomain from a website. Pass its name as hosting_websites_list-domains shows it: a parked domain, or a subdomain's full name or prefix; the tool finds which one it is. To delete a whole website use hosting_websites_delete. Works for Shared and Cloud hosting websites.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name of the website, exactly as listed on the account and without www. (e.g., example.com)"
+        },
+        "name": {
+          "type": "string",
+          "description": "The parked domain (e.g., example.net) or the subdomain, as its full name (e.g., blog.example.com) or prefix (e.g., blog), to remove."
+        }
+      },
+      "required": [
+        "domain",
+        "name"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "replacesHidden": true,
+    "templateFile": "remove-domain.template.js",
+    "templateFileTS": "remove-domain.template.ts",
+    "handlerMethod": "handleHostingWebsitesRemoveDomain",
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_websites_start-setup",
+    "title": "Start website setup (renamed to hosting_websites_create)",
+    "annotations": {
+      "title": "Start website setup (renamed to hosting_websites_create)",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "topic": "hosting",
+    "description": "Renamed to hosting_websites_create. This name still runs so older skills keep working, and will be removed in a future release.",
+    "method": "",
+    "path": "",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "order_id": {
+          "type": "integer",
+          "description": "Hosting order ID. List orders to find available IDs."
+        },
+        "type": {
+          "type": "string",
+          "description": "Website type, as hosting_websites_create takes it."
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain for the website, as hosting_websites_create takes it."
+        },
+        "datacenter_code": {
+          "type": "string",
+          "description": "Datacenter code, as hosting_websites_create takes it."
+        },
+        "wordpress": {
+          "type": "object",
+          "description": "WordPress install settings, as hosting_websites_create takes them."
+        }
+      },
+      "required": [
+        "order_id"
+      ]
+    },
+    "security": [],
+    "custom": true,
+    "templateFile": "start-setup.template.js",
+    "templateFileTS": "start-setup.template.ts",
+    "handlerMethod": "handleHostingWebsitesStartSetup",
+    "group": "hosting",
+    "hidden": true
+  },
   {
     "name": "hosting_import-wordpress-website",
     "title": "Import WordPress website",
@@ -1646,7 +1817,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_list-website-parked",
@@ -1681,7 +1853,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_create-website-parked",
@@ -1721,7 +1894,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_delete-website-parked",
@@ -1762,7 +1936,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_list-website-subdomains",
@@ -1797,7 +1972,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_create-website-subdomain",
@@ -1845,7 +2021,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_delete-website-subdomain",
@@ -1886,7 +2063,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_domains_verify-ownership",
@@ -3563,14 +3741,14 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_websites_start-setup",
+    "name": "hosting_websites_create",
     "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 (`hosting_websites_list-setups`) with the `domain` filter every 10 to 15\nseconds and wait for `status: completed` before uploading files, deploying or creating\ndatabases.\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_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)\ncreate a headless website; `headless_wordpress` additionally installs WordPress into the\n`cms` directory of the website root with generated credentials. `headless_empty` installs\nnothing: WordPress can be added later through\n`POST /api/hosting/v1/accounts/{username}/wordpress/installations`\n(`wordpress_installations_install`) with `type: headless`.\n\nOmit `domain` to set the website up on a generated temporary free subdomain. To know the\nfree subdomain before the call, so a timed-out call can be looked up and retried on the\nsame domain, generate one through `POST /api/hosting/v1/domains/free-subdomains`\n(`hosting_domains_generate-free-subdomain`) and send it as `domain`. It is accepted for\n24 hours, only from the client that generated it.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\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.",
+    "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 (`hosting_websites_list-setups`) with the `domain` filter every 10 to 15\nseconds and wait for `status: completed` before uploading files, deploying or creating\ndatabases.\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_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)\ncreate a headless website; `headless_wordpress` additionally installs WordPress into the\n`cms` directory of the website root with generated credentials. `headless_empty` installs\nnothing: WordPress can be added later through\n`POST /api/hosting/v1/accounts/{username}/wordpress/installations`\n(`wordpress_installations_install`) with `type: headless`.\n\nOmit `domain` to set the website up on a generated temporary free subdomain; the created\nsetup returns it as `domain`. REST clients that need to know the free subdomain before the\ncall, so a timed-out call can be looked up and retried on the same domain, can generate\none through `POST /api/hosting/v1/domains/free-subdomains` and send it as `domain`. It is\naccepted for 24 hours, only from the client that generated it.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\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": {
@@ -3593,7 +3771,7 @@ const tools: OpenApiTool[] = [
         },
         "domain": {
           "type": "string",
-          "description": "Customer-owned domain, or a free subdomain you generated through `POST /api/hosting/v1/domains/free-subdomains` (`hosting_domains_generate-free-subdomain`) in the last 24 hours. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain."
+          "description": "Customer-owned domain. Omit or `null` to set the website up on a generated temporary free subdomain. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. A free subdomain generated through `POST /api/hosting/v1/domains/free-subdomains` in the last 24 hours is also accepted."
         },
         "datacenter_code": {
           "type": "string",
@@ -4288,7 +4466,7 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_websites_create",
+    "name": "hosting_websites_create-deprecated",
     "title": "Create website",
     "annotations": {
       "title": "Create website",
@@ -4324,7 +4502,8 @@ const tools: OpenApiTool[] = [
         "apiToken": []
       }
     ],
-    "group": "hosting"
+    "group": "hosting",
+    "hidden": true
   },
   {
     "name": "hosting_websites_deploy-static-site-archive",

package/src/core/tools/wordpress.js

@@ -427,7 +427,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/orders/{order_id}/onboardings\n(`hosting_websites_start-setup`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_start-setup` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must already be headless: the headless\ninstall rewrites the root `.htaccess`, so on any other website the request is\nrejected with 422.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (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\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that 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.",
+    "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/orders/{order_id}/onboardings\n(`hosting_websites_create`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_create` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must already be headless: the headless\ninstall rewrites the root `.htaccess`, so on any other website the request is\nrejected with 422.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (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\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that 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": {
@@ -451,7 +451,7 @@ export default [
         },
         "type": {
           "type": "string",
-          "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_start-setup`) with `type: headless_empty`; any other website is rejected with 422.",
+          "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_create`) with `type: headless_empty`; any other website is rejected with 422.",
           "enum": [
             "default",
             "headless"

package/src/core/tools/wordpress.ts

@@ -444,7 +444,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/orders/{order_id}/onboardings\n(`hosting_websites_start-setup`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_start-setup` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must already be headless: the headless\ninstall rewrites the root `.htaccess`, so on any other website the request is\nrejected with 422.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (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\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that 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.",
+    "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/orders/{order_id}/onboardings\n(`hosting_websites_create`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_create` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must already be headless: the headless\ninstall rewrites the root `.htaccess`, so on any other website the request is\nrejected with 422.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (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\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that 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": {
@@ -468,7 +468,7 @@ const tools: OpenApiTool[] = [
         },
         "type": {
           "type": "string",
-          "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_start-setup`) with `type: headless_empty`; any other website is rejected with 422.",
+          "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_create`) with `type: headless_empty`; any other website is rejected with 422.",
           "enum": [
             "default",
             "headless"

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.agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.24.3', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.25.1', 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.agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.24.3', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.25.1', tools, instructions });