hostinger-api-mcp 1.47.0 → 1.49.0

package/README.md

@@ -69,14 +69,14 @@ pnpm update -g hostinger-api-mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (369 total)
+- `hostinger-api-mcp` — unified server with every tool (371 total)
 - `hostinger-agency-hosting-mcp` — 38 tools for agency-hosting
 - `hostinger-billing-mcp` — 9 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
 - `hostinger-domains-mcp` — 40 tools for domains
 - `hostinger-ecommerce-mcp` — 29 tools for ecommerce
 - `hostinger-horizons-mcp` — 2 tools for horizons
-- `hostinger-hosting-mcp` — 56 tools for hosting
+- `hostinger-hosting-mcp` — 58 tools for hosting
 - `hostinger-mail-mcp` — 38 tools for mail
 - `hostinger-reach-mcp` — 49 tools for reach
 - `hostinger-vps-mcp` — 62 tools for vps
@@ -1983,6 +1983,40 @@ The archive must already be present on the website's file storage. Use the
 - **Method**: `GET`
 - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/from-archive`
 
+#### hosting_listNode_jsEnvironmentVariablesV1
+
+Lists the Node.js environment variables currently set for the website. Values are always
+masked as `********` and cannot be read back through this API. Use this endpoint to see
+which keys are configured or to verify a change, not to read values.
+
+To change variables, use the `Replace Node.js environment variables` endpoint. It replaces
+the whole set, so never copy the masked values from this response into that request; send
+the full desired set with real values taken from the project `.env` file or the user
+prompt instead.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env`
+
+#### hosting_replaceNode_jsEnvironmentVariablesV1
+
+Replaces the website's Node.js environment variables with the ones provided. This is a
+full replace: any variable not in the request is deleted, and sending an empty `env_vars`
+array deletes every variable. Saving writes the values and restarts the running Node.js
+process.
+
+A restart is enough for apps that read environment variables at process start, such as
+Express or NestJS. It is not enough for frameworks that bake variables into the build.
+Next.js standalone is one of those: build-time values (including `NEXT_PUBLIC_*`) need a
+fresh build. After this call, use the `Start Node.js build` endpoint so those apps
+pick up the new values.
+
+The `List Node.js environment variables` endpoint returns masked values (`********`), so
+never copy values from it into this request. Always send the full desired set with real
+values taken from the project `.env` file or the user prompt.
+
+- **Method**: `PUT`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env`
+
 #### hosting_getNodeJSBuildLogsV1
 
 Retrieve logs from a specific Node.js build process.

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.47.0",
+  "version": "1.49.0",
   "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
   "mcpServers": {
     "hostinger": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.47.0",
+  "version": "1.49.0",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/hostinger/api-mcp-server",
     "source": "github"
   },
-  "version": "1.47.0",
+  "version": "1.49.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "hostinger-api-mcp",
-      "version": "1.47.0",
+      "version": "1.49.0",
       "transport": {
         "type": "stdio"
       },

package/src/core/runtime.js

@@ -29,7 +29,7 @@ const SECURITY_SCHEMES = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.43.1
+ * Generated from OpenAPI spec version 1.45.0
  */
 class MCPServer {
   constructor({ name, version, tools }) {

package/src/core/runtime.ts

@@ -52,7 +52,7 @@ const SECURITY_SCHEMES: Record<string, SecurityScheme> = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.43.1
+ * Generated from OpenAPI spec version 1.45.0
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -5746,6 +5746,87 @@ export default [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsEnvironmentVariablesV1",
+    "description": "Lists the Node.js environment variables currently set for the website. Values are always\nmasked as `********` and cannot be read back through this API. Use this endpoint to see\nwhich keys are configured or to verify a change, not to read values.\n\nTo change variables, use the `Replace Node.js environment variables` endpoint. It replaces\nthe whole set, so never copy the masked values from this response into that request; send\nthe full desired set with real values taken from the project `.env` file or the user\nprompt instead.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_replaceNode_jsEnvironmentVariablesV1",
+    "description": "Replaces the website's Node.js environment variables with the ones provided. This is a\nfull replace: any variable not in the request is deleted, and sending an empty `env_vars`\narray deletes every variable. Saving writes the values and restarts the running Node.js\nprocess.\n\nA restart is enough for apps that read environment variables at process start, such as\nExpress or NestJS. It is not enough for frameworks that bake variables into the build.\nNext.js standalone is one of those: build-time values (including `NEXT_PUBLIC_*`) need a\nfresh build. After this call, use the `Start Node.js build` endpoint so those apps\npick up the new values.\n\nThe `List Node.js environment variables` endpoint returns masked values (`********`), so\nnever copy values from it into this request. Always send the full desired set with real\nvalues taken from the project `.env` file or the user prompt.",
+    "method": "PUT",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "env_vars": {
+          "type": "array",
+          "description": "Environment variables to set. This is the full desired set: any variable not in\nthis list is deleted, and an empty array deletes every variable.",
+          "items": {
+            "type": "object",
+            "description": "env_vars parameter",
+            "properties": {
+              "key": {
+                "type": "string",
+                "description": "Environment variable name. Must start with an uppercase letter or\nunderscore, followed by uppercase letters, digits or underscores."
+              },
+              "value": {
+                "type": "string",
+                "description": "Environment variable value."
+              }
+            },
+            "required": [
+              "key",
+              "value"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "env_vars"
+      ]
+    },
+    "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).",

package/src/core/tools/all.ts

@@ -5760,6 +5760,87 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsEnvironmentVariablesV1",
+    "description": "Lists the Node.js environment variables currently set for the website. Values are always\nmasked as `********` and cannot be read back through this API. Use this endpoint to see\nwhich keys are configured or to verify a change, not to read values.\n\nTo change variables, use the `Replace Node.js environment variables` endpoint. It replaces\nthe whole set, so never copy the masked values from this response into that request; send\nthe full desired set with real values taken from the project `.env` file or the user\nprompt instead.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_replaceNode_jsEnvironmentVariablesV1",
+    "description": "Replaces the website's Node.js environment variables with the ones provided. This is a\nfull replace: any variable not in the request is deleted, and sending an empty `env_vars`\narray deletes every variable. Saving writes the values and restarts the running Node.js\nprocess.\n\nA restart is enough for apps that read environment variables at process start, such as\nExpress or NestJS. It is not enough for frameworks that bake variables into the build.\nNext.js standalone is one of those: build-time values (including `NEXT_PUBLIC_*`) need a\nfresh build. After this call, use the `Start Node.js build` endpoint so those apps\npick up the new values.\n\nThe `List Node.js environment variables` endpoint returns masked values (`********`), so\nnever copy values from it into this request. Always send the full desired set with real\nvalues taken from the project `.env` file or the user prompt.",
+    "method": "PUT",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "env_vars": {
+          "type": "array",
+          "description": "Environment variables to set. This is the full desired set: any variable not in\nthis list is deleted, and an empty array deletes every variable.",
+          "items": {
+            "type": "object",
+            "description": "env_vars parameter",
+            "properties": {
+              "key": {
+                "type": "string",
+                "description": "Environment variable name. Must start with an uppercase letter or\nunderscore, followed by uppercase letters, digits or underscores."
+              },
+              "value": {
+                "type": "string",
+                "description": "Environment variable value."
+              }
+            },
+            "required": [
+              "key",
+              "value"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "env_vars"
+      ]
+    },
+    "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).",

package/src/core/tools/hosting.js

@@ -1374,6 +1374,87 @@ export default [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsEnvironmentVariablesV1",
+    "description": "Lists the Node.js environment variables currently set for the website. Values are always\nmasked as `********` and cannot be read back through this API. Use this endpoint to see\nwhich keys are configured or to verify a change, not to read values.\n\nTo change variables, use the `Replace Node.js environment variables` endpoint. It replaces\nthe whole set, so never copy the masked values from this response into that request; send\nthe full desired set with real values taken from the project `.env` file or the user\nprompt instead.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_replaceNode_jsEnvironmentVariablesV1",
+    "description": "Replaces the website's Node.js environment variables with the ones provided. This is a\nfull replace: any variable not in the request is deleted, and sending an empty `env_vars`\narray deletes every variable. Saving writes the values and restarts the running Node.js\nprocess.\n\nA restart is enough for apps that read environment variables at process start, such as\nExpress or NestJS. It is not enough for frameworks that bake variables into the build.\nNext.js standalone is one of those: build-time values (including `NEXT_PUBLIC_*`) need a\nfresh build. After this call, use the `Start Node.js build` endpoint so those apps\npick up the new values.\n\nThe `List Node.js environment variables` endpoint returns masked values (`********`), so\nnever copy values from it into this request. Always send the full desired set with real\nvalues taken from the project `.env` file or the user prompt.",
+    "method": "PUT",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "env_vars": {
+          "type": "array",
+          "description": "Environment variables to set. This is the full desired set: any variable not in\nthis list is deleted, and an empty array deletes every variable.",
+          "items": {
+            "type": "object",
+            "description": "env_vars parameter",
+            "properties": {
+              "key": {
+                "type": "string",
+                "description": "Environment variable name. Must start with an uppercase letter or\nunderscore, followed by uppercase letters, digits or underscores."
+              },
+              "value": {
+                "type": "string",
+                "description": "Environment variable value."
+              }
+            },
+            "required": [
+              "key",
+              "value"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "env_vars"
+      ]
+    },
+    "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).",

package/src/core/tools/hosting.ts

@@ -1388,6 +1388,87 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsEnvironmentVariablesV1",
+    "description": "Lists the Node.js environment variables currently set for the website. Values are always\nmasked as `********` and cannot be read back through this API. Use this endpoint to see\nwhich keys are configured or to verify a change, not to read values.\n\nTo change variables, use the `Replace Node.js environment variables` endpoint. It replaces\nthe whole set, so never copy the masked values from this response into that request; send\nthe full desired set with real values taken from the project `.env` file or the user\nprompt instead.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_replaceNode_jsEnvironmentVariablesV1",
+    "description": "Replaces the website's Node.js environment variables with the ones provided. This is a\nfull replace: any variable not in the request is deleted, and sending an empty `env_vars`\narray deletes every variable. Saving writes the values and restarts the running Node.js\nprocess.\n\nA restart is enough for apps that read environment variables at process start, such as\nExpress or NestJS. It is not enough for frameworks that bake variables into the build.\nNext.js standalone is one of those: build-time values (including `NEXT_PUBLIC_*`) need a\nfresh build. After this call, use the `Start Node.js build` endpoint so those apps\npick up the new values.\n\nThe `List Node.js environment variables` endpoint returns masked values (`********`), so\nnever copy values from it into this request. Always send the full desired set with real\nvalues taken from the project `.env` file or the user prompt.",
+    "method": "PUT",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "env_vars": {
+          "type": "array",
+          "description": "Environment variables to set. This is the full desired set: any variable not in\nthis list is deleted, and an empty array deletes every variable.",
+          "items": {
+            "type": "object",
+            "description": "env_vars parameter",
+            "properties": {
+              "key": {
+                "type": "string",
+                "description": "Environment variable name. Must start with an uppercase letter or\nunderscore, followed by uppercase letters, digits or underscores."
+              },
+              "value": {
+                "type": "string",
+                "description": "Environment variable value."
+              }
+            },
+            "required": [
+              "key",
+              "value"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "env_vars"
+      ]
+    },
+    "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).",

package/src/servers/agency-hosting.js

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

package/src/servers/agency-hosting.ts

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

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: '1.47.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.49.0', 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: '1.47.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.49.0', 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: '1.47.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.49.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.47.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.49.0', tools });

package/src/servers/horizons.ts

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

package/src/servers/mail.js

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

package/src/servers/mail.ts

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

package/src/servers/wordpress.js

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

package/src/servers/wordpress.ts

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

package/types.d.ts

@@ -3763,6 +3763,65 @@ The archive must already be present on the website's file storage. Use the
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Lists the Node.js environment variables currently set for the website. Values are always
+masked as `********` and cannot be read back through this API. Use this endpoint to see
+which keys are configured or to verify a change, not to read values.
+
+To change variables, use the `Replace Node.js environment variables` endpoint. It replaces
+the whole set, so never copy the masked values from this response into that request; send
+the full desired set with real values taken from the project `.env` file or the user
+prompt instead.
+   */
+  "hosting_listNode_jsEnvironmentVariablesV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Replaces the website's Node.js environment variables with the ones provided. This is a
+full replace: any variable not in the request is deleted, and sending an empty `env_vars`
+array deletes every variable. Saving writes the values and restarts the running Node.js
+process.
+
+A restart is enough for apps that read environment variables at process start, such as
+Express or NestJS. It is not enough for frameworks that bake variables into the build.
+Next.js standalone is one of those: build-time values (including `NEXT_PUBLIC_*`) need a
+fresh build. After this call, use the `Start Node.js build` endpoint so those apps
+pick up the new values.
+
+The `List Node.js environment variables` endpoint returns masked values (`********`), so
+never copy values from it into this request. Always send the full desired set with real
+values taken from the project `.env` file or the user prompt.
+   */
+  "hosting_replaceNode_jsEnvironmentVariablesV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Environment variables to set. This is the full desired set: any variable not in
+this list is deleted, and an empty array deletes every variable.
+       */
+      env_vars: array;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve logs from a specific Node.js build process.