hostinger-api-mcp 1.2.0 → 1.3.0

package/README.md

@@ -49,16 +49,16 @@ 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 (197 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
 - `hostinger-vps-mcp` — 62 tools for vps
-- `hostinger-wordpress-mcp` — 19 tools for wordpress
+- `hostinger-wordpress-mcp` — 35 tools for wordpress
 
 Pick the binary that matches your agent's scope. `hostinger-api-mcp` remains the backwards-compatible default.
 
@@ -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
@@ -1925,6 +1941,65 @@ Use this endpoint to power off running VPS instances.
 
 ### `hostinger-wordpress-mcp`
 
+#### hosting_showAIOptionStatusV1
+
+Show the current AI option status for the Hostinger Tools plugin on the
+specified WordPress installation. Filter by `option` to return a single
+option, or omit it to return all options.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/hostinger-plugins/ai-option/status`
+
+#### hosting_setAIOptionStatusV1
+
+Enable or disable an AI option for the Hostinger Tools plugin on the specified
+WordPress installation.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `PATCH`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/hostinger-plugins/ai-option/status`
+
+#### hosting_checkIfWordPressInstallationsAreValidV1
+
+Check whether one or more WordPress installations are valid and working
+correctly. Detects broken installations caused by missing files, broken
+plugins, themes and similar issues.
+
+Provide the WordPress installation (software) identifiers in the body. They
+can be obtained from GET /api/hosting/v1/wordpress/installations (the `id`
+field).
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations/check-is-valid`
+
+#### hosting_deleteWordPressInstallationV1
+
+Delete the specified WordPress installation, with optional file and database
+removal. This removes all associated components including plugins, themes,
+staging websites and any other related data.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `DELETE`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}`
+
+#### hosting_detectWordPressInstallationsV1
+
+Trigger a background scan to detect WordPress installations for the account.
+
+This operation is asynchronous: a successful response only means the scan has
+been queued. Poll GET /api/hosting/v1/wordpress/installations to fetch the
+detected installations once the scan completes.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations/detect`
+
 #### hosting_installWordPressV1
 
 Install WordPress on an existing website.
@@ -1962,6 +2037,125 @@ Each installation includes a `valid` flag and, when invalid, a
 - **Method**: `GET`
 - **Path**: `/api/hosting/v1/wordpress/installations`
 
+#### hosting_listAvailableWordPressCoreUpdatesV1
+
+List available WordPress core updates for the specified installation.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/updates`
+
+#### hosting_getInstallationJWTTokenV1
+
+Return a JWT token used to authenticate requests against the specified
+WordPress installation, including its MCP (Model Context Protocol) endpoint.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/jwt-token`
+
+#### hosting_showWordPressCoreVersionV1
+
+Show the WordPress core version for the specified installation, along with
+known vulnerabilities affecting it.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/version`
+
+#### hosting_updateWordPressCoreV1
+
+Update the WordPress core for the specified installation (minor update or a
+specific version).
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+This operation is asynchronous: a successful response only means the update
+job has been queued.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/update`
+
+#### hosting_purgeLiteSpeedCacheV1
+
+Purge the LiteSpeed Cache for the specified WordPress installation.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/litespeed-cache/purge`
+
+#### hosting_showLiteSpeedCacheStatusV1
+
+Show the LiteSpeed Cache status for the specified WordPress installation.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/litespeed-cache/status`
+
+#### hosting_createLoginLinksV1
+
+Create temporary auto-login links for the specified WordPress installation.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/login/links`
+
+#### hosting_showMaintenanceStatusV1
+
+Show the maintenance mode status for the specified WordPress installation.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/maintenance/status`
+
+#### hosting_toggleMaintenanceModeV1
+
+Enable or disable maintenance mode for the specified WordPress installation,
+based on the `enabled` flag.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `PATCH`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/maintenance/toggle`
+
+#### hosting_showMemcachedObjectCacheStatusV1
+
+Show the Memcached object cache status for the specified WordPress
+installation.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/memcached/status`
+
+#### hosting_toggleMemcachedObjectCacheV1
+
+Activate or deactivate the Memcached object cache for the specified WordPress
+installation, based on the `enabled` flag.
+
+Provide the WordPress installation (software) identifier in the path. It can
+be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
+
+- **Method**: `PATCH`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/memcached/toggle`
+
 #### hosting_activateWordPressPluginV1
 
 Activate an installed plugin on a WordPress installation.

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.2.0",
+  "version": "1.3.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.2.0",
+  "version": "1.3.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.2.0",
+  "version": "1.3.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "hostinger-api-mcp",
-      "version": "1.2.0",
+      "version": "1.3.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.2.0
+ * Generated from OpenAPI spec version 1.3.0
  */
 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.3.0
  */
 class MCPServer {
   private readonly name: string;