hostinger-api-mcp 1.63.3 → 2.0.0

package/src/core/instructions.js

@@ -1,2 +1,2 @@
 // Auto-generated server instructions
-export default "Hostinger API notes for agents. Tool descriptions are authoritative for request shapes; read them before calling.\n\nDatabases (web hosting, hosting_* tools)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_listAccountDatabasesV1 (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_createDatabaseRemoteConnectionV1. Never use it from the app.\n- Agency Plan (agency-hosting_* tools) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read tool with backoff (seconds, then minutes). Never re-send the write.\n- hosting_createWebsiteV1 -> poll hosting_listWebsitesV1 until the domain appears (a few minutes).\n- hosting_startNode_jsBuildV1 -> hosting_getNode_jsBuildDetailsV1; logs via hosting_getNodeJSBuildLogsV1; on failure hosting_analyseFailedNode_jsBuildV1.\n- hosting_installWordPressV1 and WordPress plugin/theme/core jobs -> poll hosting_listWordPressInstallationsV1.\n- agency-hosting_createANewWebsiteV1 -> poll agency-hosting_getWebsiteSetupStatusV1 with setup_uuid; other Agency Plan jobs -> agency-hosting_listWebsiteProcessesV1.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_replaceNode_jsEnvironmentVariablesV1 (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
+export default "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_listAccountDatabasesV1 (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_createDatabaseRemoteConnectionV1. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_createWebsiteV1 -> poll hosting_listWebsitesV1 until the domain appears (a few minutes).\n- hosting_startNode_jsBuildV1 -> hosting_getNode_jsBuildDetailsV1; logs via hosting_getNodeJSBuildLogsV1; on failure hosting_analyseFailedNode_jsBuildV1.\n- hosting_installWordPressV1 and WordPress plugin/theme/core jobs -> poll hosting_listWordPressInstallationsV1.\n- agency-hosting_createANewWebsiteV1 -> poll agency-hosting_getWebsiteSetupStatusV1 with setup_uuid; other Agency Plan jobs -> agency-hosting_listWebsiteProcessesV1.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_replaceNode_jsEnvironmentVariablesV1 (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";

package/src/core/instructions.ts

@@ -1,3 +1,3 @@
 // Auto-generated server instructions
-const instructions: string = "Hostinger API notes for agents. Tool descriptions are authoritative for request shapes; read them before calling.\n\nDatabases (web hosting, hosting_* tools)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_listAccountDatabasesV1 (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_createDatabaseRemoteConnectionV1. Never use it from the app.\n- Agency Plan (agency-hosting_* tools) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read tool with backoff (seconds, then minutes). Never re-send the write.\n- hosting_createWebsiteV1 -> poll hosting_listWebsitesV1 until the domain appears (a few minutes).\n- hosting_startNode_jsBuildV1 -> hosting_getNode_jsBuildDetailsV1; logs via hosting_getNodeJSBuildLogsV1; on failure hosting_analyseFailedNode_jsBuildV1.\n- hosting_installWordPressV1 and WordPress plugin/theme/core jobs -> poll hosting_listWordPressInstallationsV1.\n- agency-hosting_createANewWebsiteV1 -> poll agency-hosting_getWebsiteSetupStatusV1 with setup_uuid; other Agency Plan jobs -> agency-hosting_listWebsiteProcessesV1.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_replaceNode_jsEnvironmentVariablesV1 (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
+const instructions: string = "Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.\n\nDatabases (web hosting, hosting_* operations)\n- MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.\n- The `host` from hosting_listAccountDatabasesV1 (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_createDatabaseRemoteConnectionV1. Never use it from the app.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- hosting_createWebsiteV1 -> poll hosting_listWebsitesV1 until the domain appears (a few minutes).\n- hosting_startNode_jsBuildV1 -> hosting_getNode_jsBuildDetailsV1; logs via hosting_getNodeJSBuildLogsV1; on failure hosting_analyseFailedNode_jsBuildV1.\n- hosting_installWordPressV1 and WordPress plugin/theme/core jobs -> poll hosting_listWordPressInstallationsV1.\n- agency-hosting_createANewWebsiteV1 -> poll agency-hosting_getWebsiteSetupStatusV1 with setup_uuid; other Agency Plan jobs -> agency-hosting_listWebsiteProcessesV1.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- Node.js apps read them from environment variables: set the full set with hosting_replaceNode_jsEnvironmentVariablesV1 (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
 export default instructions;

package/src/core/runtime.js

@@ -17,6 +17,7 @@ import { OAuthProvider, getEnvToken } from "./oauth.js";
 import * as tus from "tus-js-client";
 import fs from "fs";
 import path from "path";
