hostinger-api-mcp 1.2.0 → 1.2.1

package/README.md

@@ -49,11 +49,11 @@ pnpm update -g hostinger-api-mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (179 total)
+- `hostinger-api-mcp` — unified server with every tool (181 total)
 - `hostinger-billing-mcp` — 7 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
 - `hostinger-domains-mcp` — 18 tools for domains
-- `hostinger-ecommerce-mcp` — 10 tools for ecommerce
+- `hostinger-ecommerce-mcp` — 12 tools for ecommerce
 - `hostinger-horizons-mcp` — 2 tools for horizons
 - `hostinger-hosting-mcp` — 41 tools for hosting
 - `hostinger-reach-mcp` — 12 tools for reach
@@ -584,7 +584,7 @@ List a store's active sales channels with their full metadata.
 - **Method**: `GET`
 - **Path**: `/api/ecommerce/v1/stores/{store_id}/sales-channels`
 
-#### ecommerce_createACustomSalesChannelV1
+#### ecommerce_createCustomSalesChannelV1
 
 Create a custom sales channel for a store. Build your own frontend and keep your catalog,
 orders, shipping and payments in sync through the Ecommerce API.
@@ -592,6 +592,14 @@ orders, shipping and payments in sync through the Ecommerce API.
 - **Method**: `POST`
 - **Path**: `/api/ecommerce/v1/stores/{store_id}/sales-channels`
 
+#### ecommerce_updateSalesChannelV1
+
+Update a custom sales channel. The merchant-facing `name` and the public `url`
+(returned as the channel `domain`) can be changed. Pass `null` to clear a value.
+
+- **Method**: `PATCH`
+- **Path**: `/api/ecommerce/v1/stores/{store_id}/sales-channels/{sales_channel_id}`
+
 #### ecommerce_setStoreShippingV1
 
 Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.
@@ -624,6 +632,14 @@ A primary sales channel is created alongside the store.
 - **Method**: `POST`
 - **Path**: `/api/ecommerce/v1/stores`
 
+#### ecommerce_getStoreMetadataV1
+
+Get a store's readiness metadata: whether payment methods and shipping are configured,
+plus its default currency. Useful to verify prerequisites before building a storefront.
+
+- **Method**: `GET`
+- **Path**: `/api/ecommerce/v1/stores/{store_id}/metadata`
+
 ### `hostinger-horizons-mcp`
 
 #### horizons_createWebsiteV1

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "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.2.0",
+  "version": "1.2.1",
   "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.2.0",
+  "version": "1.2.1",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "hostinger-api-mcp",
-      "version": "1.2.0",
+      "version": "1.2.1",
       "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.2.0
