hostinger-api-mcp 0.2.5 → 0.2.7

package/src/core/tools/hosting.ts

@@ -267,6 +267,40 @@ const tools: OpenApiTool[] = [
     "handlerMethod": "handleShowJsDeploymentLogs",
     "group": "hosting"
   },
+  {
+    "name": "hosting_changeDatabasePasswordV1",
+    "description": "Changes the password for the specified database user.\n\nThe database name must be the full name returned by the list databases endpoint.\nThe password must also be updated in any website configuration that uses this database.",
+    "method": "PATCH",
+    "path": "/api/hosting/v1/accounts/{username}/databases/{name}/change-password",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "name": {
+          "type": "string",
+          "description": "Full database name as returned by the list databases endpoint."
+        },
+        "password": {
+          "type": "string",
+          "description": "New database user password."
+        }
+      },
+      "required": [
+        "username",
+        "name",
+        "password"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listAccountDatabasesV1",
     "description": "Returns a paginated list of databases for the specified account.\n\nUse the domain and is_assigned filters to find databases assigned to a specific domain.",
@@ -384,6 +418,64 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_repairDatabaseV1",
+    "description": "Repairs corrupted database tables asynchronously.\n\nUse when database errors, crashes, or corruption are reported.\nThe database name must be the full name returned by the list databases endpoint.",
+    "method": "PATCH",
+    "path": "/api/hosting/v1/accounts/{username}/databases/{name}/repair",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "name": {
+          "type": "string",
+          "description": "Full database name as returned by the list databases endpoint."
+        }
+      },
+      "required": [
+        "username",
+        "name"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_getPhpMyAdminLinkV1",
+    "description": "Returns a direct sign-on link to phpMyAdmin for the specified database.\n\nUse this when a visual database interface is needed for SQL queries, imports, exports, or table management.\nThe database name must be the full name returned by the list databases endpoint.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/databases/{name}/phpmyadmin-link",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "name": {
+          "type": "string",
+          "description": "Full database name as returned by the list databases endpoint."
+        }
+      },
+      "required": [
+        "username",
+        "name"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listAvailableDatacentersV1",
     "description": "Retrieve a list of datacenters available for setting up hosting plans\nbased on available datacenter capacity and hosting plan of your order.\nThe first item in the list is the best match for your specific order\nrequirements.",
@@ -651,6 +743,179 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNodeJSBuildsV1",
+    "description": "Retrieve a paginated list of Node.js build processes for a specific website.\n\nEach build represents a single run of the Node.js build pipeline. Use the `states`\nquery parameter to filter results by build state (pending, running, completed, failed).\nUse the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "page": {
+          "type": "integer",
+          "description": "Page number"
+        },
+        "per_page": {
+          "type": "integer",
+          "description": "Number of items per page"
+        },
+        "states": {
+          "type": "array",
+          "description": "Build states to filter by",
+          "items": {
+            "type": "string",
+            "description": "states parameter",
+            "enum": [
+              "pending",
+              "running",
+              "completed",
+              "failed"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_createNodeJSBuildFromArchiveV1",
+    "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
+    "method": "POST",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "archive": {
+          "type": "string",
+          "description": "Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB"
+        },
+        "node_version": {
+          "type": "integer",
+          "description": "Node.js version override (auto-detected from package.json if omitted)",
+          "enum": [
+            18,
+            20,
+            22,
+            24
+          ]
+        },
+        "app_type": {
+          "type": "string",
+          "description": "Node.js application type override",
+          "enum": [
+            "create-react-app",
+            "vite",
+            "angular",
+            "react",
+            "vue",
+            "parcel",
+            "express",
+            "fastify",
+            "nest"
+          ]
+        },
+        "root_directory": {
+          "type": "string",
+          "description": "Application root directory override (where package.json is located) relative to public_html"
+        },
+        "output_directory": {
+          "type": "string",
+          "description": "Build output directory override relative to the root directory"
+        },
+        "build_script": {
+          "type": "string",
+          "description": "Build script override"
+        },
+        "entry_file": {
+          "type": "string",
+          "description": "Main entry point file override"
+        },
+        "package_manager": {
+          "type": "string",
+          "description": "Package manager override",
+          "enum": [
+            "npm",
+            "yarn",
+            "pnpm"
+          ]
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "archive"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_getNodeJSBuildLogsV1",
+    "description": "Retrieve logs from a specific Node.js build process.\n\nTo stream live output while a build is running, poll this endpoint repeatedly\nwhile the build state is `running`, passing the previously returned `lines` count\nas `from_line` to fetch only new output since the last call.\nLog content may contain ANSI escape sequences (color codes).",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/{uuid}/logs",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "uuid": {
+          "type": "string",
+          "description": "Build UUID"
+        },
+        "from_line": {
+          "type": "integer",
+          "description": "Line from which to start retrieving logs"
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "uuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listOrdersV1",
     "description": "Retrieve a paginated list of orders accessible to the authenticated client.\n\nThis endpoint returns orders of your hosting accounts as well as orders\nof other client hosting accounts that have shared access with you.\n\nUse the available query parameters to filter results by order statuses\nor specific order IDs for more targeted results.",

package/src/servers/all.js

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

package/src/servers/all.ts

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

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: '0.2.5', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '0.2.7', tools });

package/src/servers/hosting.js

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

package/src/servers/hosting.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '0.2.5', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '0.2.7', 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: '0.2.5', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '0.2.7', tools });