+import { META_TOOLS, searchOperations, renderSearch, findOperation, runSteps } from "./catalog.js";
 
 // Load environment variables
 dotenvConfig({ quiet: true });
@@ -44,7 +45,7 @@ const SECURITY_SCHEMES = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.54.1
+ * Generated from OpenAPI spec version 1.54.2
  */
 class MCPServer {
   constructor({ name, version, tools, instructions }) {
@@ -54,7 +55,7 @@ class MCPServer {
     this.toolList = tools;
     this.instructions = instructions;
     this.server = null;
-    this.tools = new Map();
+    this.operations = new Map();
     this.debug = process.env.DEBUG === "true";
     this.baseUrl = process.env.API_BASE_URL || "https://developers.hostinger.com";
     this.headers = this.parseHeaders(process.env.API_HEADERS || "");
@@ -115,20 +116,13 @@ class MCPServer {
    * This runs before the server is connected, so don't log here
    */
   initializeTools() {
-    // Initialize each tool in the tools map
+    // The operations are the catalog behind search/execute; they are not listed as tools.
     for (const tool of this.toolList) {
-      this.tools.set(tool.name, {
-        name: tool.name,
-        title: tool.title,
-        description: tool.description,
-        inputSchema: tool.inputSchema,
-        annotations: tool.annotations,
-        // Don't include security at the tool level
-      });
+      this.operations.set(tool.name, tool);
     }
 
     // Don't log here, we're not connected yet
-    console.error(`Initialized ${this.tools.size} tools`);
+    console.error(`Loaded ${this.operations.size} operations`);
   }
 
   /**
@@ -149,97 +143,79 @@ class MCPServer {
     // Handle tool listing requests
     this.server.setRequestHandler(ListToolsRequestSchema, async () => {
       this.log('debug', "Handling ListTools request");
-      // Return tools in the format expected by MCP SDK
-      return {
-        tools: Array.from(this.tools.entries()).map(([id, tool]) => ({
-          id,
-          ...tool,
-        })),
-      };
+      return { tools: META_TOOLS };
     });
 
-    // Handle tool execution requests
     this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
-      const { name, arguments: params } = request.params;
-      this.log('debug', "Handling CallTool request", { name, params });
-
-      let toolName;
-      let toolDetails;
-
-      // Find the requested tool
-      for (const [tid, tool] of this.tools.entries()) {
-        if (tool.name === name) {
-          toolName = name;
-          break;
-        }
-      }
+      const { name } = request.params;
+      const args = request.params.arguments ?? {};
+      this.log('debug', "Handling CallTool request", { name, args });
 
       // An unknown tool is a protocol error, not a tool execution error: the
       // model cannot self-correct its way out of a name the server does not
-      // have. -32602 is what the spec's example and the SDK's own McpServer
-      // use; a plain Error would go out as -32603 instead.
-      if (!toolName) {
+      // have. -32602 is what the spec's example and the SDK's own McpServer use.
+      if (!META_TOOLS.some(t => t.name === name)) {
         throw new McpError(ErrorCode.InvalidParams, `Tool not found: ${name}`);
       }
 
-      toolDetails = this.toolList.find(t => t.name === toolName);
-      if (!toolDetails) {
-        throw new McpError(ErrorCode.InternalError, `Tool details not found for ID: ${toolName}`);
-      }
-
+      // Everything below is a tool execution: failures (bad input, unknown
+      // operation, API errors) come back inside the result with isError: true.
       try {
-        this.log('info', `Executing tool: ${toolName}`);
-
-        let result;
-
-        if (toolDetails.custom) {
-          result = await this.executeCustomTool(toolDetails, params || {});
-        } else {
-          result = await this.executeApiCall(toolDetails, params || {});
+        if (name === 'search') {
+          const results = searchOperations(this.toolList, args.query, args.limit ?? undefined);
+          return { content: [{ type: "text", text: renderSearch(args.query, results) }] };
         }
 
-        // Return the result in the correct MCP format
-        return {
-          content: [
-            {
-              type: "text",
-              text: JSON.stringify(result)
-            }
-          ]
-        };
-
-      } catch (error) {
-        const errorMessage = error instanceof Error ? error.message : String(error);
-        this.log('error', `Error executing tool ${name}: ${errorMessage}`);
-
-        // MCP reports tool execution failures (API errors, bad input, business
-        // logic) inside the result with isError: true. Throwing here would turn
-        // them into JSON-RPC protocol errors instead, which the spec reserves
-        // for unknown tools and malformed requests — those are still thrown,
-        // above, before this try. The status stays in the text so the model can
-        // tell a retryable 429/503 from a 403 it should not retry.
-        let errorText = errorMessage;
-        if (error instanceof ApiExecutionError) {
-          const payload = error.responseData;
-          const body = payload === null || payload === undefined || payload === ''
-            ? errorMessage
-            : typeof payload === 'object' ? JSON.stringify(payload) : String(payload);
-          errorText = error.status ? `HTTP ${error.status}: ${body}` : body;
+        if (name === 'execute') {
+          const result = await this.executeOperation(args.operation, args.params ?? {});
+          return { content: [{ type: "text", text: JSON.stringify(result) }] };
         }
 
+        const batch = await runSteps(
+          args.steps,
+          (operation, params) => this.executeOperation(operation, params),
+          (error) => this.formatToolError(error),
+        );
         return {
-          isError: true,
-          content: [
-            {
-              type: "text",
-              text: errorText
-            }
-          ]
+          ...(batch.error ? { isError: true } : {}),
+          content: [{ type: "text", text: JSON.stringify(batch) }],
         };
+      } catch (error) {
+        const errorText = this.formatToolError(error);
+        this.log('error', `Error executing ${name}: ${errorText}`);
+        return { isError: true, content: [{ type: "text", text: errorText }] };
       }
     });
   }
 
+  /**
+   * Look an operation up in the catalog, check its required params, and run it
+   * as either a custom tool or a plain API call.
+   */
+  async executeOperation(operation, params) {
+    const tool = findOperation(this.operations, operation, params);
+    this.log('info', `Executing operation: ${tool.name}`);
+    return tool.custom
+      ? this.executeCustomTool(tool, params)
+      : this.executeApiCall(tool, params);
+  }
+
+  /**
+   * Text for an isError result. The status stays in the text so the model can
+   * tell a retryable 429/503 from a 403 it should not retry.
+   */
+  formatToolError(error) {
+    const errorMessage = error instanceof Error ? error.message : String(error);
+    if (!(error instanceof ApiExecutionError)) {
+      return errorMessage;
+    }
+    const payload = error.responseData;
+    const body = payload === null || payload === undefined || payload === ''
+      ? errorMessage
+      : typeof payload === 'object' ? JSON.stringify(payload) : String(payload);
+    return error.status ? `HTTP ${error.status}: ${body}` : body;
+  }
+
   async executeCustomTool(tool, params) {
     switch (tool.name) {
       case 'agency-hosting_deployNodeStaticWebsite':
@@ -2625,7 +2601,7 @@ class MCPServer {
 
       // Start the server
       const server = app.listen(port, host, () => {
-        this.log('info', `MCP Server with HTTP streaming transport started successfully with ${this.tools.size} tools`);
+        this.log('info', `MCP Server with HTTP streaming transport started successfully with ${META_TOOLS.length} tools`);
         this.log('info', `Listening on http://${host}:${port}`);
       });
 
@@ -2651,8 +2627,8 @@ class MCPServer {
       await this.server.connect(transport);
 
       // Now we can safely log via MCP
-      console.error(`Registered ${this.tools.size} tools`);
-      this.log('info', `MCP Server with stdio transport started successfully with ${this.tools.size} tools`);
+      console.error(`Registered ${META_TOOLS.length} tools`);
+      this.log('info', `MCP Server with stdio transport started successfully with ${META_TOOLS.length} tools`);
     } catch (error) {
       console.error("Failed to start MCP server:", error);
       process.exit(1);

package/src/core/runtime.ts

@@ -19,6 +19,8 @@ import axios,{ AxiosRequestConfig, AxiosError, AxiosResponse } from "axios";
 import * as tus from "tus-js-client";
 import fs from "fs";
 import path from "path";
+import { META_TOOLS, searchOperations, renderSearch, findOperation, runSteps } from "./catalog.js";
+import type { CatalogOperation } from "./catalog.js";
 
 // Load environment variables
 dotenvConfig({ quiet: true });
@@ -70,14 +72,14 @@ const SECURITY_SCHEMES: Record<string, SecurityScheme> = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.54.1
+ * Generated from OpenAPI spec version 1.54.2
  */
 class MCPServer {
   private readonly name: string;
   private readonly version: string;
   private readonly toolList: OpenApiTool[];
   private server: Server;
-  private tools: Map<string, Tool> = new Map();
+  private operations: Map<string, OpenApiTool> = new Map();
   private instructions?: string;
   private debug: boolean;
   private baseUrl: string;
@@ -150,20 +152,13 @@ class MCPServer {
    * This runs before the server is connected, so don't log here
    */
   private initializeTools(): void {
-    // Initialize each tool in the tools map
+    // The operations are the catalog behind search/execute; they are not listed as tools.
     for (const tool of this.toolList) {
-      this.tools.set(tool.name, {
-        name: tool.name,
-        title: tool.title,
-        description: tool.description,
-        inputSchema: tool.inputSchema,
-        annotations: tool.annotations,
-        // Don't include security at the tool level
-      });
+      this.operations.set(tool.name, tool);
     }
 
     // Don't log here, we're not connected yet
-    console.error(`Initialized ${this.tools.size} tools`);
+    console.error(`Loaded ${this.operations.size} operations`);
   }
 
   /**
@@ -184,97 +179,67 @@ class MCPServer {
     // Handle tool listing requests
     this.server.setRequestHandler(ListToolsRequestSchema, async () => {
       this.log('debug', "Handling ListTools request");
-      // Return tools in the format expected by MCP SDK
-      return {
-        tools: Array.from(this.tools.entries()).map(([id, tool]) => ({
-          id,
-          ...tool,
-        })),
-      };
+      return { tools: META_TOOLS };
     });
 
-    // Handle tool execution requests
     this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
-      const { name, arguments: params } = request.params;
-      this.log('debug', "Handling CallTool request", { name, params });
-
-      let toolName: string | undefined;
-      let toolDetails: OpenApiTool | undefined;
-
-      // Find the requested tool
-      for (const [tid, tool] of this.tools.entries()) {
-        if (tool.name === name) {
-          toolName = name;
-          break;
-        }
-      }
+      const { name } = request.params;
+      const args = (request.params.arguments ?? {}) as Record<string, any>;
+      this.log('debug', "Handling CallTool request", { name, args });
 
-      // An unknown tool is a protocol error, not a tool execution error: the
-      // model cannot self-correct its way out of a name the server does not
-      // have. -32602 is what the spec's example and the SDK's own McpServer
-      // use; a plain Error would go out as -32603 instead.
-      if (!toolName) {
+      if (!META_TOOLS.some(t => t.name === name)) {
         throw new McpError(ErrorCode.InvalidParams, `Tool not found: ${name}`);
       }
 
-      toolDetails = this.toolList.find(t => t.name === toolName);
-      if (!toolDetails) {
-        throw new McpError(ErrorCode.InternalError, `Tool details not found for ID: ${toolName}`);
-      }
-        
       try {
-        this.log('info', `Executing tool: ${toolName}`);
-
-        let result: any;
-        
-        if (toolDetails.custom) {
-          result = await this.executeCustomTool(toolDetails, params || {});
-        } else {
-          result = await this.executeApiCall(toolDetails, params || {});
+        if (name === 'search') {
+          const results = searchOperations(this.toolList, args.query, args.limit ?? undefined);
+          return { content: [{ type: "text", text: renderSearch(String(args.query), results) }] };
         }
 
-        // Return the result in correct MCP format
-        return {
-          content: [
-            {
-              type: "text",
-              text: JSON.stringify(result)
-            }
-          ]
-        };
-
-      } catch (error) {
-        const errorMessage = error instanceof Error ? error.message : String(error);
-        this.log('error', `Error executing tool ${toolName}: ${errorMessage}`);
-
-        // MCP reports tool execution failures (API errors, bad input, business
-        // logic) inside the result with isError: true. Throwing here would turn
-        // them into JSON-RPC protocol errors instead, which the spec reserves
-        // for unknown tools and malformed requests — those are still thrown,
-        // above, before this try. The status stays in the text so the model can
-        // tell a retryable 429/503 from a 403 it should not retry.
-        let errorText: string = errorMessage;
-        if (error instanceof ApiExecutionError) {
-          const payload = error.responseData;
-          const body = payload === null || payload === undefined || payload === ''
-            ? errorMessage
-            : typeof payload === 'object' ? JSON.stringify(payload) : String(payload);
-          errorText = error.status ? `HTTP ${error.status}: ${body}` : body;
+        if (name === 'execute') {
+          const result = await this.executeOperation(args.operation, args.params ?? {});
+          return { content: [{ type: "text", text: JSON.stringify(result) }] };
         }
 
+        const batch = await runSteps(
+          args.steps,
+          (operation, params) => this.executeOperation(operation, params),
+          (error) => this.formatToolError(error),
+        );
         return {
-          isError: true,
-          content: [
-            {
-              type: "text",
-              text: errorText
-            }
-          ]
+          ...(batch.error ? { isError: true } : {}),
+          content: [{ type: "text", text: JSON.stringify(batch) }],
         };
+      } catch (error) {
+        const errorText = this.formatToolError(error);
+        this.log('error', `Error executing ${name}: ${errorText}`);
+        return { isError: true, content: [{ type: "text", text: errorText }] };
       }
     });
   }
 
+  private async executeOperation(operation: unknown, params: unknown): Promise<any> {
+    const tool = findOperation(this.operations, operation, params);
+    const input = params as Record<string, any>;
+    this.log('info', `Executing operation: ${tool.name}`);
+    return tool.custom
+      ? this.executeCustomTool(tool, input)
+      : this.executeApiCall(tool, input);
+  }
+
+  private formatToolError(error: unknown): string {
+    const errorMessage = error instanceof Error ? error.message : String(error);
+    if (!(error instanceof ApiExecutionError)) {
+      return errorMessage;
+    }
+    const payload = error.responseData;
+    const body = payload === null || payload === undefined || payload === ''
+      ? errorMessage
+      : typeof payload === 'object' ? JSON.stringify(payload) : String(payload);
+    return error.status ? `HTTP ${error.status}: ${body}` : body;
+  }
+
   private async executeCustomTool(tool: OpenApiTool, params: Record<string, any>): Promise<any> {
     switch (tool.name) {
       case 'agency-hosting_deployNodeStaticWebsite':
@@ -2681,7 +2646,7 @@ class MCPServer {
 
       // Start the server
       const server = app.listen(port, host, () => {
-        this.log('info', `MCP Server with HTTP streaming transport started successfully with ${this.tools.size} tools`);
+        this.log('info', `MCP Server with HTTP streaming transport started successfully with ${META_TOOLS.length} tools`);
         this.log('info', `Listening on http://${host}:${port}`);
       });
 
@@ -2707,8 +2672,8 @@ class MCPServer {
       await this.server.connect(transport);
 
       // Now we can safely log via MCP
-      console.error(`Registered ${this.tools.size} tools`);
-      this.log('info', `MCP Server with stdio transport started successfully with ${this.tools.size} tools`);
+      console.error(`Registered ${META_TOOLS.length} tools`);
+      this.log('info', `MCP Server with stdio transport started successfully with ${META_TOOLS.length} tools`);
     } catch (error) {
       console.error("Failed to start MCP server:", error);
       process.exit(1);

package/src/core/tools/all.js

@@ -8566,7 +8566,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nProvide the domain name and associated order ID to create a new website.\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
+    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -8578,7 +8578,7 @@ export default [
         },
         "order_id": {
           "type": "integer",
-          "description": "ID of the associated order"
+          "description": "Hosting order ID to create this website on. Choose the order whose hosting plan should host the new website. List orders to find available IDs."
         },
         "datacenter_code": {
           "type": "string",

package/src/core/tools/all.ts

@@ -8580,7 +8580,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nProvide the domain name and associated order ID to create a new website.\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
+    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -8592,7 +8592,7 @@ const tools: OpenApiTool[] = [
         },
         "order_id": {
           "type": "integer",
-          "description": "ID of the associated order"
+          "description": "Hosting order ID to create this website on. Choose the order whose hosting plan should host the new website. List orders to find available IDs."
         },
         "datacenter_code": {
           "type": "string",

package/src/core/tools/hosting.js

@@ -3105,7 +3105,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nProvide the domain name and associated order ID to create a new website.\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
+    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -3117,7 +3117,7 @@ export default [
         },
         "order_id": {
           "type": "integer",
-          "description": "ID of the associated order"
+          "description": "Hosting order ID to create this website on. Choose the order whose hosting plan should host the new website. List orders to find available IDs."
         },
         "datacenter_code": {
           "type": "string",

package/src/core/tools/hosting.ts

@@ -3119,7 +3119,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nProvide the domain name and associated order ID to create a new website.\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
+    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation takes up to a few minutes to complete. Check the\nwebsites list endpoint to see when your new website becomes available.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -3131,7 +3131,7 @@ const tools: OpenApiTool[] = [
         },
         "order_id": {
           "type": "integer",
-          "description": "ID of the associated order"
+          "description": "Hosting order ID to create this website on. Choose the order whose hosting plan should host the new website. List orders to find available IDs."
         },
         "datacenter_code": {
           "type": "string",

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

package/src/servers/all.js

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.63.3', tools, instructions });
+startServer({ name: 'hostinger-api-mcp', version: '2.0.0', tools, instructions });

package/src/servers/all.ts

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.63.3', tools, instructions });
+startServer({ name: 'hostinger-api-mcp', version: '2.0.0', tools, instructions });

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