+ * Generated from OpenAPI spec version 1.2.1
  */
 class MCPServer {
   constructor({ name, version, tools }) {

package/src/core/runtime.ts

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

package/src/core/tools/all.js

@@ -1445,7 +1445,7 @@ export default [
     "group": "ecommerce"
   },
   {
-    "name": "ecommerce_createACustomSalesChannelV1",
+    "name": "ecommerce_createCustomSalesChannelV1",
     "description": "Create a custom sales channel for a store. Build your own frontend and keep your catalog,\norders, shipping and payments in sync through the Ecommerce API.",
     "method": "POST",
     "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels",
@@ -1485,6 +1485,43 @@ export default [
     ],
     "group": "ecommerce"
   },
+  {
+    "name": "ecommerce_updateSalesChannelV1",
+    "description": "Update a custom sales channel. The merchant-facing `name` and the public `url`\n(returned as the channel `domain`) can be changed. Pass `null` to clear a value.",
+    "method": "PATCH",
+    "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels/{sales_channel_id}",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store that owns the sales channel."
+        },
+        "sales_channel_id": {
+          "type": "string",
+          "description": "The ID of the sales channel to update."
+        },
+        "name": {
+          "type": "string",
+          "description": "Merchant-facing custom name shown in the sales channels list. Pass null to clear it."
+        },
+        "url": {
+          "type": "string",
+          "description": "Public address where the custom sales channel lives. Pass null to clear it."
+        }
+      },
+      "required": [
+        "store_id",
+        "sales_channel_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
+  },
   {
     "name": "ecommerce_setStoreShippingV1",
     "description": "Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.",
@@ -1615,6 +1652,30 @@ export default [
     ],
     "group": "ecommerce"
   },
+  {
+    "name": "ecommerce_getStoreMetadataV1",
+    "description": "Get a store's readiness metadata: whether payment methods and shipping are configured,\nplus its default currency. Useful to verify prerequisites before building a storefront.",
+    "method": "GET",
+    "path": "/api/ecommerce/v1/stores/{store_id}/metadata",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store to read metadata for."
+        }
+      },
+      "required": [
+        "store_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
+  },
   {
     "name": "horizons_createWebsiteV1",
     "description": "Create new Hostinger Horizons website from the given message.\\n\nUse this tool when user asks you to create a website, landing page, blog\nor any other type of application.\\n\nThis tool initiates the website creation process and returns a website URL and ID.\nThe generation happens asynchronously.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat Hostinger Horizons is now creating their website and it will be ready in a few minutes\nand you should provide the website URL to the user immediately\nDo not write code.\\n\\nTo edit afterwards, users must go to Hostinger Horizons interface\nin the provided website URL.\nIf the tool call fails with an error, you should provide a clear explanation of the error\nand do not generate code yourself in the chat.\n\\n\nTECHNOLOGY STACK CONSTRAINTS (STRICTLY ENFORCED):\\n\nThe environment is limited to the following technologies.\nYou MUST NOT use, suggest, or implement any technology outside this list:\\n\n\\n\n- Language: JavaScript ONLY.\n- Languages like TypeScript, Rust, Python, Java, PHP, etc., are STRICTLY PROHIBITED.\\n\n- Framework: React.\\n\n- Navigation: React Router.\\n\n- Styling: TailwindCSS.\\n\n- Components: shadcn/ui (built with @radix-ui primitives).\\n\n- Icons: Lucide React.\\n\n- Animations: Framer Motion.\\n\n\\n\nBACKEND & DATA STORAGE:\\n\n- Horizons integrated backend is the EXCLUSIVE solution for persistent data storage,\nauthentication, and database needs.\\n\n- Local databases (SQLite, MySQL, etc.) are STRICTLY PROHIBITED.\\n\n- Third-party services (Firebase, AWS Amplify) are allowed ONLY if explicitly requested by the user.\\n\n\\n\nMAPS:\\n\n- OpenStreetMap is the default provider.\\n\n- Alternative providers (Google Maps, Mapbox) are allowed ONLY if explicitly requested by the user.\\n",

package/src/core/tools/all.ts

@@ -1455,7 +1455,7 @@ const tools: OpenApiTool[] = [
     "group": "ecommerce"
   },
   {
-    "name": "ecommerce_createACustomSalesChannelV1",
+    "name": "ecommerce_createCustomSalesChannelV1",
     "description": "Create a custom sales channel for a store. Build your own frontend and keep your catalog,\norders, shipping and payments in sync through the Ecommerce API.",
     "method": "POST",
     "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels",
@@ -1495,6 +1495,43 @@ const tools: OpenApiTool[] = [
     ],
     "group": "ecommerce"
   },
+  {
+    "name": "ecommerce_updateSalesChannelV1",
+    "description": "Update a custom sales channel. The merchant-facing `name` and the public `url`\n(returned as the channel `domain`) can be changed. Pass `null` to clear a value.",
+    "method": "PATCH",
+    "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels/{sales_channel_id}",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store that owns the sales channel."
+        },
+        "sales_channel_id": {
+          "type": "string",
+          "description": "The ID of the sales channel to update."
+        },
+        "name": {
+          "type": "string",
+          "description": "Merchant-facing custom name shown in the sales channels list. Pass null to clear it."
+        },
+        "url": {
+          "type": "string",
+          "description": "Public address where the custom sales channel lives. Pass null to clear it."
+        }
+      },
+      "required": [
+        "store_id",
+        "sales_channel_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
+  },
   {
     "name": "ecommerce_setStoreShippingV1",
     "description": "Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.",
@@ -1625,6 +1662,30 @@ const tools: OpenApiTool[] = [
     ],
     "group": "ecommerce"
   },