package/types.d.ts

@@ -796,6 +796,30 @@ Use this endpoint to view which domains use specific contact profiles.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Changes the password for the specified database user.
+
+The database name must be the full name returned by the list databases endpoint.
+The password must also be updated in any website configuration that uses this database.
+   */
+  "hosting_changeDatabasePasswordV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Full database name as returned by the list databases endpoint.
+       */
+      name: string;
+      /**
+       * New database user password.
+       */
+      password: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Returns a paginated list of databases for the specified account.
 
@@ -881,6 +905,46 @@ The database name must be the full name returned by the list databases endpoint.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Repairs corrupted database tables asynchronously.
+
+Use when database errors, crashes, or corruption are reported.
+The database name must be the full name returned by the list databases endpoint.
+   */
+  "hosting_repairDatabaseV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Full database name as returned by the list databases endpoint.
+       */
+      name: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Returns a direct sign-on link to phpMyAdmin for the specified database.
+
+Use this when a visual database interface is needed for SQL queries, imports, exports, or table management.
+The database name must be the full name returned by the list databases endpoint.
+   */
+  "hosting_getPhpMyAdminLinkV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Full database name as returned by the list databases endpoint.
+       */
+      name: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a list of datacenters available for setting up hosting plans
 based on available datacenter capacity and hosting plan of your order.
@@ -1071,6 +1135,137 @@ Skip this verification when using Hostinger's free subdomains (*.hostingersite.c
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Retrieve a paginated list of Node.js build processes for a specific website.
+
+Each build represents a single run of the Node.js build pipeline. Use the `states`
+query parameter to filter results by build state (pending, running, completed, failed).
+Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.
+   */
+  "hosting_listNodeJSBuildsV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+      /**
+       * Build states to filter by
+       */
+      states?: array;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.
+
+This is the recommended single-step approach for deploying a Node.js application.
+The archive is uploaded to the website's file storage, build settings are auto-detected
+from the package.json inside the archive, and the build process starts automatically.
+Optional override fields take precedence over auto-detected values.
+Maximum archive size is 50MB.
+
+Before archiving, exclude `node_modules/` and any build output directories
+(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build
+process runs the install step automatically, and including them unnecessarily
+increases the archive size. This also helps keep the archive well under the 50MB limit.
+
+Example (zip):
+```
+zip -r archive.zip . --exclude "node_modules/*" --exclude "dist/*"
+```
+
+The returned build `uuid` can be used to poll progress and retrieve logs via
+the `Get Node.js Build Logs` endpoint.
+   */
+  "hosting_createNodeJSBuildFromArchiveV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB
+       */
+      archive: string;
+      /**
+       * Node.js version override (auto-detected from package.json if omitted)
+       */
+      node_version?: number;
+      /**
+       * Node.js application type override
+       */
+      app_type?: string;
+      /**
+       * Application root directory override (where package.json is located) relative to public_html
+       */
+      root_directory?: string;
+      /**
+       * Build output directory override relative to the root directory
+       */
+      output_directory?: string;
+      /**
+       * Build script override
+       */
+      build_script?: string;
+      /**
+       * Main entry point file override
+       */
+      entry_file?: string;
+      /**
+       * Package manager override
+       */
+      package_manager?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve logs from a specific Node.js build process.
+
+To stream live output while a build is running, poll this endpoint repeatedly
+while the build state is `running`, passing the previously returned `lines` count
+as `from_line` to fetch only new output since the last call.
+Log content may contain ANSI escape sequences (color codes).
+   */
+  "hosting_getNodeJSBuildLogsV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Build UUID
+       */
+      uuid: string;
+      /**
+       * Line from which to start retrieving logs
+       */
+      from_line?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a paginated list of orders accessible to the authenticated client.