hostinger-api-mcp 1.5.0 → 1.5.3

package/README.md

@@ -49,13 +49,14 @@ pnpm update -g hostinger-api-mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (203 total)
+- `hostinger-api-mcp` — unified server with every tool (212 total)
+- `hostinger-agency-hosting-mcp` — 11 tools for agency-hosting
 - `hostinger-billing-mcp` — 7 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
 - `hostinger-domains-mcp` — 18 tools for domains
 - `hostinger-ecommerce-mcp` — 12 tools for ecommerce
 - `hostinger-horizons-mcp` — 2 tools for horizons
-- `hostinger-hosting-mcp` — 47 tools for hosting
+- `hostinger-hosting-mcp` — 45 tools for hosting
 - `hostinger-reach-mcp` — 12 tools for reach
 - `hostinger-vps-mcp` — 62 tools for vps
 - `hostinger-wordpress-mcp` — 35 tools for wordpress
@@ -200,6 +201,130 @@ console.log("Tool result:", result);
 
 This MCP server provides the following tools:
 
+### `hostinger-agency-hosting-mcp`
+
+#### agency-hosting_listAvailableDatacentersForAnAgencyPlanOrderV1
+
+Lists the datacenters available for provisioning a new website on the given Agency Plan
+hosting order.
+
+Each datacenter includes a `pinger_url` you can ping from the client to measure round-trip
+latency; comparing the results across datacenters lets you pick the nearest one (lowest
+ping) before choosing its `code` as the `datacenter_code` when creating a website setup.
+
+- **Method**: `GET`
+- **Path**: `/api/agency-hosting/v1/orders/{order_id}/datacenters`
+
+#### agency-hosting_changeAgencyPlanWebsiteDomainV1
+
+Changes the primary domain for an Agency Plan website.
+
+Provide the current domain in the path and the new domain in the request body.
+Set domain to null to revert to the temporary domain.
+
+- **Method**: `PUT`
+- **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{from_domain}`
+
+#### agency-hosting_linkDomainToAgencyPlanWebsiteV1
+
+Links a domain to the specified Agency Plan website so it can serve traffic for that domain.
+
+- **Method**: `POST`
+- **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains`
+
+#### agency-hosting_listAgencyPlanDomainsV1
+
+Returns a paginated list of domains associated with Agency Plan websites accessible to the authenticated client.
+
+Use the website_uuids filter to narrow results to specific websites.
+
+- **Method**: `GET`
+- **Path**: `/api/agency-hosting/v1/domains`
+
+#### agency-hosting_unlinkDomainFromAgencyPlanWebsiteV1
+
+Unlinks a domain from the specified Agency Plan website.
+
+The website stops serving traffic on this domain immediately.
+
+Website files and database are preserved, and any other linked domains remain accessible.
+
+If this is the only domain on the website, unlinking leaves the website without an accessible domain.
+
+- **Method**: `DELETE`
+- **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}`
+
+#### agency-hosting_provisionANewAgencyPlanWebsiteV1
+
+Provisions a new website on one of your Agency Plan hosting orders.
+
+Choose the datacenter, stack (`flavor`), and PHP version for the site. Optionally attach
+your own `domain` — omit it, set it to `null`, or leave it unavailable and a free
+`*.hostingersite.com` subdomain is generated instead — and/or install WordPress by
+supplying the `wordpress` details (admin account, site title, and language).
+
+Common setups:
+- **Plain PHP site**: `flavor` set to `php-fpm`, with `settings.php.version`; omit
+  `wordpress` and `type`.
+- **WordPress site**: `flavor` set to the desired WordPress version (e.g. `wp-7.0`), plus
+  the `wordpress` block (admin account, title, language).
+- **Static/Node.js frontend app**: `flavor` set to `php-fpm` and `type` set to
+  `node-static`.
+
+Provisioning runs in the background, so the response returns immediately with a setup UUID
+that identifies the job. The new website becomes reachable once provisioning finishes.
+
+- **Method**: `POST`
+- **Path**: `/api/agency-hosting/v1/orders/{order_id}/websites/setups`
+
+#### agency-hosting_getAgencyPlanWebsiteSetupStatusV1
+
+Returns the current status of an Agency Plan website setup started via the setups
+endpoint.
+
+Poll this endpoint using the `setup_uuid` returned from the provisioning request until
+`status` becomes `completed`, at which point `website_uid` identifies the new website.
+
+- **Method**: `GET`
+- **Path**: `/api/agency-hosting/v1/orders/{order_id}/websites/setups/{setup_uuid}`
+
+#### agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1
+
+Builds and deploys a Node.js application for an Agency Plan website from an already-uploaded archive.
+
+Upload the archive to file browser first, then provide its relative path from document root in this request.
+Website contents are overwritten by the build result, which is deployed to public_html.
+
+- **Method**: `POST`
+- **Path**: `/api/agency-hosting/v1/websites/{website_uid}/build-assets`
+
+#### agency-hosting_getAgencyPlanWebsiteDetailsV1
+
+Retrieves detailed information about a specific Agency Plan website, including configuration,
+status, metadata, hosting plan details, and resource quotas.
+
+- **Method**: `GET`
+- **Path**: `/api/agency-hosting/v1/websites/{website_uid}`
+
+#### agency-hosting_deleteAgencyPlanWebsiteV1
+
+Deletes an Agency Plan website and schedules cleanup of its resources.
+
+This action is irreversible. Website files, databases, and linked domains are removed.
+
+- **Method**: `DELETE`
+- **Path**: `/api/agency-hosting/v1/websites/{website_uid}`
+
+#### agency-hosting_listRunningAgencyPlanWebsiteProcessesV1
+
+Lists active and recently completed asynchronous processes for an Agency Plan website.
+
+Each process has a unique ID (for tracking), a type, and a status (running, completed, failed).
+Poll this endpoint after initiating async operations (SSL setup, backups, cloning) to track progress.
+
+- **Method**: `GET`
+- **Path**: `/api/agency-hosting/v1/websites/{website_uid}/processes`
+
 ### `hostinger-billing-mcp`
 
 #### billing_getCatalogItemListV1
@@ -754,44 +879,27 @@ installation living in a subdirectory, pass the directory query parameter to cle
 - **Method**: `DELETE`
 - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/clear`
 
