hostinger-api-mcp 0.2.4 → 0.2.6

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_listNode.jsBuildsV1": {
+    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_createNode.jsBuildFromArchiveV1": {
+    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_getNode.jsBuildLogsV1": {
+    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.
 
@@ -1173,6 +1368,99 @@ websites list endpoint to see when your new website becomes available.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Install WordPress on an existing website.
+
+The website must already exist before calling this endpoint. To create a new
+website first, use POST /api/hosting/v1/websites and poll
+GET /api/hosting/v1/websites until it appears.
+
+Call GET /api/hosting/v1/wordpress/installations filtered by username and
+domain before proceeding to check whether WordPress is already installed on
+the target domain/path. If WordPress already exists and `overwrite` is false
+(the default), the async job will fail.
+
+This operation is asynchronous: a successful response only means the install
+job has been queued, not that WordPress is ready. Installation typically
+takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered
+by username and domain to track progress. When the installation appears in
+that list, WordPress is ready.
+   */
+  "hosting_installWordPressV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain of the existing website where WordPress will be installed
+       */
+      domain: string;
+      /**
+       * Title of the WordPress site
+       */
+      site_title: string;
+      /**
+       * WordPress locale. Defaults to en_US when omitted.
+       */
+      language?: string;
+      /**
+       * Relative directory to install WordPress into. Defaults to the website root when omitted.
+       */
+      directory?: string;
+      /**
+       * When false (default), does not replace an existing installation. If WordPress is already installed on the domain/path, the async install job fails unless true.
+       */
+      overwrite?: boolean;
+      /**
+       * WordPress core auto-update policy
+       */
+      auto_updates?: string;
+      /**
+       * WordPress core version to install. If omitted, the latest core version compatible with the account vhost PHP version is selected.
+       */
+      version?: string;
+      /**
+       * WordPress admin credentials
+       */
+      credentials: object;
+      /**
+       * Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.
+       */
+      database?: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * List WordPress installations accessible to the authenticated client.
+
+Use this endpoint to discover existing WordPress installations and to poll
+for installation status after calling the install endpoint. When a newly
+requested installation appears in this list, WordPress is ready. Filter by
+username and domain to narrow results to a specific website.
+
+Each installation includes a `valid` flag and, when invalid, a
+`validationError` describing why.
+   */
+  "hosting_listWordPressInstallationsV1": {
+    params: {
+      /**
+       * Filter by specific username
+       */
+      username?: string;
+      /**
+       * Filter by domain name (exact match)
+       */
+      domain?: string;
+      /**
+       * Filter by ownership type. Defaults to "owned". Use "all" to include both owned and managed installations.
+       */
+      ownership?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Delete a contact with the specified UUID.