+  {
+    "name": "ecommerce_getStoreMetadataV1",
+    "description": "Get a store's readiness metadata: whether payment methods and shipping are configured,\nplus its default currency. Useful to verify prerequisites before building a storefront.",
+    "method": "GET",
+    "path": "/api/ecommerce/v1/stores/{store_id}/metadata",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store to read metadata for."
+        }
+      },
+      "required": [
+        "store_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
+  },
   {
     "name": "horizons_createWebsiteV1",
     "description": "Create new Hostinger Horizons website from the given message.\\n\nUse this tool when user asks you to create a website, landing page, blog\nor any other type of application.\\n\nThis tool initiates the website creation process and returns a website URL and ID.\nThe generation happens asynchronously.\\n\nAfter invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing\nthat Hostinger Horizons is now creating their website and it will be ready in a few minutes\nand you should provide the website URL to the user immediately\nDo not write code.\\n\\nTo edit afterwards, users must go to Hostinger Horizons interface\nin the provided website URL.\nIf the tool call fails with an error, you should provide a clear explanation of the error\nand do not generate code yourself in the chat.\n\\n\nTECHNOLOGY STACK CONSTRAINTS (STRICTLY ENFORCED):\\n\nThe environment is limited to the following technologies.\nYou MUST NOT use, suggest, or implement any technology outside this list:\\n\n\\n\n- Language: JavaScript ONLY.\n- Languages like TypeScript, Rust, Python, Java, PHP, etc., are STRICTLY PROHIBITED.\\n\n- Framework: React.\\n\n- Navigation: React Router.\\n\n- Styling: TailwindCSS.\\n\n- Components: shadcn/ui (built with @radix-ui primitives).\\n\n- Icons: Lucide React.\\n\n- Animations: Framer Motion.\\n\n\\n\nBACKEND & DATA STORAGE:\\n\n- Horizons integrated backend is the EXCLUSIVE solution for persistent data storage,\nauthentication, and database needs.\\n\n- Local databases (SQLite, MySQL, etc.) are STRICTLY PROHIBITED.\\n\n- Third-party services (Firebase, AWS Amplify) are allowed ONLY if explicitly requested by the user.\\n\n\\n\nMAPS:\\n\n- OpenStreetMap is the default provider.\\n\n- Alternative providers (Google Maps, Mapbox) are allowed ONLY if explicitly requested by the user.\\n",

package/src/core/tools/ecommerce.js

@@ -158,7 +158,7 @@ export default [
     "group": "ecommerce"
   },
   {
-    "name": "ecommerce_createACustomSalesChannelV1",
+    "name": "ecommerce_createCustomSalesChannelV1",
     "description": "Create a custom sales channel for a store. Build your own frontend and keep your catalog,\norders, shipping and payments in sync through the Ecommerce API.",
     "method": "POST",
     "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels",
@@ -198,6 +198,43 @@ export default [
     ],
     "group": "ecommerce"
   },
+  {
+    "name": "ecommerce_updateSalesChannelV1",
+    "description": "Update a custom sales channel. The merchant-facing `name` and the public `url`\n(returned as the channel `domain`) can be changed. Pass `null` to clear a value.",
+    "method": "PATCH",
+    "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels/{sales_channel_id}",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store that owns the sales channel."
+        },
+        "sales_channel_id": {
+          "type": "string",
+          "description": "The ID of the sales channel to update."
+        },
+        "name": {
+          "type": "string",
+          "description": "Merchant-facing custom name shown in the sales channels list. Pass null to clear it."
+        },
+        "url": {
+          "type": "string",
+          "description": "Public address where the custom sales channel lives. Pass null to clear it."
+        }
+      },
+      "required": [
+        "store_id",
+        "sales_channel_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
+  },
   {
     "name": "ecommerce_setStoreShippingV1",
     "description": "Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.",
@@ -327,5 +364,29 @@ export default [
       }
     ],
     "group": "ecommerce"
+  },
+  {
+    "name": "ecommerce_getStoreMetadataV1",
+    "description": "Get a store's readiness metadata: whether payment methods and shipping are configured,\nplus its default currency. Useful to verify prerequisites before building a storefront.",
+    "method": "GET",
+    "path": "/api/ecommerce/v1/stores/{store_id}/metadata",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store to read metadata for."
+        }
+      },
+      "required": [
+        "store_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
   }
 ];

