hostinger-api-mcp 1.43.0 → 1.44.0

package/types.d.ts

@@ -5,7 +5,7 @@
 
 export interface APITools {
   /**
-   * Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.
+   * Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.
    */
   "agency-hosting_deployNodeStaticWebsite": {
     params: {
@@ -26,7 +26,7 @@ export interface APITools {
   };
 
   /**
-   * Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.
+   * Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.
    */
   "agency-hosting_deployPhpApplication": {
     params: {
@@ -47,7 +47,7 @@ export interface APITools {
   };
 
   /**
-   * Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. The username will be automatically resolved from the domain.
+   * Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end. The username will be automatically resolved from the domain.
    */
   "hosting_importWordpressWebsite": {
     params: {
@@ -68,7 +68,7 @@ export interface APITools {
   };
 
   /**
-   * Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment.
+   * Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end.
    */
   "hosting_deployWordpressPlugin": {
     params: {
@@ -89,7 +89,7 @@ export interface APITools {
   };
 
   /**
-   * Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment.
+   * Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end.
    */
   "hosting_deployWordpressTheme": {
     params: {
@@ -114,7 +114,7 @@ export interface APITools {
   };
 
   /**
-   * Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress.
+   * Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress.
    */
   "hosting_deployJsApplication": {
     params: {
@@ -135,7 +135,7 @@ export interface APITools {
   };
 
   /**
-   * Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deployJsApplication instead. The archive will be extracted and deployed directly without any build steps. The username will be automatically resolved from the domain.
+   * Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deployJsApplication instead. The tool uploads the archive to the website's file browser over TUS and triggers deployment; the archive is extracted and deployed directly without any build steps. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. The username will be automatically resolved from the domain.
    */
   "hosting_deployStaticWebsite": {
     params: {
@@ -306,6 +306,55 @@ If this is the only domain on the website, unlinking leaves the website without
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Generate a file browser upload URL with authentication credentials for uploading files
+to an Agency Plan website's file storage.
+
+Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the
+website's file storage via the TUS resumable upload protocol (TUS 1.0.0). Send
+`X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.
+
+1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers
+   `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`.
+2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or
+   `PATCH` requests with an `upload-offset` header tracking progress) until complete.
+
+`relative_file_path` is the destination path inside the website's file storage, e.g.
+`app.zip`.
+
+Instead of a TUS client, plain `curl` also works:
+```
+FILE=app.zip
+SIZE=$(stat -f%z "$FILE")   # stat -c%s on Linux
+
+curl -i -X POST "{url}/${FILE}?override=true" \
+  -H "X-Auth: {auth_key}" \
+  -H "X-Auth-Rest: {rest_auth_key}" \
+  -H "Tus-Resumable: 1.0.0" \
+  -H "Upload-Length: ${SIZE}" \
+  -H "Upload-Offset: 0"
+# -> 201 Created
+
+curl -i -X PATCH "{url}/${FILE}?override=true" \
+  -H "X-Auth: {auth_key}" \
+  -H "X-Auth-Rest: {rest_auth_key}" \
+  -H "Tus-Resumable: 1.0.0" \
+  -H "Content-Type: application/offset+octet-stream" \
+  -H "Upload-Offset: 0" \
+  --data-binary "@${FILE}"
+# -> 204 No Content, Upload-Offset response header equals SIZE when done
+```
+   */
+  "agency-hosting_generateUploadURLV1": {
+    params: {
+      /**
+       * Agency Plan website UID
+       */
+      website_uid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Imports an Agency Plan website from an already-uploaded archive.
 
@@ -2977,6 +3026,59 @@ Skip this verification when using Hostinger's free subdomains (*.hostingersite.c
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Generate a file browser upload URL with authentication credentials
+for uploading files directly to a website's file storage.
+
+Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the
+website's `public_html` directory via the TUS resumable upload protocol (TUS 1.0.0).
+Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request
+below.
+
+1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers
+   `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`.
+2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or
+   `PATCH` requests with an `upload-offset` header tracking progress) until complete.
+
+`relative_file_path` is the destination path inside `public_html`, e.g. `app.zip`.
+
+Instead of a TUS client, plain `curl` also works:
+```
+FILE=app.zip
+SIZE=$(stat -f%z "$FILE")   # stat -c%s on Linux
+
+curl -i -X POST "{url}/${FILE}?override=true" \
+  -H "X-Auth: {auth_key}" \
+  -H "X-Auth-Rest: {rest_auth_key}" \
+  -H "Tus-Resumable: 1.0.0" \
+  -H "Upload-Length: ${SIZE}" \
+  -H "Upload-Offset: 0"
+# -> 201 Created
+
+curl -i -X PATCH "{url}/${FILE}?override=true" \
+  -H "X-Auth: {auth_key}" \
+  -H "X-Auth-Rest: {rest_auth_key}" \
+  -H "Tus-Resumable: 1.0.0" \
+  -H "Content-Type: application/offset+octet-stream" \
+  -H "Upload-Offset: 0" \
+  --data-binary "@${FILE}"
+# -> 204 No Content, Upload-Offset response header equals SIZE when done
+```
+   */
+  "hosting_generateUploadURLV1": {
+    params: {
+      /**
+       * Account username
+       */
+      username: string;
+      /**
+       * Website domain
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * List files and directories under a website's document root.
 
@@ -3082,9 +3184,79 @@ Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs`
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Start a Node.js build process using files already present on the website's file storage.
+
+WARNING: on success this overwrites the website's existing contents and cannot be
+undone — verify this is intended before calling this endpoint.
+
+The `source_type` must be `archive` and `source_options.archive_path` must point to an
+existing archive file on the server (relative to the website document root).
+Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.
+
+To auto-detect build settings from an archive before starting, first call the
+`Get Node.js Build Settings from Archive` endpoint. To upload an archive and start
+a build in one step, use the `Create Node.js Build from Archive` endpoint instead.
+
+The returned build `uuid` can be used to poll progress and retrieve logs via
+the `Get Node.js Build Logs` endpoint.
+   */
+  "hosting_startNode_jsBuildV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Node.js version
+       */
+      node_version: number;
+      /**
+       * Node.js application type
+       */
+      app_type: string;
+      /**
+       * Application root directory (where package.json is located) relative to public_html
+       */
+      root_directory: string;
+      /**
+       * Build output directory relative to the root directory
+       */
+      output_directory: string;
+      /**
+       * Build script that will be ran to build the application
+       */
+      build_script: string;
+      /**
+       * The main entry point file for the application
+       */
+      entry_file?: string;
+      /**
+       * Package manager
+       */
+      package_manager?: string;
+      /**
+       * The source type of the files
+       */
+      source_type: string;
+      /**
+       * Source-specific options
+       */
+      source_options: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.
 
+WARNING: on success this overwrites the website's existing contents and cannot be
+undone — verify this is intended before calling this endpoint.
+
 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.
@@ -3150,6 +3322,36 @@ the `Get Node.js Build Logs` endpoint.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Auto-detect Node.js build settings from a package.json inside an archive already on the server.
+
+Use this before calling `Start Node.js Build` to preview what settings will be used,
+or to let the user review and override values (framework, node version, root directory,
+output directory, build script) before committing to a build.
+
+The archive must already be present on the website's file storage. Use the
+`Generate Upload URL` endpoint to obtain credentials and upload the archive first.
+To upload an archive and start a build in one step without inspecting settings first,
+use the `Create Node.js Build from Archive` endpoint instead.
+   */
+  "hosting_getNode_jsBuildSettingsFromArchiveV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * The path to the archive file relative to the document root of the vhost
+       */
+      archive_path: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve logs from a specific Node.js build process.
 
@@ -3590,6 +3792,38 @@ websites list endpoint to see when your new website becomes available.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Deploy a static application from an archive file.
+
+WARNING: this overwrites the website's existing contents and cannot be undone —
+verify this is intended before calling this endpoint.
+
+This endpoint allows you to deploy a static application from an archive
+file that has been uploaded to the website's directory.
+
+This only works for static sites (pre-built HTML/CSS/JS with no build step). For
+Node.js applications, use `Create NodeJS build from archive` instead, or
+`Start Node.js build` if the archive is already uploaded. For WordPress sites,
+use `Import WordPress website`.
+   */
+  "hosting_deployStaticSiteArchiveV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Relative path to the archive file from website root directory
+       */
+      archive_path: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * This endpoint permanently removes a website and all of its data. This action
 cannot be undone. Before calling it, make sure the user understands the
@@ -7129,6 +7363,37 @@ detected installations once the scan completes.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Import WordPress website to the specified domain.
+
+WARNING: this overwrites the website's existing contents and cannot be undone —
+verify this is intended before calling this endpoint.
+
+This endpoint allows you to import a WordPress website from archive and
+database files that have been uploaded to the website's directory.
+   */
+  "hosting_importWordPressWebsiteV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Path to the WordPress archive file (relative to website root)
+       */
+      archive_path: string;
+      /**
+       * Path to the database SQL file (relative to website root)
+       */
+      sql_path: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Install WordPress on an existing website.
 
@@ -7521,6 +7786,34 @@ deactivation job has been queued.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Deploy a WordPress plugin from an already uploaded directory.
+
+This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website's directory.
+The plugin will be activated and made available in the WordPress admin panel.
+   */
+  "hosting_deployWordPressPluginV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Slug of the plugin
+       */
+      slug: string;
+      /**
+       * Relative path to the plugin directory from wp-content/plugins
+       */
+      plugin_path: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Install one or more plugins on an existing WordPress installation.
 
@@ -7751,6 +8044,38 @@ job has been queued.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Deploy a WordPress theme from an already uploaded directory.
+
+This endpoint allows you to deploy a WordPress theme that has been uploaded to the website's directory.
+The theme can be optionally activated after deployment.
+   */
+  "hosting_deployWordPressThemeV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Slug of the theme
+       */
+      slug: string;
+      /**
+       * Relative path to the theme directory from wp-content/themes
+       */
+      theme_path: string;
+      /**
+       * Whether to activate the theme after deployment
+       */
+      is_activated?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Install a theme on an existing WordPress installation.