-#### hosting_disableCachelessModeV1
+#### hosting_toggleCachelessModeV1
 
-Turns off development (cacheless) mode and returns the website to normal caching. Use it after
+Turns development (cacheless) mode on or off, based on the enabled flag. When enabled, nothing
+is cached, effectively turning off all caching for the website; use it while actively developing,
+testing changes, debugging issues, or when real-time updates must be visible. Disable it after
 finishing development work to restore the performance benefits of caching.
 
 - **Method**: `PATCH`
-- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cacheless-mode/disable`
-
-#### hosting_disableWebsiteCacheV1
-
-Turns off server-side caching for the website until it is enabled again. May impact performance.
-Use it when experiencing cache-related issues; to temporarily bypass caching while developing
-or debugging, prefer enabling cacheless mode instead.
-
-Does nothing if caching is already disabled.
-
-- **Method**: `PATCH`
-- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/disable`
-
-#### hosting_enableCachelessModeV1
-
-Enables development (cacheless) mode where nothing is cached, effectively turning off all
-caching for the website. Use it while actively developing, testing changes, debugging issues,
-or when real-time updates must be visible. Disable cacheless mode afterwards to restore
-normal caching.
-
-- **Method**: `PATCH`
-- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cacheless-mode/enable`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cacheless-mode/toggle`
 
-#### hosting_enableWebsiteCacheV1
+#### hosting_toggleWebsiteCacheV1
 
-Turns on server-side caching for the website for better performance. Use it for faster page
-loads, reduced server load, or improved user experience. Recommended for production websites.
+Turns server-side caching for the website on or off, based on the enabled flag. Enable it for
+faster page loads, reduced server load, and improved user experience; recommended for production
+websites. Disabling may impact performance; to temporarily bypass caching while developing or
+debugging, prefer toggling cacheless mode instead.
 
-Does nothing if caching is already enabled.
+Does nothing if caching is already in the requested state.
 
 - **Method**: `PATCH`
-- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/enable`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/toggle`
 
 #### hosting_listAccountCronJobsV1
 
@@ -1055,7 +1163,7 @@ Log content may contain ANSI escape sequences (color codes).
 - **Method**: `GET`
 - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/{uuid}/logs`
 
-#### hosting_restartNode.jsApplicationV1
+#### hosting_restartNode_jsApplicationV1
 
 Restarts the Node.js server process for the website. Does not rebuild or redeploy the
 application. Use it to apply environment or configuration changes, or to recover a hung

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.5.0",
+  "version": "1.5.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": "1.5.0",
+  "version": "1.5.3",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {
@@ -19,6 +19,7 @@
   "main": "./src/servers/all.js",
   "bin": {
     "hostinger-api-mcp": "./src/servers/all.js",
+    "hostinger-agency-hosting-mcp": "./src/servers/agency-hosting.js",
     "hostinger-billing-mcp": "./src/servers/billing.js",
     "hostinger-dns-mcp": "./src/servers/dns.js",
     "hostinger-domains-mcp": "./src/servers/domains.js",
@@ -44,7 +45,7 @@
     "tus-js-client": "^4.1.0"
   },
   "devDependencies": {
-    "@types/node": "^24.0.0",
+    "@types/node": "^26.1.1",
     "@types/express": "^5.0.0",
     "@types/cors": "^2.8.17",
     "@types/minimist": "^1.2.5",

package/server.json

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