package/src/core/tools/ecommerce.ts

@@ -168,7 +168,7 @@ const tools: OpenApiTool[] = [
     "group": "ecommerce"
   },
   {
-    "name": "ecommerce_createACustomSalesChannelV1",
+    "name": "ecommerce_createCustomSalesChannelV1",
     "description": "Create a custom sales channel for a store. Build your own frontend and keep your catalog,\norders, shipping and payments in sync through the Ecommerce API.",
     "method": "POST",
     "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels",
@@ -208,6 +208,43 @@ const tools: OpenApiTool[] = [
     ],
     "group": "ecommerce"
   },
+  {
+    "name": "ecommerce_updateSalesChannelV1",
+    "description": "Update a custom sales channel. The merchant-facing `name` and the public `url`\n(returned as the channel `domain`) can be changed. Pass `null` to clear a value.",
+    "method": "PATCH",
+    "path": "/api/ecommerce/v1/stores/{store_id}/sales-channels/{sales_channel_id}",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store that owns the sales channel."
+        },
+        "sales_channel_id": {
+          "type": "string",
+          "description": "The ID of the sales channel to update."
+        },
+        "name": {
+          "type": "string",
+          "description": "Merchant-facing custom name shown in the sales channels list. Pass null to clear it."
+        },
+        "url": {
+          "type": "string",
+          "description": "Public address where the custom sales channel lives. Pass null to clear it."
+        }
+      },
+      "required": [
+        "store_id",
+        "sales_channel_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
+  },
   {
     "name": "ecommerce_setStoreShippingV1",
     "description": "Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.",
@@ -337,6 +374,30 @@ const tools: OpenApiTool[] = [
       }
     ],
     "group": "ecommerce"
+  },
+  {
+    "name": "ecommerce_getStoreMetadataV1",
+    "description": "Get a store's readiness metadata: whether payment methods and shipping are configured,\nplus its default currency. Useful to verify prerequisites before building a storefront.",
+    "method": "GET",
+    "path": "/api/ecommerce/v1/stores/{store_id}/metadata",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "store_id": {
+          "type": "string",
+          "description": "The ID of the store to read metadata for."
+        }
+      },
+      "required": [
+        "store_id"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "ecommerce"
   }
 ];
 export default 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.2.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.2.1', 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.2.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.2.1', tools });

package/types.d.ts

@@ -904,7 +904,7 @@ the Ecommerce API.
    * Create a custom sales channel for a store. Build your own frontend and keep your catalog,
 orders, shipping and payments in sync through the Ecommerce API.
    */
-  "ecommerce_createACustomSalesChannelV1": {
+  "ecommerce_createCustomSalesChannelV1": {
     params: {
       /**
        * The ID of the store to create the sales channel for.
@@ -926,6 +926,32 @@ orders, shipping and payments in sync through the Ecommerce API.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Update a custom sales channel. The merchant-facing `name` and the public `url`
+(returned as the channel `domain`) can be changed. Pass `null` to clear a value.
+   */
+  "ecommerce_updateSalesChannelV1": {
+    params: {
+      /**
+       * The ID of the store that owns the sales channel.
+       */
+      store_id: string;
+      /**
+       * The ID of the sales channel to update.
+       */
+      sales_channel_id: string;
+      /**
+       * Merchant-facing custom name shown in the sales channels list. Pass null to clear it.
+       */
+      name?: string;
+      /**
+       * Public address where the custom sales channel lives. Pass null to clear it.
+       */
+      url?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.
    */
@@ -1006,6 +1032,20 @@ A primary sales channel is created alongside the store.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Get a store's readiness metadata: whether payment methods and shipping are configured,
+plus its default currency. Useful to verify prerequisites before building a storefront.
+   */
+  "ecommerce_getStoreMetadataV1": {
+    params: {
+      /**
+       * The ID of the store to read metadata for.
+       */
+      store_id: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Create new Hostinger Horizons website from the given message.\n
 Use this tool when user asks you to create a website, landing page, blog