hostinger-api-mcp 2.7.2 → 2.7.3

package/CHANGELOG.md

@@ -4,6 +4,18 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v2.7.3 — 2026-10-05
+
+### Operations
+
+- Changed the description and input schema of `wordpress_installations_install`
+
+### Also in this release
+
+- Documentation: `README.md`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Build and packaging: `types.d.ts`
+
 ## v2.7.2 — 2026-10-05
 
 ### Operations

package/README.md

@@ -4534,6 +4534,9 @@ 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.
 
+Returns 422 when the account already uses all the databases its plan allows,
+unless `database.name` is an existing database on the account.
+
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations`
 

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "2.7.2",
+  "version": "2.7.3",
   "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": "2.7.2",
+  "version": "2.7.3",
   "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": "2.7.2",
+  "version": "2.7.3",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "2.7.2",
+      "version": "2.7.3",
       "transport": {
         "type": "stdio"
       },

package/src/core/runtime.js

@@ -64,7 +64,7 @@ const GetSkillRequestSchema = z.object({
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.58.2
+ * Generated from OpenAPI spec version 1.58.3
  */
 class MCPServer {
   constructor({ name, version, tools, instructions, skills = [] }) {

package/src/core/runtime.ts

@@ -94,7 +94,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.58.2
+ * Generated from OpenAPI spec version 1.58.3
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -15472,7 +15472,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -15540,7 +15540,7 @@ export default [
         },
         "database": {
           "type": "object",
-          "description": "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.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -15548,7 +15548,7 @@ export default [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

package/src/core/tools/all.ts

@@ -15486,7 +15486,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -15554,7 +15554,7 @@ const tools: OpenApiTool[] = [
         },
         "database": {
           "type": "object",
-          "description": "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.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -15562,7 +15562,7 @@ const tools: OpenApiTool[] = [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

package/src/core/tools/wordpress.js

@@ -255,7 +255,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -323,7 +323,7 @@ export default [
         },
         "database": {
           "type": "object",
-          "description": "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.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -331,7 +331,7 @@ export default [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

package/src/core/tools/wordpress.ts

@@ -269,7 +269,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -337,7 +337,7 @@ const tools: OpenApiTool[] = [
         },
         "database": {
           "type": "object",
-          "description": "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.",
+          "description": "Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.",
           "properties": {
             "name": {
               "type": "string",
@@ -345,7 +345,7 @@ const tools: OpenApiTool[] = [
             },
             "password": {
               "type": "string",
-              "description": "password parameter"
+              "description": "Password for a new database. Random when omitted or null. Ignored when the named database already exists."
             }
           }
         }

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

package/src/servers/all.js

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '2.7.2', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.7.3', tools, instructions, skills });

package/src/servers/all.ts

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '2.7.2', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.7.3', tools, instructions, skills });

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

package/src/servers/hosting.js

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

package/src/servers/hosting.ts

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

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: '2.7.2', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.7.3', 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: '2.7.2', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.7.3', 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: '2.7.2', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.7.3', 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: '2.7.2', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.7.3', 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: '2.7.2', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.7.3', 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: '2.7.2', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.7.3', 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: '2.7.2', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.7.3', 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: '2.7.2', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.7.3', tools });

package/types.d.ts

@@ -9045,6 +9045,9 @@ 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.
+
+Returns 422 when the account already uses all the databases its plan allows,
+unless `database.name` is an existing database on the account.
    */
   "wordpress_installations_install": {
     params: {
@@ -9085,7 +9088,7 @@ that list, WordPress is ready.
        */
       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.
+       * Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan's database limit.
        */
       database?: object;
     };