hostinger-api-mcp 0.3.2 → 1.1.0

package/README.md

@@ -49,15 +49,16 @@ pnpm update -g hostinger-api-mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (153 total)
+- `hostinger-api-mcp` — unified server with every tool (170 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` — 7 tools for ecommerce
 - `hostinger-horizons-mcp` — 2 tools for horizons
-- `hostinger-hosting-mcp` — 37 tools for hosting
+- `hostinger-hosting-mcp` — 35 tools for hosting
 - `hostinger-reach-mcp` — 12 tools for reach
 - `hostinger-vps-mcp` — 62 tools for vps
+- `hostinger-wordpress-mcp` — 19 tools for wordpress
 
 Pick the binary that matches your agent's scope. `hostinger-api-mcp` remains the backwards-compatible default.
 
@@ -1008,43 +1009,6 @@ websites list endpoint to see when your new website becomes available.
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/websites`
 
-#### hosting_installWordPressV1
-
-Install WordPress on an existing website.
-
-The website must already exist before calling this endpoint. To create a new
-website first, use POST /api/hosting/v1/websites and poll
-GET /api/hosting/v1/websites until it appears.
-
-Call GET /api/hosting/v1/wordpress/installations filtered by username and
-domain before proceeding to check whether WordPress is already installed on
-the target domain/path. If WordPress already exists and `overwrite` is false
-(the default), the async job will fail.
-
-This operation is asynchronous: a successful response only means the install
-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.
-
-- **Method**: `POST`
-- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations`
-
-#### hosting_listWordPressInstallationsV1
-
-List WordPress installations accessible to the authenticated client.
-
-Use this endpoint to discover existing WordPress installations and to poll
-for installation status after calling the install endpoint. When a newly
-requested installation appears in this list, WordPress is ready. Filter by
-username and domain to narrow results to a specific website.
-
-Each installation includes a `valid` flag and, when invalid, a
-`validationError` describing why.
-
-- **Method**: `GET`
-- **Path**: `/api/hosting/v1/wordpress/installations`
-
 ### `hostinger-reach-mcp`
 
 #### reach_deleteAContactV1
@@ -1876,3 +1840,253 @@ Use this endpoint to power off running VPS instances.
 
 - **Method**: `POST`
 - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/stop`
+
+### `hostinger-wordpress-mcp`
+
+#### hosting_installWordPressV1
+
+Install WordPress on an existing website.
+
+The website must already exist before calling this endpoint. To create a new
+website first, use POST /api/hosting/v1/websites and poll
+GET /api/hosting/v1/websites until it appears.
+
+Call GET /api/hosting/v1/wordpress/installations filtered by username and
+domain before proceeding to check whether WordPress is already installed on
+the target domain/path. If WordPress already exists and `overwrite` is false
+(the default), the async job will fail.
+
+This operation is asynchronous: a successful response only means the install
+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.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations`
+
+#### hosting_listWordPressInstallationsV1
+
+List WordPress installations accessible to the authenticated client.
+
+Use this endpoint to discover existing WordPress installations and to poll
+for installation status after calling the install endpoint. When a newly
+requested installation appears in this list, WordPress is ready. Filter by
+username and domain to narrow results to a specific website.
+
+Each installation includes a `valid` flag and, when invalid, a
+`validationError` describing why.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/wordpress/installations`
+
+#### hosting_activateWordPressPluginV1
+
+Activate an installed plugin on a 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).
+
+This operation is asynchronous: a successful response only means the activation
+job has been queued.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/activate`
+
+#### hosting_deactivateWordPressPluginV1
+
+Deactivate an installed plugin on a 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).
+
+This operation is asynchronous: a successful response only means the
+deactivation job has been queued.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/deactivate`
+
+#### hosting_installWordPressPluginsV1
+
+Install one or more plugins on an existing 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). Use GET /api/hosting/v1/wordpress/plugins to discover the plugin
+slugs available for installation.
+
+This operation is asynchronous: a successful response only means the install
+job has been queued, not that the plugins are ready.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install`
+
+#### hosting_listAvailableWordPressPluginsV1
+
+List plugins recommended for installation on a WordPress installation that are
+not yet installed.
+
+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}/plugins/available`
+
+#### hosting_listInstalledWordPressPluginsV1
+
+List plugins installed on a WordPress installation, including their status,
+available updates and known vulnerabilities.
+
+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}/plugins`
+
+#### hosting_searchWordPressPluginsV1
+
+Search the WordPress.org plugin directory for plugins available to install.
+
+Use the returned `slug` values with
+POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/wordpress/plugins`
+
+#### hosting_listSuggestedWordPressPluginsV1
+
+List curated plugin suggestions grouped by website type.
+
+Use the returned `slug` values with
+POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/wordpress/plugins/suggested`
+
+#### hosting_checkIfWooCommerceIsInstalledV1
+
+Check whether WooCommerce is installed on any WordPress installation of a
+domain. Optionally filter by domain to scope the check.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/wordpress/plugins/is-woocommerce-installed`
+
+#### hosting_uninstallWordPressPluginsV1
+
+Uninstall one or more plugins from a 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).
+
+This operation is asynchronous: a successful response only means the uninstall
+job has been queued.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/uninstall`
+
+#### hosting_updateHostingerWordPressPluginV1
+
+Update a Hostinger plugin to its latest version on a 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).
+
+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}/plugins/hostinger/update`
+
+#### hosting_updateWordPressPluginsV1
+
+Update one or more installed plugins to their latest version on a 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).
+
+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}/plugins/update`
+
+#### hosting_activateWordPressThemeV1
+
+Activate an installed theme on a 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).
+
+This operation is asynchronous: a successful response only means the activation
+job has been queued.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/themes/activate`
+
+#### hosting_installWordPressThemeV1
+
+Install a theme on an existing 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).
+
+When the theme is one of the Hostinger themes (hostinger-blog,
+hostinger-affiliate-theme, hostinger-ai-theme), the optional `palette`,
+`layout`, and `font` fields are forwarded to the custom installer (defaults:
+palette1, layout1, default). For any other theme they are ignored.
+
+This operation is asynchronous: a successful response only means the install
+job has been queued, not that the theme is ready.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/themes/install`
+
+#### hosting_listInstalledWordPressThemesV1
+
+List themes installed on a WordPress installation, including their status,
+available updates and known vulnerabilities.
+
+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}/themes`
+
+#### hosting_listWordPressThemesV1
+
+List WordPress themes available to install.
+
+Use the returned `slug` values with
+POST /api/hosting/v1/accounts/{username}/wordpress/{software}/themes/install.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/wordpress/themes`
+
+#### hosting_uninstallWordPressThemesV1
+
+Uninstall one or more themes from a 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).
+
+This operation is asynchronous: a successful response only means the uninstall
+job has been queued.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/themes/uninstall`
+
+#### hosting_updateWordPressThemesV1
+
+Update one or more installed themes to their latest version on a 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).
+
+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}/themes/update`

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "0.3.2",
+  "version": "1.1.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": "0.3.2",
+  "version": "1.1.0",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {
@@ -26,7 +26,8 @@
     "hostinger-horizons-mcp": "./src/servers/horizons.js",
     "hostinger-hosting-mcp": "./src/servers/hosting.js",
     "hostinger-reach-mcp": "./src/servers/reach.js",
-    "hostinger-vps-mcp": "./src/servers/vps.js"
+    "hostinger-vps-mcp": "./src/servers/vps.js",
+    "hostinger-wordpress-mcp": "./src/servers/wordpress.js"
   },
   "scripts": {
     "start": "node src/servers/all.js",

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/hostinger/api-mcp-server",
     "source": "github"
   },
-  "version": "0.3.2",
+  "version": "1.1.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "hostinger-api-mcp",
-      "version": "0.3.2",
+      "version": "1.1.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 0.22.1
+ * Generated from OpenAPI spec version 1.1.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 0.22.1
+ * Generated from OpenAPI spec version 1.1.0
  */
 class MCPServer {
   private readonly name: string;