# hostinger-api-mcp Model Context Protocol (MCP) server for Hostinger API. ## Quick start: Hosted remote server If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server: ``` https://mcp.hostinger.com ``` ### Claude Code ```bash claude mcp add --transport http hostinger https://mcp.hostinger.com ``` This opens a browser window to authorize via OAuth. Once approved, all tools below are available in your session. ### Other MCP-compatible clients Add `https://mcp.hostinger.com` as a remote Streamable HTTP MCP server in your client's configuration and complete the OAuth prompt when it appears. Refer to your client's docs for how it exposes "add remote MCP server" / "custom connector" settings. ## Prerequisites - Node.js version 24 or higher If you don't have Node.js installed, you can download it from the [official website](https://nodejs.org/en/download/). Alternatively, you can use a package manager like [Homebrew](https://brew.sh/) (for macOS) or [Chocolatey](https://chocolatey.org/) (for Windows) to install Node.js. We recommend using [NVM (Node Version Manager)](https://github.com/nvm-sh/nvm) to install and manage installed Node.js versions. After installing NVM, you can install Node.js with the following command: ```bash nvm install v24 nvm use v24 ``` ## Installation To install the MCP server, run one of the following command, depending on your package manager: ```bash # Install globally from npm npm install -g hostinger-api-mcp # Or with yarn yarn global add hostinger-api-mcp # Or with pnpm pnpm add -g hostinger-api-mcp ``` ## Update To update the MCP server to the latest version, use one of the following commands, depending on your package manager: ```bash # Update globally from npm npm update -g hostinger-api-mcp # Or with yarn yarn global upgrade hostinger-api-mcp # Or with pnpm pnpm update -g hostinger-api-mcp ``` ## Binaries This package installs the following MCP server commands: - `hostinger-api-mcp` — unified server with every tool (371 total) - `hostinger-agency-hosting-mcp` — 38 tools for agency-hosting - `hostinger-billing-mcp` — 9 tools for billing - `hostinger-dns-mcp` — 8 tools for dns - `hostinger-domains-mcp` — 40 tools for domains - `hostinger-ecommerce-mcp` — 29 tools for ecommerce - `hostinger-horizons-mcp` — 2 tools for horizons - `hostinger-hosting-mcp` — 58 tools for hosting - `hostinger-mail-mcp` — 38 tools for mail - `hostinger-reach-mcp` — 49 tools for reach - `hostinger-vps-mcp` — 62 tools for vps - `hostinger-wordpress-mcp` — 38 tools for wordpress Pick the binary that matches your agent's scope. `hostinger-api-mcp` remains the backwards-compatible default. ## Configuration The following environment variables can be configured when running the server: - `DEBUG`: Enable debug logging (true/false) (default: false) - `HOSTINGER_API_TOKEN`: Your API token, which will be sent in the `Authorization` header. When set, OAuth is bypassed entirely. - `API_TOKEN`: Deprecated alias for `HOSTINGER_API_TOKEN`. Will be removed in a future version — prefer `HOSTINGER_API_TOKEN`. - `OAUTH_ISSUER`: OAuth server base URL (default: `https://auth.hostinger.com`). Only used when `HOSTINGER_API_TOKEN` is not set. ## Authentication The server supports two authentication methods: ### API Token (recommended for CI/scripts) Set `HOSTINGER_API_TOKEN` in the environment or `.env` file. When present it always takes precedence — no OAuth code runs. ### OAuth 2.0 with PKCE (interactive sign-in) When `HOSTINGER_API_TOKEN` is not set and the server runs in stdio mode, OAuth 2.0 with PKCE is used automatically on the first authenticated tool call: 1. A dynamic OAuth client is registered with the issuer (RFC 7591) — once per machine. 2. A browser window opens to the authorization page. 3. After sign-in, the server captures the redirect on a local ephemeral port, exchanges the code for tokens, and stores them. 4. Subsequent calls reuse the stored access token; expired tokens are refreshed automatically. If a refresh token is revoked, the browser flow is re-launched. Credentials are stored at: - macOS / Linux: `~/.config/hostinger-mcp/credentials.json` (mode 0600) - Windows: `%APPDATA%\hostinger-mcp\credentials.json` Credentials are shared across all Hostinger MCP binaries (`hostinger-api-mcp`, `hostinger-vps-mcp`, etc.). **Manual commands:** ```bash # Run the OAuth sign-in flow immediately (don't wait for the first tool call) hostinger-api-mcp --login # Revoke stored credentials hostinger-api-mcp --logout ``` **HTTP transport note:** OAuth sign-in is not supported in `--http` mode. Set `HOSTINGER_API_TOKEN` before using `--http`. ## Usage ### JSON configuration for Claude, Cursor, etc. ```json { "mcpServers": { "hostinger-api": { "command": "hostinger-api-mcp", "env": { "DEBUG": "false", "HOSTINGER_API_TOKEN": "YOUR API TOKEN" } } } } ``` ### Transport Options The MCP server supports two transport modes: #### Standard I/O Transport The server can use standard input / output (stdio) transport (default). This provides local streaming: #### Streamable HTTP Transport The server can use HTTP streaming transport. This provides bidirectional streaming over HTTP: ```bash # Default HTTP transport on localhost:8100 hostinger-api-mcp --http # Specify custom host and port hostinger-api-mcp --http --host 0.0.0.0 --port 8150 ``` #### Command Line Options ``` Options: --http Use HTTP streaming transport (requires HOSTINGER_API_TOKEN env var) --stdio Use Server-Sent Events transport (default) --host {host} Hostname or IP address to listen on (default: 127.0.0.1) --port {port} Port to bind to (default: 8100) --login Run OAuth sign-in flow and exit --logout Revoke stored OAuth credentials and exit --help Show help message ``` ### Using as an MCP Tool Provider This server implements the Model Context Protocol (MCP) and can be used with any MCP-compatible consumer. Example of connecting to this server using HTTP streaming transport: ```javascript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; // Create HTTP transport const transport = new StreamableHTTPClientTransport({ url: "http://localhost:8100/", headers: { "Authorization": `Bearer ${process.env.HOSTINGER_API_TOKEN}` } }); // Connect to the MCP server const client = new Client({ name: "my-client", version: "1.0.0" }, { capabilities: {} }); await client.connect(transport); // List available tools const { tools } = await client.listTools(); console.log("Available tools:", tools); // Call a tool const result = await client.callTool({ name: "billing_getCatalogItemListV1", arguments: { category: "DOMAIN" } }); console.log("Tool result:", result); ``` ## Available Tools This MCP server provides the following tools: ### `hostinger-agency-hosting-mcp` #### agency-hosting_deployNodeStaticWebsite Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain. - **Method**: `custom` - **Path**: `custom` #### agency-hosting_deployPhpApplication Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain. - **Method**: `custom` - **Path**: `custom` #### agency-hosting_listAvailableDatacentersV1 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_changeWebsiteDomainV1 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_linkDomainToWebsiteV1 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_listDomainsV1 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_unlinkDomainFromWebsiteV1 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_generateUploadURLV1 Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website's file storage. Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website's file storage via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below. 1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or `PATCH` requests with an `upload-offset` header tracking progress) until complete. `relative_file_path` is the destination path inside the website's file storage, e.g. `app.zip`. Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z "$FILE") # stat -c%s on Linux curl -i -X POST "{url}/${FILE}?override=true" \ -H "X-Auth: {auth_key}" \ -H "X-Auth-Rest: {rest_auth_key}" \ -H "Tus-Resumable: 1.0.0" \ -H "Upload-Length: ${SIZE}" \ -H "Upload-Offset: 0" # -> 201 Created curl -i -X PATCH "{url}/${FILE}?override=true" \ -H "X-Auth: {auth_key}" \ -H "X-Auth-Rest: {rest_auth_key}" \ -H "Tus-Resumable: 1.0.0" \ -H "Content-Type: application/offset+octet-stream" \ -H "Upload-Offset: 0" \ --data-binary "@${FILE}" # -> 204 No Content, Upload-Offset response header equals SIZE when done ``` - **Method**: `POST` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/files/upload-urls` #### agency-hosting_importWebsiteFromArchiveV1 Imports an Agency Plan website from an already-uploaded archive. Upload the archive to the website's root directory via file browser first, then provide its filename in this request. Website contents are overwritten by the archive contents. Supported archive types: .zip, .tar, .tar.gz, .tgz. - **Method**: `POST` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/files/import-archive` #### agency-hosting_listAgencyPlanOrderDiskUsageMetricsV1 Returns aggregated disk and inode usage for the Agency Plan order over the selected time frame, plus the plan quotas. Figures cover the whole order account. Values may be up to one hour stale. CPU, memory, and process usage are on the resource-usage-metrics endpoint. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/orders/{order_id}/disk-usage-metrics` #### agency-hosting_listOrdersV1 Returns a paginated list of Agency Plan orders accessible to the authenticated client. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/orders` #### agency-hosting_listOrderResourceUsageMetricsV1 Returns aggregated CPU, memory, and process usage for the Agency Plan order over the selected time frame, plus the plan quotas and a per-website breakdown. Each website is identified by uid. Suspended and deleted websites are excluded from both the order totals and the per-website breakdown. Values may be up to one hour stale. Disk and inode usage are on the disk-usage-metrics endpoint. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/orders/{order_id}/resource-usage-metrics` #### agency-hosting_listPHPExtensionsForAWebsiteV1 Lists every PHP extension available to an Agency Plan website and whether it is currently enabled. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/extensions` #### agency-hosting_replaceWebsitePHPExtensionsV1 Replaces the set of PHP extensions enabled on an Agency Plan website with the ones provided. Any toggleable extension not in the request is disabled, so call the extensions endpoint first and send the full desired set. Extensions compiled into PHP, reported with the "built-in" state, are always active and are unaffected. - **Method**: `PUT` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/extensions` #### agency-hosting_listPHPOptionsForAWebsiteV1 Lists the php.ini directives that can be configured for an Agency Plan website, each with its default, the value currently in effect, and the values it accepts. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/options` #### agency-hosting_replaceWebsitePHPOptionsV1 Replaces the custom php.ini values on an Agency Plan website with the ones provided. Any option not in the request is reset to its default, so call the options endpoint first and send the full desired set. Sending an empty array resets every option to its default. - **Method**: `PUT` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/options` #### agency-hosting_listAvailablePHPVersionsForAnOrderV1 Lists the PHP versions available to websites created under an Agency Plan order, determined by the server the order is hosted on. Use this before creating a website; for a website that already exists, call the website-scoped versions endpoint instead. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/orders/{order_id}/websites/php-settings/versions` #### agency-hosting_listAvailablePHPVersionsForAWebsiteV1 Lists the PHP versions an Agency Plan website can be switched to. The version the website is currently running is returned as settings.php.version by the website details endpoint. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/versions` #### agency-hosting_updateWebsitePHPVersionV1 Switches an Agency Plan website to a different PHP version. Call the available versions endpoint first to see which versions can be selected. The website restarts on the new version, so requests served during the switch may fail and code that is incompatible with the target version will break. - **Method**: `PATCH` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/version` #### agency-hosting_createANewWebsiteV1 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_getWebsiteSetupStatusV1 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_buildWebsiteNodeJSAssetsV1 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_clearWebsiteCacheV1 Clears cache for all domains associated with an Agency Plan website, including its preview domain. This operation clears all cache types for the website. - **Method**: `DELETE` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cache` #### agency-hosting_listWebsiteCronJobsV1 Returns a paginated list of cron jobs configured for an Agency Plan website. Each entry includes the schedule expression and the command executed on that schedule. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cron-jobs` #### agency-hosting_createWebsiteCronJobV1 Creates a cron job for an Agency Plan website from a schedule expression and a command. Returns the created cron job, including its uuid, which is required to delete the cron job. - **Method**: `POST` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cron-jobs` #### agency-hosting_deleteWebsiteCronJobV1 Permanently deletes the cron job identified by its uuid from an Agency Plan website. The operation is idempotent: deleting a cron job that does not exist succeeds without error. - **Method**: `DELETE` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cron-jobs/{uuid}` #### agency-hosting_listWebsiteDatabasesV1 Returns a paginated list of MySQL databases created for an Agency Plan website. Each entry includes the database's non-system users. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases` #### agency-hosting_createWebsiteDatabaseV1 Creates a MySQL database with a dedicated user for an Agency Plan website. The database name, username, and password must all be provided by the caller. - **Method**: `POST` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases` #### agency-hosting_deleteWebsiteDatabaseV1 Permanently deletes a MySQL database and all its data from an Agency Plan website, including its users. The operation is idempotent: deleting a database that does not exist succeeds without error. - **Method**: `DELETE` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}` #### agency-hosting_createWebsiteDatabaseUserV1 Creates a user for an existing database on an Agency Plan website. Each database supports a single non-system user; creating a user for a database that already has one fails. - **Method**: `POST` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}/users` #### agency-hosting_deleteWebsiteDatabaseUserV1 Permanently deletes a database user from an Agency Plan website database, revoking all access it had. The operation is idempotent: deleting a user that does not exist succeeds without error. - **Method**: `DELETE` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}/users/{database_user_name}` #### agency-hosting_getWebsiteDetailsV1 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_deleteWebsiteV1 Permanently deletes an Agency Plan website. Deletion is processed asynchronously: the website is immediately transitioned to a deleting state and the underlying server resources are removed in the background. - **Method**: `DELETE` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}` #### agency-hosting_listAgencyPlanWebsitesV1 Retrieve a paginated list of Agency Plan websites (H5G, Builder, and Horizons) accessible to the authenticated client. This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you. The response shape differs per platform — see the `platform` field on each item. Use `website_types` to list only websites of a given detected type, e.g. only WordPress websites (`website_types=wordpress`) or only Node.js websites (`website_types=nodejs`). Combine with `order_ids`, `states`, or `domain` for more targeted results. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites` #### agency-hosting_listWebsiteProcessesV1 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` #### agency-hosting_changeWordPressVersionV1 Changes the installed WordPress core version on an Agency Plan website to one of the versions available for installation. - **Method**: `PATCH` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings/version` #### agency-hosting_getWordPressSettingsV1 Returns the current WordPress settings for an Agency Plan website: installed core version, LiteSpeed Cache plugin status, object cache status, and maintenance mode status. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings` #### agency-hosting_listAvailableWordPressVersionsV1 Lists the WordPress core versions available for installation on an Agency Plan website. - **Method**: `GET` - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings/versions` ### `hostinger-billing-mcp` #### billing_getCatalogItemListV1 Retrieve catalog items available for order. Prices in catalog items is displayed as cents (without floating point), e.g: float `17.99` is displayed as integer `1799`. Use this endpoint to view available services and pricing before placing orders. - **Method**: `GET` - **Path**: `/api/billing/v1/catalog` #### billing_createPurchaseOrderV1 Create a purchase order for any Hostinger product. This unified endpoint places an order for one or more catalog items and works across all Hostinger products, leveraging the existing billing infrastructure. Use the [catalog endpoint](#tag/billing-catalog) to look up the `item_id` values available for purchase. If no payment method is provided, your default payment method will be used automatically. This endpoint only places the order. Product-specific provisioning (e.g. VPS setup or domain registration) is not performed here — once the order completes, use the relevant product endpoints or [hPanel](https://hpanel.hostinger.com/) to finalize setup. Use this endpoint to purchase any product available in the catalog. - **Method**: `POST` - **Path**: `/api/billing/v1/orders` #### billing_setDefaultPaymentMethodV1 Set the default payment method for your account. Use this endpoint to configure the primary payment method for future orders. - **Method**: `POST` - **Path**: `/api/billing/v1/payment-methods/{paymentMethodId}` #### billing_deletePaymentMethodV1 Delete a payment method from your account. Use this endpoint to remove unused payment methods from user accounts. - **Method**: `DELETE` - **Path**: `/api/billing/v1/payment-methods/{paymentMethodId}` #### billing_getPaymentMethodListV1 Retrieve available payment methods that can be used for placing new orders. If you want to add new payment method, please use [hPanel](https://hpanel.hostinger.com/billing/payment-methods). Use this endpoint to view available payment options before creating orders. - **Method**: `GET` - **Path**: `/api/billing/v1/payment-methods` #### billing_getSubscriptionListV1 Retrieve a list of all subscriptions associated with your account. Use this endpoint to monitor active services and billing status. - **Method**: `GET` - **Path**: `/api/billing/v1/subscriptions` #### billing_disableAutoRenewalV1 Disable auto-renewal for a subscription. Use this endpoint when disable auto-renewal for a subscription. - **Method**: `DELETE` - **Path**: `/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/disable` #### billing_enableAutoRenewalV1 Enable auto-renewal for a subscription. Use this endpoint when enable auto-renewal for a subscription. - **Method**: `PATCH` - **Path**: `/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable` #### billing_renewSubscriptionV1 Create a renewal order for an existing Hostinger subscription. This endpoint places a renewal order for a single subscription, leveraging the existing billing infrastructure. Use the [subscriptions endpoint](#tag/billing-subscriptions) to look up the `subscriptionId` values available for renewal. If no payment method is provided, your default payment method will be used automatically. Use this endpoint to renew any subscription available in your account. - **Method**: `POST` - **Path**: `/api/billing/v1/subscriptions/{subscriptionId}/renew` ### `hostinger-dns-mcp` #### DNS_getDNSSnapshotV1 Retrieve particular DNS snapshot with contents of DNS zone records. Use this endpoint to view historical DNS configurations for domains. - **Method**: `GET` - **Path**: `/api/dns/v1/snapshots/{domain}/{snapshotId}` #### DNS_getDNSSnapshotListV1 Retrieve DNS snapshots for a domain. Use this endpoint to view available DNS backup points for restoration. - **Method**: `GET` - **Path**: `/api/dns/v1/snapshots/{domain}` #### DNS_restoreDNSSnapshotV1 Restore DNS zone to the selected snapshot. Use this endpoint to revert domain DNS to a previous configuration. - **Method**: `POST` - **Path**: `/api/dns/v1/snapshots/{domain}/{snapshotId}/restore` #### DNS_getDNSRecordsV1 Retrieve DNS zone records for a specific domain. Use this endpoint to view current DNS configuration for domain management. - **Method**: `GET` - **Path**: `/api/dns/v1/zones/{domain}` #### DNS_updateDNSRecordsV1 Update DNS records for the selected domain. Using `overwrite = true` will replace existing records with the provided ones. Otherwise existing records will be updated and new records will be added. Use this endpoint to modify domain DNS configuration. - **Method**: `PUT` - **Path**: `/api/dns/v1/zones/{domain}` #### DNS_deleteDNSRecordsV1 Delete DNS records for the selected domain. To filter which records to delete, add the `name` of the record and `type` to the filter. Multiple filters can be provided with single request. If you have multiple records with the same name and type, and you want to delete only part of them, refer to the `Update zone records` endpoint. Use this endpoint to remove specific DNS records from domains. - **Method**: `DELETE` - **Path**: `/api/dns/v1/zones/{domain}` #### DNS_resetDNSRecordsV1 Reset DNS zone to the default records. Use this endpoint to restore domain DNS to original configuration. - **Method**: `POST` - **Path**: `/api/dns/v1/zones/{domain}/reset` #### DNS_validateDNSRecordsV1 Validate DNS records prior to update for the selected domain. If the validation is successful, the response will contain `200 Success` code. If there is validation error, the response will fail with `422 Validation error` code. Use this endpoint to verify DNS record validity before applying changes. - **Method**: `POST` - **Path**: `/api/dns/v1/zones/{domain}/validate` ### `hostinger-domains-mcp` #### v2_getDomainVerificationsDIRECT Retrieve a list of pending and completed domain verifications. - **Method**: `GET` - **Path**: `/api/v2/direct/verifications/active` #### domains_suggestDomainNamesFromADescriptionV1 Suggest available domain names based on a free-text description of your project. Suggestions are generated by an AI model, so they differ between calls. Endpoint has rate limit of 90 requests per minute. Use this endpoint to find a domain name when you only know what the website is about. - **Method**: `POST` - **Path**: `/api/domains/v1/availability/alternatives-from-description` #### domains_suggestDomainNamesFromADomainV1 Suggest available domain names based on a domain name you already have in mind. Suggestions are generated by an AI model, so they differ between calls. Endpoint has rate limit of 90 requests per minute. Use this endpoint when the domain you wanted is taken and you need close alternatives. - **Method**: `POST` - **Path**: `/api/domains/v1/availability/alternatives-from-domain` #### domains_checkDomainAvailabilityV1 Check availability of domain names across multiple TLDs. Multiple TLDs can be checked at once. If you want alternative domains with response, provide only one TLD and set `with_alternatives` to `true`. TLDs should be provided without leading dot (e.g. `com`, `net`, `org`). Endpoint has rate limit of 90 requests per minute. Use this endpoint to verify domain availability before purchase. - **Method**: `POST` - **Path**: `/api/domains/v1/availability` #### domains_getDomainForwardingV1 Retrieve domain forwarding data. Use this endpoint to view current redirect configuration for domains. - **Method**: `GET` - **Path**: `/api/domains/v1/forwarding/{domain}` #### domains_updateDomainForwardingV1 Update domain forwarding configuration. Use this endpoint to modify existing redirect configuration for domains. - **Method**: `PUT` - **Path**: `/api/domains/v1/forwarding/{domain}` #### domains_deleteDomainForwardingV1 Delete domain forwarding data. Use this endpoint to remove redirect configuration from domains. - **Method**: `DELETE` - **Path**: `/api/domains/v1/forwarding/{domain}` #### domains_createDomainForwardingV1 Create domain forwarding configuration. Use this endpoint to set up domain redirects to other URLs. - **Method**: `POST` - **Path**: `/api/domains/v1/forwarding` #### domains_getPendingIRTPVerificationV1 Retrieve a pending IRTP verification for a domain. Both the old and new registrant must confirm it before the WHOIS change takes effect. Use this endpoint to check the status of a WHOIS change awaiting registrant confirmation. - **Method**: `GET` - **Path**: `/api/domains/v1/irtp/{domain}` #### domains_cancelPendingIRTPVerificationV1 Cancel a pending IRTP verification. Use this endpoint to back out of a WHOIS change that is stuck waiting on registrant confirmation, for example when the confirmation email cannot be received, without waiting out the 5-day expiry. - **Method**: `DELETE` - **Path**: `/api/domains/v1/irtp/{domain}` #### domains_getIncomingDomainMoveV1 Retrieve the incoming move for a specified domain. Returns 404 when no account is moving this domain to you. Use this endpoint to check whether a domain addressed to you is still waiting to be accepted. - **Method**: `GET` - **Path**: `/api/domains/v1/move/incoming/{domain}` #### domains_acceptIncomingDomainMoveV1 Accept an incoming move for a specified domain. The provided WHOIS profiles become the contacts of the domain, so they must belong to your account and satisfy the requirements of the TLD. Only the contact types the domain actually uses are applied, but all four profile IDs have to be provided. The move has to still be waiting for your decision, already accepted moves cannot be accepted again. Accepting does not complete the move. A confirmation email is sent to the email address of the new owner contact, and the domain changes hands only after the change is confirmed from it. Until then the move stays in the `activating` status, which can be followed with the [incoming move endpoint](#tag/domains-move). Use this endpoint to take ownership of a domain offered to you. - **Method**: `PUT` - **Path**: `/api/domains/v1/move/incoming/{domain}` #### domains_rejectIncomingDomainMoveV1 Reject an incoming move for a specified domain. The domain stays in the account which initiated the move. Moves you have already accepted cannot be rejected anymore. Use this endpoint to decline a domain you do not want to take over. - **Method**: `DELETE` - **Path**: `/api/domains/v1/move/incoming/{domain}` #### domains_getIncomingDomainMoveListV1 Retrieve all domains other Hostinger accounts are moving to your account. Moves of every status are returned, including the ones which already completed. Use this endpoint to find domains waiting for you to accept them. - **Method**: `GET` - **Path**: `/api/domains/v1/move/incoming` #### domains_getOutgoingDomainMoveV1 Retrieve the outgoing move for a specified domain. Returns 404 when the domain has no move in progress. Use this endpoint to track the status of a move you have initiated for a single domain. - **Method**: `GET` - **Path**: `/api/domains/v1/move/outgoing/{domain}` #### domains_startOutgoingDomainMoveV1 Initiate a move of a specified domain to another Hostinger account. The receiving account has to already exist and accept the move before the domain changes hands. The domain must be active. The subscription it belongs to is resolved automatically, and the request is rejected with a 404 status code when the domain has no domain subscription of its own. Domains protected by premium protection require an additional verification step, such requests are rejected with a 428 status code. Use this endpoint to hand a domain over to another Hostinger user. - **Method**: `POST` - **Path**: `/api/domains/v1/move/outgoing/{domain}` #### domains_cancelOutgoingDomainMoveV1 Cancel an outgoing move for a specified domain. The move can only be cancelled while the receiving account has not accepted it yet. The domain stays in your account. Use this endpoint to withdraw a move you no longer want to complete. - **Method**: `DELETE` - **Path**: `/api/domains/v1/move/outgoing/{domain}` #### domains_getOutgoingDomainMoveListV1 Retrieve all domains you are moving to other Hostinger accounts. Only moves which have not completed yet are returned. Use this endpoint to track moves you have initiated and the accounts they are addressed to. - **Method**: `GET` - **Path**: `/api/domains/v1/move/outgoing` #### domains_getDomainAuthorizationCodeV1 Retrieve the authorization (EPP) code for a specified domain so it can be transferred away from Hostinger to another registrar. Requesting a new code invalidates any code retrieved previously. Use this endpoint to obtain the code required to transfer a domain to another registrar. - **Method**: `GET` - **Path**: `/api/domains/v1/portfolio/{domain}/auth-code` #### domains_claimFreeDomainV1 Claim a free domain available on your account and register it. Unlike purchasing a domain, this consumes a free domain you already have, so no payment method is required. A successful response means the domain is registered. If registration fails, login to [hPanel](https://hpanel.hostinger.com/) and check domain registration status. If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account. Some TLDs require `additional_details` to be provided and these will be validated before claiming. Requests which cannot be fulfilled are rejected with an error code in the response body, for example `2037` when no free domain is available. Use this endpoint to register a domain using a free domain from your account. - **Method**: `POST` - **Path**: `/api/domains/v1/portfolio/claim` #### domains_enableDomainLockV1 Enable domain lock for the domain. When domain lock is enabled, the domain cannot be transferred to another registrar without first disabling the lock. Use this endpoint to secure domains against unauthorized transfers. - **Method**: `PUT` - **Path**: `/api/domains/v1/portfolio/{domain}/domain-lock` #### domains_disableDomainLockV1 Disable domain lock for the domain. Domain lock needs to be disabled before transferring the domain to another registrar. Use this endpoint to prepare domains for transfer to other registrars. - **Method**: `DELETE` - **Path**: `/api/domains/v1/portfolio/{domain}/domain-lock` #### domains_getDomainDetailsV1 Retrieve detailed information for specified domain. Use this endpoint to view comprehensive domain configuration and status. - **Method**: `GET` - **Path**: `/api/domains/v1/portfolio/{domain}` #### domains_getDomainListV1 Retrieve all domains associated with your account. Use this endpoint to view user's domain portfolio. - **Method**: `GET` - **Path**: `/api/domains/v1/portfolio` #### domains_purchaseNewDomainV1 Purchase and register a new domain name. If registration fails, login to [hPanel](https://hpanel.hostinger.com/) and check domain registration status. If no payment method is provided, your default payment method will be used automatically. If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account. Some TLDs require `additional_details` to be provided and these will be validated before completing purchase. Use this endpoint to register new domains for users. - **Method**: `POST` - **Path**: `/api/domains/v1/portfolio` #### domains_enablePrivacyProtectionV1 Enable privacy protection for the domain. When privacy protection is enabled, domain owner's personal information is hidden from public WHOIS database. Use this endpoint to protect domain owner's personal information from public view. - **Method**: `PUT` - **Path**: `/api/domains/v1/portfolio/{domain}/privacy-protection` #### domains_disablePrivacyProtectionV1 Disable privacy protection for the domain. When privacy protection is disabled, domain owner's personal information is visible in public WHOIS database. Use this endpoint to make domain owner's information publicly visible. - **Method**: `DELETE` - **Path**: `/api/domains/v1/portfolio/{domain}/privacy-protection` #### domains_getDomainRenewalInformationV1 Retrieve renewal information for a specified domain, including its status and current expiration date. Use this endpoint to build renewal automation and expiry monitoring for a single domain. - **Method**: `GET` - **Path**: `/api/domains/v1/portfolio/{domain}/renewal` #### domains_updateDomainNameserversV1 Set nameservers for a specified domain. Be aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable. Use this endpoint to configure custom DNS hosting for domains. - **Method**: `PUT` - **Path**: `/api/domains/v1/portfolio/{domain}/nameservers` #### domains_claimFreeDomainTransferV1 Claim a free domain transfer available on your account and start the transfer. Unlike purchasing a transfer, this consumes a free domain transfer you already have, so no payment method is required. Before making request, unlock the domain at the current registrar and get its authorization code. The transfer is validated first, so domains which cannot be transferred are rejected before the free domain transfer is consumed. A successful response means the transfer has been started. Completion depends on the current registrar and can be followed with the [transfer list endpoint](#tag/domains-transfer). If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account. Requests which cannot be fulfilled are rejected with an error code in the response body. Use this endpoint to transfer a domain using a free domain transfer from your account. - **Method**: `POST` - **Path**: `/api/domains/v1/transfers/claim` #### domains_getTransferV1 Retrieve the transfer for a specified domain. Use this endpoint to track an incoming or outgoing registrar transfer and its status. - **Method**: `GET` - **Path**: `/api/domains/v1/transfers/{domain}` #### domains_getTransferListV1 Retrieve all domain transfers in your portfolio. Use this endpoint to monitor incoming and outgoing registrar transfers across your domains. - **Method**: `GET` - **Path**: `/api/domains/v1/transfers` #### domains_changeWHOISProfileForDomainV1 Change WHOIS contact profile for a domain. Repoints the given contact roles to a new WHOIS profile and submits the change to the registry. The profile currently assigned to those roles is resolved automatically; the request fails if the given roles are not all on the same profile today. Changing transfer sensitive fields on the owner contact starts an IRTP verification. The change is processed asynchronously. Use this endpoint to move a registered domain onto different contact information. - **Method**: `PUT` - **Path**: `/api/domains/v1/whois/change` #### domains_setWHOISProfileAsDefaultV1 Set WHOIS contact profile as default. The default profile is pre-selected for the TLD it belongs to when registering new domains. Use this endpoint to avoid picking contact information for every registration. - **Method**: `PUT` - **Path**: `/api/domains/v1/whois/default/{whoisId}` #### domains_unsetDefaultWHOISProfileV1 Unset WHOIS contact profile as default. The profile itself is kept, it is only no longer pre-selected for its TLD. Use this endpoint to stop reusing contact information for new registrations. - **Method**: `DELETE` - **Path**: `/api/domains/v1/whois/default/{whoisId}` #### domains_getWHOISProfileV1 Retrieve a WHOIS contact profile. Use this endpoint to view domain registration contact information. - **Method**: `GET` - **Path**: `/api/domains/v1/whois/{whoisId}` #### domains_deleteWHOISProfileV1 Delete WHOIS contact profile. Use this endpoint to remove unused contact profiles from account. - **Method**: `DELETE` - **Path**: `/api/domains/v1/whois/{whoisId}` #### domains_getWHOISProfileListV1 Retrieve WHOIS contact profiles. Use this endpoint to view available contact profiles for domain registration. - **Method**: `GET` - **Path**: `/api/domains/v1/whois` #### domains_createWHOISProfileV1 Create WHOIS contact profile. Use this endpoint to add new contact information for domain registration. - **Method**: `POST` - **Path**: `/api/domains/v1/whois` #### domains_getWHOISProfileUsageV1 Retrieve domain list where provided WHOIS contact profile is used. Use this endpoint to view which domains use specific contact profiles. - **Method**: `GET` - **Path**: `/api/domains/v1/whois/{whoisId}/usage` ### `hostinger-ecommerce-mcp` #### ecommerce_listDiscountsV1 List a store's discounts. Filter by free text over code and name, or by disabled state. Amounts for fixed discounts are integers in the smallest currency unit; percentage discounts carry a whole-number value between 1 and 100. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores/{store_id}/discounts` #### ecommerce_createADiscountV1 Create a discount for a store. Fixed discounts take an amount in the smallest currency unit (e.g. $10 is 1000); percentage discounts take a whole-number value between 1 and 100. Free-shipping discounts ignore value. Returns the created discount. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/discounts` #### ecommerce_getCustomStorefrontSetupInstructionsV1 Retrieve step-by-step setup instructions, formatted as Markdown, for connecting a custom sales channel to your store and keeping your catalog, orders, shipping and payments in sync through the Ecommerce API. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/miscellaneous/custom-storefront-instructions` #### ecommerce_cancelAnOrderV1 Cancel the order and optionally email the customer. Returns the updated order summary. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders/{order_id}/cancel` #### ecommerce_fulfilAnOrderV1 Create a fulfilment for the order and attach tracking in one call. Omit items to fulfil every remaining unfulfilled item. Returns the updated order summary. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders/{order_id}/fulfill` #### ecommerce_listStoreOrdersV1 List a store's orders newest first as summaries. Filter by status, payment or fulfilment status, customer email, order number or a free-text query. Amounts are in the smallest currency unit. Retrieve a single order for its line items, addresses and fulfilments. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders` #### ecommerce_retrieveAnOrderV1 Retrieve one order in full: line items (each with the id the fulfil endpoint needs), addresses, the totals breakdown and fulfilments with tracking. Amounts are in the smallest currency unit. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders/{order_id}` #### ecommerce_enableManualPaymentMethodV1 Enable a manual payment method so the store can accept orders without an online payment provider. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/payment-methods/manual` #### ecommerce_createAPaymentProviderConnectLinkV1 Create an onboarding link for connecting a payment gateway to the store. Returns the gateway onboarding URL for the merchant to open and a deep-link into the store admin. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/payment-providers/{provider_id}/connect-link` #### ecommerce_listStorePaymentProvidersV1 List a store's payment providers, split into providers already connected to the store and gateways available to install. Never exposes gateway credentials, secrets, or configuration. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores/{store_id}/payment-providers` #### ecommerce_createAProductImageUploadURLV1 Returns a signed URL to upload a product image to (multipart/form-data POST). Then call the attach-image endpoint with the returned object_name to scan and attach it to the product. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/images/upload-url` #### ecommerce_deleteAProductV1 Delete a product and its variants from the store. A subscription product with active subscribers is archived instead of deleted so its data stays available. - **Method**: `DELETE` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}` #### ecommerce_updateAProductV1 Update a product's name, description or status. Set status to published to make it buyable, draft to hide it, or archived to retire it. Variants, prices and inventory are managed through the variant endpoints, not here. Returns the updated product summary. - **Method**: `PATCH` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}` #### ecommerce_createDigitalProductV1 Create a published digital product with a single variant and an optional external download link. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/digital` #### ecommerce_listProductsV1 List a store's products newest first as lean summaries (name, status, thumbnail, variant count and price range). Prices are integers in the smallest currency unit and live on variants. Filter by status, free text or a set of product ids. Use include=variants to embed each product's variants with prices and inventory, and include=media to embed its media. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products` #### ecommerce_createPhysicalProductV1 Create a published physical product with a single variant priced in the store currency. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/physical` #### ecommerce_uploadAndAttachAProductImageV1 Fetch a raster image (JPEG, PNG, GIF or WebP, max 15MB) from a URL and attach it to a product in a single call. The image is virus-scanned and validated by content, then stored on the CDN. Set is_thumbnail to make it the product's primary image. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/images` #### ecommerce_listSalesChannelsV1 List a store's active sales channels with their full metadata. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores/{store_id}/sales-channels` #### ecommerce_createASalesChannelV1 Create a sales channel for a store. A "custom" channel is headless: build your own frontend and keep your catalog, orders, shipping and payments in sync through the Ecommerce API. A "quick-link" channel is a hosted one-page store whose handle is auto-generated. - **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. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/shipping` #### ecommerce_deleteStoreV1 Soft-delete a store owned by your account. The underlying store data is preserved; only the store is marked as deleted. - **Method**: `DELETE` - **Path**: `/api/ecommerce/v1/stores/{store_id}` #### ecommerce_getStoresV1 Retrieve the stores associated with your account. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores` #### ecommerce_createStoreV1 Create a new store for your account. 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` #### ecommerce_updateProductVariantsInBatchV1 Update up to 100 existing variants in place by id — title, inventory, stock tracking and prices. Variants omitted from the request are left untouched. Prices replace the variant's existing prices in full. Returns the updated variants. - **Method**: `PATCH` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants/batch` #### ecommerce_deleteAProductVariantV1 Delete a single variant from the product. - **Method**: `DELETE` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants/{variant_id}` #### ecommerce_listProductVariantsV1 List a product's variants, ordered by rank, with their options, prices and inventory. Prices are integers in the smallest currency unit and live on variants. - **Method**: `GET` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants` #### ecommerce_createAProductVariantV1 Add a variant to a product along one or more option dimensions (e.g. Size, Color). Options missing from the product are created automatically; provide a value for every option the product already has. Prices are integers in the smallest currency unit and default to the store currency. Returns the created variant. - **Method**: `POST` - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants` ### `hostinger-horizons-mcp` #### horizons_createWebsiteV1 Create new Hostinger Horizons website from the given message.\n Use this tool when user asks you to create a website, landing page, blog or any other type of application.\n This tool initiates the website creation process and returns a website URL and ID. The generation happens asynchronously.\n After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing that Hostinger Horizons is now creating their website and it will be ready in a few minutes and you should provide the website URL to the user immediately Do not write code.\n\nTo edit afterwards, users must go to Hostinger Horizons interface in the provided website URL. If the tool call fails with an error, you should provide a clear explanation of the error and do not generate code yourself in the chat. \n TECHNOLOGY STACK CONSTRAINTS (STRICTLY ENFORCED):\n The environment is limited to the following technologies. You MUST NOT use, suggest, or implement any technology outside this list:\n \n - Language: JavaScript ONLY. - Languages like TypeScript, Rust, Python, Java, PHP, etc., are STRICTLY PROHIBITED.\n - Framework: React.\n - Navigation: React Router.\n - Styling: TailwindCSS.\n - Components: shadcn/ui (built with @radix-ui primitives).\n - Icons: Lucide React.\n - Animations: Framer Motion.\n \n BACKEND & DATA STORAGE:\n - Horizons integrated backend is the EXCLUSIVE solution for persistent data storage, authentication, and database needs.\n - Local databases (SQLite, MySQL, etc.) are STRICTLY PROHIBITED.\n - Third-party services (Firebase, AWS Amplify) are allowed ONLY if explicitly requested by the user.\n \n MAPS:\n - OpenStreetMap is the default provider.\n - Alternative providers (Google Maps, Mapbox) are allowed ONLY if explicitly requested by the user.\n - **Method**: `POST` - **Path**: `/api/horizons/v1/websites` #### horizons_getWebsiteV1 Get a link for the user to edit their website in Hostinger Horizons interface.\n Use this tool when user wants to modify, edit or add new features to an existing website.\n Websites can only be edited in Hostinger Horizons interface in the provided website URL. - **Method**: `GET` - **Path**: `/api/horizons/v1/websites/{websiteId}` ### `hostinger-hosting-mcp` #### hosting_importWordpressWebsite Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end. The username will be automatically resolved from the domain. - **Method**: `custom` - **Path**: `custom` #### hosting_deployWordpressPlugin Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end. - **Method**: `custom` - **Path**: `custom` #### hosting_deployWordpressTheme Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end. - **Method**: `custom` - **Path**: `custom` #### hosting_deployJsApplication Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress. - **Method**: `custom` - **Path**: `custom` #### hosting_deployStaticWebsite Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deployJsApplication instead. The tool uploads the archive to the website's file browser over TUS and triggers deployment; the archive is extracted and deployed directly without any build steps. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. The username will be automatically resolved from the domain. - **Method**: `custom` - **Path**: `custom` #### hosting_listJsDeployments List javascript application deployments for checking their status. Use this tool when customer asks for the status of the deployment. This tool retrieves a paginated list of Node.js application deployments for a domain with optional filtering by deployment states. - **Method**: `custom` - **Path**: `custom` #### hosting_showJsDeploymentLogs Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure. - **Method**: `custom` - **Path**: `custom` #### hosting_clearWebsiteCacheV1 Permanently clears all server-side cache for the website at once. Use it when content was updated and needs to be visible immediately, or after making major changes. Also purges the Hostinger CDN cache when CDN is enabled on the website. For a WordPress installation living in a subdirectory, pass the directory query parameter to clear its cache. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/clear` #### hosting_toggleCachelessModeV1 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/toggle` #### hosting_toggleWebsiteCacheV1 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 in the requested state. - **Method**: `PATCH` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/toggle` #### hosting_listAccountCronJobsV1 Returns the list of cron jobs configured for the specified account, including their schedule and command. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/cron-jobs` #### hosting_createAccountCronJobV1 Creates a cron job for the specified account from a schedule expression and a command. Returns the created cron job, including its uid, which is required to delete the cron job or fetch its output. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/cron-jobs` #### hosting_deleteAccountCronJobV1 Permanently deletes the cron job identified by its uid. The uid is returned by the list cron jobs endpoint. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/accounts/{username}/cron-jobs/{uid}` #### hosting_getCronJobOutputV1 Returns the output captured from the last execution of the cron job identified by its uid. The uid is returned by the list cron jobs endpoint. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/cron-jobs/{uid}/output` #### hosting_changeDatabasePasswordV1 Changes the password for the specified database user. The database name must be the full name returned by the list databases endpoint. The password must also be updated in any website configuration that uses this database. - **Method**: `PATCH` - **Path**: `/api/hosting/v1/accounts/{username}/databases/{name}/change-password` #### hosting_listAccountDatabasesV1 Returns a paginated list of databases for the specified account. Use the domain and is_assigned filters to find databases assigned to a specific domain. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/databases` #### hosting_createAccountDatabaseV1 Creates a database with a database user and password for the specified account. The database name and user are automatically prefixed with the account username when needed. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/databases` #### hosting_deleteAccountDatabaseV1 Permanently deletes a database and its remote connections. The database name must be the full name returned by the list databases endpoint. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/accounts/{username}/databases/{name}` #### hosting_createDatabaseRemoteConnectionV1 Allows a remote host to connect to the specified database. Provide an IPv4/IPv6 address, or "%" to allow any host. The database name must be the full name returned by the list databases endpoint. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/databases/{name}/remote-connections` #### hosting_deleteDatabaseRemoteConnectionV1 Permanently removes a remote-access rule, revoking the given host's remote access to the database. Identify the rule with the required ip query parameter (the IPv4/IPv6 address, or "%", exactly as returned by the list remote connections endpoint). The database name must be the full name returned by the list databases endpoint. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/accounts/{username}/databases/{name}/remote-connections` #### hosting_listDatabaseRemoteConnectionsV1 Returns the remote-access rules for the specified account: the remote hosts (IPv4/IPv6 addresses, or "%" for any host) allowed to connect to the account databases. Use the domain filter to only return rules for databases assigned to a specific domain. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/databases/remote-connections` #### hosting_repairDatabaseV1 Repairs corrupted database tables asynchronously. Use when database errors, crashes, or corruption are reported. The database name must be the full name returned by the list databases endpoint. - **Method**: `PATCH` - **Path**: `/api/hosting/v1/accounts/{username}/databases/{name}/repair` #### hosting_getPhpMyAdminLinkV1 Returns a direct sign-on link to phpMyAdmin for the specified database. Use this when a visual database interface is needed for SQL queries, imports, exports, or table management. The database name must be the full name returned by the list databases endpoint. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/databases/{name}/phpmyadmin-link` #### hosting_listAvailableDatacentersV1 Retrieve a list of datacenters available for setting up hosting plans based on available datacenter capacity and hosting plan of your order. The first item in the list is the best match for your specific order requirements. - **Method**: `GET` - **Path**: `/api/hosting/v1/datacenters` #### hosting_generateAFreeSubdomainV1 Generate a unique free subdomain that can be used for hosting services without purchasing custom domains. Free subdomains allow you to start using hosting services immediately and you can always connect a custom domain to your site later. - **Method**: `POST` - **Path**: `/api/hosting/v1/domains/free-subdomains` #### hosting_listWebsiteParkedDomainsV1 Retrieve all parked or alias domains created under the selected website. Use this endpoint to inspect parked domain configuration for a specific website, including the parent domain and root directory assigned to each parked domain. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains` #### hosting_createWebsiteParkedDomainV1 Create a parked or alias domain for the selected website. Provide a domain name or IP address to park on the website so it serves the same content as the parent domain. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains` #### hosting_deleteWebsiteParkedDomainV1 Delete an existing parked or alias domain from the selected website. Use this endpoint to remove parked domains that are no longer needed. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains/{parkedDomain}` #### hosting_listWebsiteSubdomainsV1 Retrieve all subdomains created under the selected website. Use this endpoint to inspect subdomain configuration for a specific website, including the parent domain and root directory assigned to each subdomain. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/subdomains` #### hosting_createWebsiteSubdomainV1 Create a new subdomain for the selected website. Provide a subdomain prefix and, optionally, a custom directory or the website public directory to use as the subdomain root. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/subdomains` #### hosting_deleteWebsiteSubdomainV1 Delete an existing subdomain from the selected website. Use this endpoint to remove subdomains that are no longer needed. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/subdomains/{subdomain}` #### hosting_verifyDomainOwnershipV1 Verify ownership of a single domain and return the verification status. Use this endpoint to check if a domain is accessible for you before using it for new websites. If the domain is accessible, the response will have `is_accessible: true`. If not, add the given TXT record to your domain's DNS records and try verifying again. Keep in mind that it may take up to 10 minutes for new TXT DNS records to propagate. Skip this verification when using Hostinger's free subdomains (*.hostingersite.com). - **Method**: `POST` - **Path**: `/api/hosting/v1/domains/verify-ownership` #### hosting_generateUploadURLV1 Generate a file browser upload URL with authentication credentials for uploading files directly to a website's file storage. Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website's `public_html` directory via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below. 1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or `PATCH` requests with an `upload-offset` header tracking progress) until complete. `relative_file_path` is the destination path inside `public_html`, e.g. `app.zip`. Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z "$FILE") # stat -c%s on Linux curl -i -X POST "{url}/${FILE}?override=true" \ -H "X-Auth: {auth_key}" \ -H "X-Auth-Rest: {rest_auth_key}" \ -H "Tus-Resumable: 1.0.0" \ -H "Upload-Length: ${SIZE}" \ -H "Upload-Offset: 0" # -> 201 Created curl -i -X PATCH "{url}/${FILE}?override=true" \ -H "X-Auth: {auth_key}" \ -H "X-Auth-Rest: {rest_auth_key}" \ -H "Tus-Resumable: 1.0.0" \ -H "Content-Type: application/offset+octet-stream" \ -H "Upload-Offset: 0" \ --data-binary "@${FILE}" # -> 204 No Content, Upload-Offset response header equals SIZE when done ``` - **Method**: `POST` - **Path**: `/api/hosting/v1/files/upload-urls` #### hosting_listWebsiteFilesAndDirectoriesV1 List files and directories under a website's document root. Use `directory` to browse a subdirectory relative to the document root. Symlinked entries are listed but never traversed into or resolved. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/domains/{domain}/files` #### hosting_getWebsiteFileContentV1 Get a single file's content, relative to a website's document root. Read-only; refuses symlinks, oversized files, non-text file types, and files identified as containing secrets (e.g. credential files) — none of these are returned by this endpoint. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/domains/{domain}/files/content` #### hosting_listNodeJSBuildsV1 Retrieve a paginated list of Node.js build processes for a specific website. Each build represents a single run of the Node.js build pipeline. Use the `states` query parameter to filter results by build state (pending, running, completed, failed). Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds` #### hosting_startNode_jsBuildV1 Start a Node.js build process using files already present on the website's file storage. WARNING: on success this overwrites the website's existing contents and cannot be undone — verify this is intended before calling this endpoint. The `source_type` must be `archive` and `source_options.archive_path` must point to an existing archive file on the server (relative to the website document root). Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first. To auto-detect build settings from an archive before starting, first call the `Get Node.js Build Settings from Archive` endpoint. The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds` #### hosting_getNode_jsBuildSettingsFromArchiveV1 Auto-detect Node.js build settings from a package.json inside an archive already on the server. Use this before calling `Start Node.js Build` to preview what settings will be used, or to let the user review and override values (framework, node version, root directory, output directory, build script) before committing to a build. The archive must already be present on the website's file storage. Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/from-archive` #### hosting_listNode_jsEnvironmentVariablesV1 Lists the Node.js environment variables currently set for the website. Values are always masked as `********` and cannot be read back through this API. Use this endpoint to see which keys are configured or to verify a change, not to read values. To change variables, use the `Replace Node.js environment variables` endpoint. It replaces the whole set, so never copy the masked values from this response into that request; send the full desired set with real values taken from the project `.env` file or the user prompt instead. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env` #### hosting_replaceNode_jsEnvironmentVariablesV1 Replaces the website's Node.js environment variables with the ones provided. This is a full replace: any variable not in the request is deleted, and sending an empty `env_vars` array deletes every variable. Saving writes the values and restarts the running Node.js process. A restart is enough for apps that read environment variables at process start, such as Express or NestJS. It is not enough for frameworks that bake variables into the build. Next.js standalone is one of those: build-time values (including `NEXT_PUBLIC_*`) need a fresh build. After this call, use the `Start Node.js build` endpoint so those apps pick up the new values. The `List Node.js environment variables` endpoint returns masked values (`********`), so never copy values from it into this request. Always send the full desired set with real values taken from the project `.env` file or the user prompt. - **Method**: `PUT` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/env` #### hosting_getNodeJSBuildLogsV1 Retrieve logs from a specific Node.js build process. To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. 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 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 application. Only applicable to server-side applications (Express, Next.js, NestJS, etc.). Static front-end apps (React, Vue, Vite) have no persistent server process, so restarting them has no effect. Returns success even when the website has no server process to restart. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/server/restart` #### hosting_listNode_jsVulnerabilitiesV1 Lists known npm package vulnerabilities detected on a Node.js website, enriched with advisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from the most severe to the least severe, then by publish date (newest first). Use the `severities` query parameter to filter. Vulnerabilities with `is_patchable` set to `true` can be auto-fixed via the `Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with updated package versions. Auto-fix is only available for websites deployed from a connected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to `true` are already included in an open patch pull request; while any patch pull request is open, new patch requests for this website are rejected until it is merged or closed. Data comes from periodic dependency scans, so it may lag behind the latest deployment. An empty list means the most recent scan found no vulnerabilities; it does not guarantee the current deployment is vulnerability-free. Available on Business and Cloud Hosting plans. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities` #### hosting_patchNode_jsVulnerabilitiesV1 Patches the selected Node.js vulnerabilities by updating the affected package versions in `package.json` and opening a GitHub pull request in the connected repository. The customer reviews and merges the pull request; merging triggers the automatic deployment. Auto-fix is only available for websites deployed from a connected GitHub repository. Websites deployed from an archive have no auto-fix path and return a 404. The Hostinger GitHub App needs write access to the repository; without it the request fails with a 403 explaining the missing permission. Only vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable IDs in the selection are skipped; the pull request covers the patchable subset, listed in `patched_vulnerability_ids`. Selections without any patchable vulnerability are rejected with a 422. Only one patch pull request can be open at a time per website; close or merge it before patching again. Available on Business and Cloud Hosting plans. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities/patch` #### hosting_listOrdersV1 Retrieve a paginated list of orders accessible to the authenticated client. This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you. Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results. - **Method**: `GET` - **Path**: `/api/hosting/v1/orders` #### hosting_resetPHPExtensionsV1 Resets all PHP extensions of the website to their default state. Use it to recover from extension conflicts or restore the original configuration. - **Method**: `PATCH` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/php/extensions/reset` #### hosting_getPHPDetailsV1 Returns the full PHP configuration for the website: current version, available versions (supported and unsupported), enabled/disabled extensions, options with their current value, default, type and the plan limit (`max`), and conflicting extension groups. Use it to check the current PHP setup before updating the version, extensions or options. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/php/details` #### hosting_getPHPInfoV1 Returns the full phpinfo page (HTML) for the website. Use it to debug PHP issues or inspect the complete PHP environment of the website. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/php/php-info` #### hosting_updatePHPExtensionsV1 Enables or disables PHP extensions (modules) for the website. Use the Get PHP details endpoint to check the current extension states before changing them. - **Method**: `PATCH` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/php/extensions` #### hosting_updatePHPOptionsV1 Updates PHP options for the website (e.g. `memory_limit`, `max_execution_time`, `upload_max_filesize`). Only provide the options you want to change, inside the `options` object. Values above the account plan limit are silently capped to that limit, so the request can succeed with a smaller applied value. Call the Get PHP details endpoint afterwards to read the applied value. - **Method**: `PATCH` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/php/options` #### hosting_updatePHPVersionV1 Changes the PHP version of the website. Use the Get PHP details endpoint to see the versions available for the website. - **Method**: `PATCH` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/php/version` #### hosting_listWebsiteRedirectsV1 Returns a paginated list of redirects configured for the selected website. - **Method**: `GET` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/redirects` #### hosting_createWebsiteRedirectV1 Creates a redirect from a URL on the selected website to another URL or IP address. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/redirects` #### hosting_deleteWebsiteRedirectV1 Permanently deletes the redirect identified by its source URL. Pass the `from` value exactly as returned by the list redirects endpoint. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/redirects` #### hosting_listWebsitesV1 Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client. This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you. Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms. Use `website_types` to list only websites of a given detected type, e.g. only WordPress websites (`website_types=wordpress`) or only Node.js websites (`website_types=nodejs`). Combine with the other available query parameters to filter by username, order ID, enabled status, or domain name for more targeted results. - **Method**: `GET` - **Path**: `/api/hosting/v1/websites` #### hosting_createWebsiteV1 Create a new website for the authenticated client. Provide the domain name and associated order ID to create a new website. The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter. Subsequent websites will be hosted on the same datacenter automatically. Website creation takes up to a few minutes to complete. Check the websites list endpoint to see when your new website becomes available. - **Method**: `POST` - **Path**: `/api/hosting/v1/websites` #### hosting_deployStaticSiteArchiveV1 Deploy a static application from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — verify this is intended before calling this endpoint. This endpoint allows you to deploy a static application from an archive file that has been uploaded to the website's directory. This only works for static sites (pre-built HTML/CSS/JS with no build step). For Node.js applications, use `Create NodeJS build from archive` instead, or `Start Node.js build` if the archive is already uploaded. For WordPress sites, use `Import WordPress website`. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/deploy` #### hosting_deleteWebsiteV1 This endpoint permanently removes a website and all of its data. This action cannot be undone. Before calling it, make sure the user understands the consequences and explicitly confirms that they want to proceed. All website files, databases and related configuration will be removed. The hosting plan itself is kept, so a new website can be created on it afterwards. Supported websites: main and addon domain websites on web hosting plans, and Website Builder websites. Parked domains and subdomains cannot be deleted with this endpoint. The domain must be the exact website domain, not a preview domain or an alias. Returns 404 when the domain does not exist or does not belong to the authenticated client. Website removal is processed asynchronously and can take a few minutes to complete. The response returns before the removal finishes. - **Method**: `DELETE` - **Path**: `/api/hosting/v1/websites/{domain}` ### `hostinger-mail-mcp` #### mail_createAliasV1 Create an alias for the given mailbox. The alias address is formed from the given local part and the domain of the mailbox. Messages sent to the alias are delivered to the mailbox. - **Method**: `POST` - **Path**: `/api/mail/v1/mailboxes/{mailboxId}/aliases` #### mail_deleteAliasV1 Delete an alias. Messages sent to the alias address are no longer delivered to the mailbox. - **Method**: `DELETE` - **Path**: `/api/mail/v1/aliases/{aliasId}` #### mail_listAliasesV1 Retrieve a paginated list of aliases across all mailboxes of a mail order. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/aliases` #### mail_createAPITokenV1 Create an API token for the given mail order. The token grants access to the [Hostinger Email API](https://api.mail.hostinger.com/), where you can provision and manage the mailboxes it is scoped to. The plaintext token is returned only in this response, never again. A maximum of 10 tokens can exist per order. Use `scope.has_all_mailboxes` to cover all current and future mailboxes, or list specific mailboxes in `scope.mailbox_ids`. - **Method**: `POST` - **Path**: `/api/mail/v1/orders/{orderId}/api-tokens` #### mail_revokeAPITokenV1 Revoke an API token. The token immediately loses access to the [Hostinger Email API](https://api.mail.hostinger.com/). This action cannot be undone. - **Method**: `DELETE` - **Path**: `/api/mail/v1/api-tokens/{tokenId}` #### mail_listAPITokensV1 Retrieve a paginated list of [Hostinger Email API](https://api.mail.hostinger.com/) tokens across all your mail orders, optionally filtered by order. Plaintext tokens are never included; they are returned only when a token is created. - **Method**: `GET` - **Path**: `/api/mail/v1/api-tokens` #### mail_createAutoreplyV1 Create an automatic reply for the given mailbox. A mailbox can have only one autoreply. Omit `starts_at` to activate the autoreply immediately and omit `ends_at` to keep it active indefinitely. - **Method**: `POST` - **Path**: `/api/mail/v1/mailboxes/{mailboxId}/autoreplies` #### mail_updateAutoreplyV1 Replace the autoreply with the given content and schedule. Omitted optional fields are cleared: omit `starts_at` to activate the autoreply immediately and omit `ends_at` to keep it active indefinitely. - **Method**: `PUT` - **Path**: `/api/mail/v1/autoreplies/{autoreplyId}` #### mail_deleteAutoreplyV1 Delete the autoreply of a mailbox. The mailbox stops sending automatic replies immediately. - **Method**: `DELETE` - **Path**: `/api/mail/v1/autoreplies/{autoreplyId}` #### mail_listAutorepliesV1 Retrieve a paginated list of autoreplies across all mailboxes of a mail order. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/autoreplies` #### mail_createCatchAllV1 Create a catch-all that routes all messages sent to unknown addresses of the domain to the given mailbox. The mailbox address receives a confirmation email and the catch-all becomes active only after it is confirmed. A domain can have only one catch-all. - **Method**: `POST` - **Path**: `/api/mail/v1/mailboxes/{mailboxId}/catchalls` #### mail_deleteCatchAllV1 Delete a catch-all. Messages sent to unknown addresses of the domain are no longer routed to the mailbox. - **Method**: `DELETE` - **Path**: `/api/mail/v1/catchalls/{catchallId}` #### mail_listCatchAllsV1 Retrieve a paginated list of catch-alls across all mailboxes of a mail order. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/catchalls` #### mail_resendCatchAllConfirmationV1 Resend the confirmation email to the mailbox address of an unconfirmed catch-all. - **Method**: `POST` - **Path**: `/api/mail/v1/catchalls/{catchallId}/confirmation/resend` #### mail_createForwarderV1 Create a forwarder from the given mailbox to the destination address. The destination receives a confirmation email and forwarding becomes active only after it is confirmed. - **Method**: `POST` - **Path**: `/api/mail/v1/mailboxes/{mailboxId}/forwarders` #### mail_deleteForwarderV1 Delete a forwarder. The mailbox stops forwarding messages to the destination address immediately. - **Method**: `DELETE` - **Path**: `/api/mail/v1/forwarders/{forwarderId}` #### mail_listForwardersV1 Retrieve a paginated list of forwarders across all mailboxes of a mail order. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/forwarders` #### mail_resendForwarderConfirmationV1 Resend the confirmation email to the destination address of an unconfirmed forwarder. - **Method**: `POST` - **Path**: `/api/mail/v1/forwarders/{forwarderId}/confirmation/resend` #### mail_updateForwarderKeepCopySettingV1 Enable or disable keeping a copy of forwarded messages in the mailbox. - **Method**: `PATCH` - **Path**: `/api/mail/v1/forwarders/{forwarderId}/keep-copy` #### mail_listAccessLogsV1 Retrieve paginated access logs for the domain attached to the given mail order. Supports filtering by account, date range, protocol, status, and deletion flag. Results are sorted by timestamp descending. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/logs/access` #### mail_listActionLogsV1 Retrieve paginated account action logs (administrative and user actions) for the given mail order. Supports filtering by account, date range, and status. Results are sorted by timestamp descending. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/logs/action` #### mail_listInboundLogsV1 Retrieve paginated inbound (received mail) delivery logs for the domain attached to the given mail order. Supports filtering by account, date range, status, sender, and recipient. Results are sorted by timestamp descending. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/logs/inbound` #### mail_listMailboxActionLogsV1 Retrieve paginated mailbox action logs (message and mailbox events) for a mailbox in the given mail order. The mailbox email must belong to the order's domain. Supports date range and event type filters. Results are sorted by timestamp descending. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/logs/mailbox-actions` #### mail_listOutboundLogsV1 Retrieve paginated outbound (sent mail) delivery logs for the domain attached to the given mail order. Supports filtering by account, date range, status, sender, and recipient. Results are sorted by timestamp descending. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/logs/outbound` #### mail_listMailboxesV1 Retrieve a paginated list of mailboxes belonging to a mail order. Use this endpoint to monitor mailboxes of your mail service, including their status, enabled protocols, attached resource counts, and periodically synced usage numbers (usage may lag behind live values). - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/mailboxes` #### mail_createMailboxV1 Create a mailbox under the given mail order. The full email address is composed from the given local part and the domain of the order. - **Method**: `POST` - **Path**: `/api/mail/v1/orders/{orderId}/mailboxes` #### mail_deleteMailboxV1 Delete a mailbox. The mailbox is soft-deleted and stays restorable for a limited period before it is permanently removed. - **Method**: `DELETE` - **Path**: `/api/mail/v1/mailboxes/{mailboxId}` #### mail_changeMailboxPasswordV1 Change the password of a mailbox. - **Method**: `PATCH` - **Path**: `/api/mail/v1/mailboxes/{mailboxId}/password` #### mail_listOrdersV1 Retrieve a paginated list of mail orders associated with your account. Use this endpoint to monitor your mail services, including their status, plan, attached domain, and expiration details. - **Method**: `GET` - **Path**: `/api/mail/v1/orders` #### mail_getOrderPlanV1 Retrieve the plan the given mail order was purchased with, including domain-level and mailbox-level quotas, limits, and protocol availability. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/plan` #### mail_createWebhookV1 Create a webhook for the given mailbox. The generated secret is returned only in this response and is sent as a bearer token with every delivery. - **Method**: `POST` - **Path**: `/api/mail/v1/mailboxes/{mailboxId}/webhooks` #### mail_listWebhookDeliveryLogsV1 Retrieve a paginated list of webhook delivery logs for the given mail order, including delivery outcome, duration, and retry counts. Supports filtering by mailbox. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/webhooks/delivery-logs` #### mail_getWebhookV1 Retrieve the details of a single webhook. The webhook secret is never included; it is returned only when a webhook is created or its secret is regenerated. - **Method**: `GET` - **Path**: `/api/mail/v1/webhooks/{webhookId}` #### mail_deleteWebhookV1 Permanently delete a webhook. This action cannot be undone. After deletion the URL no longer receives event notifications. - **Method**: `DELETE` - **Path**: `/api/mail/v1/webhooks/{webhookId}` #### mail_updateWebhookV1 Partially update a webhook. Only the fields included in the request body are changed; omitted fields retain their current values. Pass `"description": null` to clear the description. - **Method**: `PATCH` - **Path**: `/api/mail/v1/webhooks/{webhookId}` #### mail_listWebhooksV1 Retrieve a paginated list of webhooks belonging to the given mail order. Supports filtering by mailbox and status. The webhook secret is never included; it is returned only when a webhook is created or its secret is regenerated. - **Method**: `GET` - **Path**: `/api/mail/v1/orders/{orderId}/webhooks` #### mail_regenerateWebhookSecretV1 Regenerate the secret of a webhook. The previous secret is immediately invalidated. The new secret is returned only in this response and is sent as a bearer token with every delivery. - **Method**: `POST` - **Path**: `/api/mail/v1/webhooks/{webhookId}/regenerate-secret` #### mail_testWebhookV1 Send a test delivery to the webhook URL and return the result. Test requests are rate limited upstream. - **Method**: `POST` - **Path**: `/api/mail/v1/webhooks/{webhookId}/test` ### `hostinger-reach-mcp` #### reach_getAutomationDetailsV1 Get a single automation with the counts of contacts that entered it, are moving through it, finished it or failed on the way. This describes the automation itself. To see the workflow it runs, use the steps endpoint. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/automations/{automationUuid}` #### reach_listAutomationsV1 Get a paginated list of the automations in a profile. Every automation comes with the counts of contacts that entered it, are moving through it, finished it or failed on the way. Those counts describe the contact journey and are not email engagement metrics - for opens, clicks and unsubscribes use the campaign statistics endpoint instead. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/automations` #### reach_listAutomationStepsV1 Get the workflow of an automation as a flat list of steps. The steps form a tree rather than a straight line: follow `parent_uuid` to reconstruct the branches, and use `step_order` to order the steps that share a parent. An automation with no steps yet returns an empty list. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/automations/{automationUuid}/steps` #### reach_getCampaignDetailsV1 Get a single campaign with its sender, subject, template reference, targeting and delivery progress. This describes how the campaign was set up and how far it has got. For opens, clicks and unsubscribes use the campaign statistics endpoint. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/campaigns/{campaignUuid}` #### reach_listCampaignsV1 Get a paginated list of the campaigns in a profile. Each campaign carries its headline engagement rates. Filter by status to find drafts, scheduled, sending or sent campaigns, keeping in mind that a fully sent campaign has the status `publish`. By default only regular campaigns are returned - pass `type` to get the emails sent by automations or the double opt-in confirmations instead. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/campaigns` #### reach_getCampaignPerformanceV1 Get the performance of a campaign: delivery, opens, clicks and unsubscribes, with the matching rates. Every count is unique contacts rather than raw events, so a contact who opens the same email five times is counted once. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/campaigns/{campaignUuid}/statistics` #### reach_deleteAContactV1 Delete a contact with the specified UUID. This endpoint permanently removes a contact from the email marketing system. **Deprecated.** This endpoint cannot target a profile, so it always falls back to the client's default profile and cannot delete contacts of any other profile. Use `DELETE /api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}` instead. - **Method**: `DELETE` - **Path**: `/api/reach/v1/contacts/{uuid}` #### reach_deleteAContactFieldV1 Delete a custom contact field. Every value contacts hold for the field is deleted with it, and for the choice types so are its options. The contacts themselves are not affected. - **Method**: `DELETE` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields/{fieldUuid}` #### reach_updateAContactFieldV1 Rename a custom contact field and, for the choice types, replace its option set. Options carrying a uuid are kept and relabelled, options without one are created, and any existing option left out of the list is deleted along with the values contacts hold for it. The field type and slug cannot be changed. - **Method**: `PATCH` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields/{fieldUuid}` #### reach_listContactFieldsV1 Get the custom contact fields defined in a profile. Custom fields let you store your own attributes on contacts. The returned uuids are what you pass to the contact update endpoint to set values, and choice fields also list the options available to pick from. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields` #### reach_createAContactFieldV1 Define a new custom contact field in a profile. The `slug` is derived from the label and, like the field type, cannot be changed later. Use the returned uuid to set values on contacts. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/fields` #### reach_listContactGroupsV1 Get a list of all contact groups. This endpoint returns a list of contact groups that can be used to organize contacts. - **Method**: `GET` - **Path**: `/api/reach/v1/contacts/groups` #### reach_listContactsV1 Get a list of contacts, optionally filtered by group and subscription status. This endpoint returns a paginated list of contacts with their basic information. You can filter contacts by group UUID and subscription status. **Deprecated.** This endpoint cannot target a profile, so it always falls back to the client's default profile and cannot list contacts of any other profile. Use `GET /api/reach/v1/profiles/{profileUuid}/contacts` instead, which also replaces the group filter with a tag filter. - **Method**: `GET` - **Path**: `/api/reach/v1/contacts` #### reach_createANewContactV1 Create a new contact in the email marketing system. This endpoint allows you to create a new contact with basic information like name, email, and surname. If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent. - **Method**: `POST` - **Path**: `/api/reach/v1/contacts` #### reach_getContactDetailsV1 Get the full details of a single contact. Alongside the contact's own attributes this returns the tags assigned to it and the values it holds for the profile's custom contact fields. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}` #### reach_deleteAProfileContactV1 Permanently delete a contact from a profile. The contact is removed together with its custom field values and tag assignments. - **Method**: `DELETE` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}` #### reach_updateAContactV1 Update a contact's attributes and custom field values. Only the properties present in the request body are changed, so a partial body is enough to change a single attribute. Sending a property as `null` clears it. The response carries the contact's core attributes. Read back its tags, custom field values, source and note with `GET /api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}`. - **Method**: `PATCH` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/{contactUuid}` #### reach_createContactsInBulkV1 Create many contacts in a profile in a single call. The contacts are imported in the background, so a success response means the import was accepted rather than finished. Contacts whose email already exists in the profile are left as they are. If double opt-in is enabled, new contacts start off pending and are sent a confirmation email. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts/bulk` #### reach_listProfileContactsV1 Get a paginated list of contacts belonging to a profile. Contacts can be filtered by subscription status, by tag, and by an email search term. The `meta.total` field of the response is the number of contacts matching the filters, so calling this endpoint without filters gives the profile's total contact count. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts` #### reach_createNewContactsV1 Create a new contact in the email marketing system. This endpoint allows you to create a new contact with basic information like name, email, and surname. If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/contacts` #### reach_listSegmentsV1 Get a list of all contact segments. This endpoint returns a list of contact segments that can be used to organize contacts. **Deprecated.** This endpoint cannot target a profile, so it always falls back to the client's default profile and cannot list the segments of any other profile. Use `GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments` instead. - **Method**: `GET` - **Path**: `/api/reach/v1/segmentation/segments` #### reach_createANewContactSegmentV1 Create a new contact segment. This endpoint allows creating a new contact segment that can be used to organize contacts. The segment can be configured with specific criteria like email, name, subscription status, etc. **Deprecated.** This endpoint cannot target a profile, so it always falls back to the client's default profile and cannot create segments in any other profile. Use `POST /api/reach/v1/profiles/{profileUuid}/segmentation/segments` instead. - **Method**: `POST` - **Path**: `/api/reach/v1/segmentation/segments` #### reach_countProfileSegmentContactsV1 Count the contacts currently matching a segment without listing them. Cheaper than paging through the segment contacts endpoint when only the size is needed. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}/count` #### reach_listProfileSegmentContactsV1 Retrieve contacts associated with a specific segment for a given profile. This endpoint allows you to fetch and filter contacts that belong to a particular segment, identified by its UUID, scoped to a specific profile. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}/contacts` #### reach_getProfileSegmentDetailsV1 Get a single segment of a profile, including the conditions that define it. To retrieve the contacts currently matching those conditions, use the segment contacts endpoint instead. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}` #### reach_updateAProfileSegmentV1 Rename a segment and/or replace the conditions that define it. `name` is always required. Omit `conditions` to rename without touching the conditions; supply them and they replace the existing set entirely rather than being merged into it. Contacts are never modified, but which of them match the segment can change immediately. - **Method**: `PUT` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}` #### reach_deleteAProfileSegmentV1 Delete a segment. Only the segment definition is removed. The contacts that matched it are left untouched. - **Method**: `DELETE` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}` #### reach_listSegmentFilterAttributesV1 List every attribute a segment condition can filter on, with the operators each attribute accepts, the value format they expect and, where the value is constrained, the allowed values. The list is profile specific: it includes the profile's custom contact fields, its tags and its 20 most recently published campaigns, so the valid attributes cannot be hardcoded. Read it before creating or updating a segment to discover the valid `attribute`, `operator` and `value` combinations. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/filters/attributes` #### reach_previewContactsMatchingConditionsV1 Preview the contacts matching a set of conditions without saving a segment. The body is the same set of conditions accepted when creating or updating a segment, so this is how to check who a filter reaches, and how many, before persisting it. Nothing is stored and no contact is modified. Call the segment filter attributes endpoint first to discover the valid `attribute`, `operator` and `value` combinations. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/filters/contacts` #### reach_listProfileSegmentsV1 Get a paginated list of the segments defined in a profile. Each entry carries the number of contacts currently matching it, which is recalculated on read rather than stored. Use `count_type` to count either every matching contact or only the subscribed ones. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments` #### reach_createAProfileSegmentV1 Create a segment in a profile. A segment is a saved set of conditions rather than a fixed list, so its membership changes as contacts change. Creating one does not modify any contact. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/segmentation/segments` #### reach_listSegmentContactsV1 Retrieve contacts associated with a specific segment. This endpoint allows you to fetch and filter contacts that belong to a particular segment, identified by its UUID. **Deprecated.** This endpoint cannot target a profile, so it always falls back to the client's default profile and cannot read segments of any other profile. Use `GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}/contacts` instead. - **Method**: `GET` - **Path**: `/api/reach/v1/segmentation/segments/{segmentUuid}/contacts` #### reach_getSegmentDetailsV1 Get details of a specific segment. This endpoint retrieves information about a single segment identified by UUID. Segments are used to organize and group contacts based on specific criteria. **Deprecated.** This endpoint cannot target a profile, so it always falls back to the client's default profile and cannot read segments of any other profile. Use `GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}` instead. - **Method**: `GET` - **Path**: `/api/reach/v1/segmentation/segments/{segmentUuid}` #### reach_assignAContactToATagV1 Assign a tag to a single contact. Unlike the bulk endpoint this is applied immediately rather than queued. Assigning a tag the contact already carries succeeds without duplicating it. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts/{contactUuid}` #### reach_removeAContactFromATagV1 Remove a tag from a single contact. Unlike the bulk endpoint this is applied immediately rather than queued. Neither the tag nor the contact is deleted. - **Method**: `DELETE` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts/{contactUuid}` #### reach_assignContactsToATagV1 Assign a tag to many contacts at once. Pass `contact_uuids` to target specific contacts, or `all_contacts` to target every contact in the profile. The work is queued, so a success response means it was accepted rather than finished. Contacts that already carry the tag are left alone. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts` #### reach_removeContactsFromATagV1 Remove a tag from many contacts at once. Pass `contact_uuids` to target specific contacts, or `all_contacts` to target every contact in the profile. The work is queued, so a success response means it was accepted rather than finished. The tag itself and the contacts are not deleted. - **Method**: `DELETE` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}/contacts` #### reach_deleteATagV1 Delete a tag and remove it from every contact carrying it. The contacts themselves are not deleted. This is idempotent: deleting a tag that does not exist in the profile still succeeds. - **Method**: `DELETE` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}` #### reach_renameATagV1 Rename a tag. The contacts assigned to the tag are unaffected. Names are unique within a profile, so renaming a tag to a name that is already taken is rejected. - **Method**: `PATCH` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags/{tagUuid}` #### reach_listProfileTagsV1 Get all tags defined in a profile. Tags are the way contacts are grouped in Reach, and can be used to filter the contact list or to build segments. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags` #### reach_createOrFindTagsV1 Create tags in a profile. Names that already exist in the profile are not duplicated: the existing tag is returned instead, so the call is safe to repeat. Every tag in the request is returned, whether it was created now or already existed. - **Method**: `POST` - **Path**: `/api/reach/v1/profiles/{profileUuid}/tags` #### reach_getFormDetailsV1 Get a single form with the URL of its hosted template and the tags it applies to the contacts it captures. There is no ready-made embed snippet in the response - either serve the template HTML yourself or build your own embed around the form uuid. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/forms/{formUuid}` #### reach_deleteFormV1 Permanently delete a form together with its template. A form that has already captured submissions cannot be deleted, so that the contacts it collected are never silently discarded - pause the form instead to stop it collecting new ones. Views alone do not block deletion. - **Method**: `DELETE` - **Path**: `/api/reach/v1/profiles/{profileUuid}/forms/{formUuid}` #### reach_listFormsV1 Get a paginated list of the signup forms in a profile. Each form carries a reference to the template that renders it. Get the form details for a directly usable template URL and for the tags the form puts on the contacts it captures. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/forms` #### reach_getProfileDomainDNSStatusV1 Retrieve the DNS configuration status for a profile's domain. This endpoint reports the state of MX, SPF, DKIM and DMARC records, including the actual records found and the suggested records required for correct email delivery. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/domains/dns-status` #### reach_getConnectedSendingDomainV1 Get the sending domain connected to the profile, its verification status and any suspended sender addresses. Campaigns only go out once a domain is connected and active, so this is the cheapest way to check that precondition before building one. A profile with no domain connected returns the same shape with every field set to `null`. For the individual MX, SPF, DKIM and DMARC records behind the status, use the DNS status endpoint. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/domains` #### reach_listPlanFeatureAccessV1 List which plan features the profile can use. This is the feature lock matrix, not a usage quota. `available` means the feature can be used right now and `locked` means it is not part of the base plan, so an upgrade is needed. For remaining emails, recipients and AI credits use the limits endpoint instead. Worth checking before building something that cannot be activated afterwards, such as an automation on a plan without automation activation. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/features` #### reach_getRemainingPlanLimitsV1 Get how much of the plan is left for the current period. Two things to keep in mind before you build alerting on this. The period is a calendar month rather than a billing anniversary, so the counters reset on the 1st no matter when the subscription started. And usage is tracked per order, so every profile on the same order shares one pool and reports the same numbers here. Only the current period is available, past usage is not kept. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles/{profileUuid}/limits` #### reach_listProfilesV1 This endpoint returns all profiles available to the client, including their basic information. - **Method**: `GET` - **Path**: `/api/reach/v1/profiles` ### `hostinger-vps-mcp` #### VPS_getDataCenterListV1 Retrieve all available data centers. Use this endpoint to view location options before deploying VPS instances. - **Method**: `GET` - **Path**: `/api/vps/v1/data-centers` #### VPS_getProjectContainersV1 Retrieves a list of all containers belonging to a specific Docker Compose project on the virtual machine. This endpoint returns detailed information about each container including their current status, port mappings, and runtime configuration. Use this to monitor the health and state of all services within your Docker Compose project. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/containers` #### VPS_getProjectContentsV1 Retrieves the complete project information including the docker-compose.yml file contents, project metadata, and current deployment status. This endpoint provides the full configuration and state details of a specific Docker Compose project. Use this to inspect project settings, review the compose file, or check the overall project health. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}` #### VPS_deleteProjectV1 Completely removes a Docker Compose project from the virtual machine, stopping all containers and cleaning up associated resources including networks, volumes, and images. This operation is irreversible and will delete all project data. Use this when you want to permanently remove a project and free up system resources. - **Method**: `DELETE` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/down` #### VPS_getProjectListV1 Retrieves a list of all Docker Compose projects currently deployed on the virtual machine. This endpoint returns basic information about each project including name, status, file path and list of containers with details about their names, image, status, health and ports. Container stats are omitted in this endpoint. If you need to get detailed information about container with stats included, use the `Get project containers` endpoint. Use this to get an overview of all Docker projects on your VPS instance. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker` #### VPS_createNewProjectV1 Deploy new project from docker-compose.yaml contents or download contents from URL. URL can be Github repository url in format https://github.com/[user]/[repo] and it will be automatically resolved to docker-compose.yaml file in master branch. Any other URL provided must return docker-compose.yaml file contents. If project with the same name already exists, existing project will be replaced. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker` #### VPS_getProjectLogsV1 Retrieves aggregated log entries from all services within a Docker Compose project. This endpoint returns recent log output from each container, organized by service name with timestamps. The response contains the last 300 log entries across all services. Use this for debugging, monitoring application behavior, and troubleshooting issues across your entire project stack. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/logs` #### VPS_restartProjectV1 Restarts all services in a Docker Compose project by stopping and starting containers in the correct dependency order. This operation preserves data volumes and network configurations while refreshing the running containers. Use this to apply configuration changes or recover from service failures. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/restart` #### VPS_startProjectV1 Starts all services in a Docker Compose project that are currently stopped. This operation brings up containers in the correct dependency order as defined in the compose file. Use this to resume a project that was previously stopped or to start services after a system reboot. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/start` #### VPS_stopProjectV1 Stops all running services in a Docker Compose project while preserving container configurations and data volumes. This operation gracefully shuts down containers in reverse dependency order. Use this to temporarily halt a project without removing data or configurations. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/stop` #### VPS_updateProjectV1 Updates a Docker Compose project by pulling the latest image versions and recreating containers with new configurations. This operation preserves data volumes while applying changes from the compose file. Use this to deploy application updates, apply configuration changes, or refresh container images to their latest versions. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/update` #### VPS_activateFirewallV1 Activate a firewall for a specified virtual machine. Only one firewall can be active for a virtual machine at a time. Use this endpoint to apply firewall rules to VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/firewall/{firewallId}/activate/{virtualMachineId}` #### VPS_deactivateFirewallV1 Deactivate a firewall for a specified virtual machine. Use this endpoint to remove firewall protection from VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/firewall/{firewallId}/deactivate/{virtualMachineId}` #### VPS_getFirewallDetailsV1 Retrieve firewall by its ID and rules associated with it. Use this endpoint to view specific firewall configuration and rules. - **Method**: `GET` - **Path**: `/api/vps/v1/firewall/{firewallId}` #### VPS_deleteFirewallV1 Delete a specified firewall. Any virtual machine that has this firewall activated will automatically have it deactivated. Use this endpoint to remove unused firewall configurations. - **Method**: `DELETE` - **Path**: `/api/vps/v1/firewall/{firewallId}` #### VPS_getFirewallListV1 Retrieve all available firewalls. Use this endpoint to view existing firewall configurations. - **Method**: `GET` - **Path**: `/api/vps/v1/firewall` #### VPS_createNewFirewallV1 Create a new firewall. Use this endpoint to set up new firewall configurations for VPS security. - **Method**: `POST` - **Path**: `/api/vps/v1/firewall` #### VPS_updateFirewallRuleV1 Update a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to modify existing firewall rules. - **Method**: `PUT` - **Path**: `/api/vps/v1/firewall/{firewallId}/rules/{ruleId}` #### VPS_deleteFirewallRuleV1 Delete a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to remove specific firewall rules. - **Method**: `DELETE` - **Path**: `/api/vps/v1/firewall/{firewallId}/rules/{ruleId}` #### VPS_createFirewallRuleV1 Create new firewall rule for a specified firewall. By default, the firewall drops all incoming traffic, which means you must add accept rules for all ports you want to use. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to add new security rules to firewalls. - **Method**: `POST` - **Path**: `/api/vps/v1/firewall/{firewallId}/rules` #### VPS_syncFirewallV1 Sync a firewall for a specified virtual machine. Firewall can lose sync with virtual machine if the firewall has new rules added, removed or updated. Use this endpoint to apply updated firewall rules to VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/firewall/{firewallId}/sync/{virtualMachineId}` #### VPS_getPostInstallScriptV1 Retrieve post-install script by its ID. Use this endpoint to view specific automation script details. - **Method**: `GET` - **Path**: `/api/vps/v1/post-install-scripts/{postInstallScriptId}` #### VPS_updatePostInstallScriptV1 Update a specific post-install script. Use this endpoint to modify existing automation scripts. - **Method**: `PUT` - **Path**: `/api/vps/v1/post-install-scripts/{postInstallScriptId}` #### VPS_deletePostInstallScriptV1 Delete a post-install script from your account. Use this endpoint to remove unused automation scripts. - **Method**: `DELETE` - **Path**: `/api/vps/v1/post-install-scripts/{postInstallScriptId}` #### VPS_getPostInstallScriptsV1 Retrieve post-install scripts associated with your account. Use this endpoint to view available automation scripts for VPS deployment. - **Method**: `GET` - **Path**: `/api/vps/v1/post-install-scripts` #### VPS_createPostInstallScriptV1 Add a new post-install script to your account, which can then be used after virtual machine installation. The script contents will be saved to the file `/post_install` with executable attribute set and will be executed once virtual machine is installed. The output of the script will be redirected to `/post_install.log`. Maximum script size is 48KB. Use this endpoint to create automation scripts for VPS setup tasks. - **Method**: `POST` - **Path**: `/api/vps/v1/post-install-scripts` #### VPS_attachPublicKeyV1 Attach existing public keys from your account to a specified virtual machine. Multiple keys can be attached to a single virtual machine. Use this endpoint to enable SSH key authentication for VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/public-keys/attach/{virtualMachineId}` #### VPS_deletePublicKeyV1 Delete a public key from your account. **Deleting public key from account does not remove it from virtual machine** Use this endpoint to remove unused SSH keys from account. - **Method**: `DELETE` - **Path**: `/api/vps/v1/public-keys/{publicKeyId}` #### VPS_getPublicKeysV1 Retrieve public keys associated with your account. Use this endpoint to view available SSH keys for VPS authentication. - **Method**: `GET` - **Path**: `/api/vps/v1/public-keys` #### VPS_createPublicKeyV1 Add a new public key to your account. Use this endpoint to register SSH keys for VPS authentication. - **Method**: `POST` - **Path**: `/api/vps/v1/public-keys` #### VPS_getTemplateDetailsV1 Retrieve detailed information about a specific OS template for virtual machines. Use this endpoint to view specific template specifications before deployment. - **Method**: `GET` - **Path**: `/api/vps/v1/templates/{templateId}` #### VPS_getTemplatesV1 Retrieve available OS templates for virtual machines. Use this endpoint to view operating system options before creating or recreating VPS instances. - **Method**: `GET` - **Path**: `/api/vps/v1/templates` #### VPS_getActionDetailsV1 Retrieve detailed information about a specific action performed on a specified virtual machine. Use this endpoint to monitor specific VPS operation status and details. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/actions/{actionId}` #### VPS_getActionsV1 Retrieve actions performed on a specified virtual machine. Actions are operations or events that have been executed on the virtual machine, such as starting, stopping, or modifying the machine. This endpoint allows you to view the history of these actions, providing details about each action, such as the action name, timestamp, and status. Use this endpoint to view VPS operation history and troubleshoot issues. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/actions` #### VPS_getAttachedPublicKeysV1 Retrieve public keys attached to a specified virtual machine. Use this endpoint to view SSH keys configured for specific VPS instances. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/public-keys` #### VPS_getBackupsV1 Retrieve backups for a specified virtual machine. Use this endpoint to view available backup points for VPS data recovery. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/backups` #### VPS_restoreBackupV1 Restore a backup for a specified virtual machine. The system will then initiate the restore process, which may take some time depending on the size of the backup. **All data on the virtual machine will be overwritten with the data from the backup.** Use this endpoint to recover VPS data from backup points. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/backups/{backupId}/restore` #### VPS_setHostnameV1 Set hostname for a specified virtual machine. Changing hostname does not update PTR record automatically. If you want your virtual machine to be reachable by a hostname, you need to point your domain A/AAAA records to virtual machine IP as well. Use this endpoint to configure custom hostnames for VPS instances. - **Method**: `PUT` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/hostname` #### VPS_resetHostnameV1 Reset hostname and PTR record of a specified virtual machine to default value. Use this endpoint to restore default hostname configuration for VPS instances. - **Method**: `DELETE` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/hostname` #### VPS_getVirtualMachineDetailsV1 Retrieve detailed information about a specified virtual machine. Use this endpoint to view comprehensive VPS configuration and status. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}` #### VPS_getVirtualMachinesV1 Retrieve all available virtual machines. Use this endpoint to view available VPS instances. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines` #### VPS_purchaseNewVirtualMachineV1 Purchase and setup a new virtual machine. If virtual machine setup fails for any reason, login to [hPanel](https://hpanel.hostinger.com/) and complete the setup manually. If no payment method is provided, your default payment method will be used automatically. Use this endpoint to create new VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines` #### VPS_getScanMetricsV1 Retrieve scan metrics for the [Monarx](https://www.monarx.com/) malware scanner installed on a specified virtual machine. The scan metrics provide detailed information about malware scans performed by Monarx, including number of scans, detected threats, and other relevant statistics. This information is useful for monitoring security status of the virtual machine and assessing effectiveness of the malware scanner. Use this endpoint to monitor VPS security scan results and threat detection. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/monarx` #### VPS_installMonarxV1 Install the Monarx malware scanner on a specified virtual machine. [Monarx](https://www.monarx.com/) is a security tool designed to detect and prevent malware infections on virtual machines. By installing Monarx, users can enhance the security of their virtual machines, ensuring that they are protected against malicious software. Use this endpoint to enable malware protection on VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/monarx` #### VPS_uninstallMonarxV1 Uninstall the Monarx malware scanner on a specified virtual machine. If Monarx is not installed, the request will still be processed without any effect. Use this endpoint to remove malware scanner from VPS instances. - **Method**: `DELETE` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/monarx` #### VPS_getMetricsV1 Retrieve historical metrics for a specified virtual machine. It includes the following metrics: - CPU usage - Memory usage - Disk usage - Network usage - Uptime Use this endpoint to monitor VPS performance and resource utilization over time. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/metrics` #### VPS_setNameserversV1 Set nameservers for a specified virtual machine. Be aware, that improper nameserver configuration can lead to the virtual machine being unable to resolve domain names. Use this endpoint to configure custom DNS resolvers for VPS instances. - **Method**: `PUT` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/nameservers` #### VPS_createPTRRecordV1 Create or update a PTR (Pointer) record for a specified virtual machine. Use this endpoint to configure reverse DNS lookup for VPS IP addresses. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/ptr/{ipAddressId}` #### VPS_deletePTRRecordV1 Delete a PTR (Pointer) record for a specified virtual machine. Once deleted, reverse DNS lookups to the virtual machine's IP address will no longer return the previously configured hostname. Use this endpoint to remove reverse DNS configuration from VPS instances. - **Method**: `DELETE` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/ptr/{ipAddressId}` #### VPS_setPanelPasswordV1 Set panel password for a specified virtual machine. If virtual machine does not use panel OS, the request will still be processed without any effect. Requirements for password are same as in the [recreate virtual machine endpoint](/#tag/vps-virtual-machine/POST/api/vps/v1/virtual-machines/{virtualMachineId}/recreate). Use this endpoint to configure control panel access credentials for VPS instances. - **Method**: `PUT` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/panel-password` #### VPS_startRecoveryModeV1 Initiate recovery mode for a specified virtual machine. Recovery mode is a special state that allows users to perform system rescue operations, such as repairing file systems, recovering data, or troubleshooting issues that prevent the virtual machine from booting normally. Virtual machine will boot recovery disk image and original disk image will be mounted in `/mnt` directory. Use this endpoint to enable system rescue operations on VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/recovery` #### VPS_stopRecoveryModeV1 Stop recovery mode for a specified virtual machine. If virtual machine is not in recovery mode, this operation will fail. Use this endpoint to exit system rescue mode and return VPS to normal operation. - **Method**: `DELETE` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/recovery` #### VPS_recreateVirtualMachineV1 Recreate a virtual machine from scratch. The recreation process involves reinstalling the operating system and resetting the virtual machine to its initial state. Snapshots, if there are any, will be deleted. ## Password Requirements Password will be checked against leaked password databases. Requirements for the password are: - At least 12 characters long - At least one uppercase letter - At least one lowercase letter - At least one number - Is not leaked publicly **This operation is irreversible and will result in the loss of all data stored on the virtual machine!** Use this endpoint to completely rebuild VPS instances with fresh OS installation. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/recreate` #### VPS_restartVirtualMachineV1 Restart a specified virtual machine by fully stopping and starting it. If the virtual machine was stopped, it will be started. Use this endpoint to reboot VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/restart` #### VPS_setRootPasswordV1 Set root password for a specified virtual machine. Requirements for password are same as in the [recreate virtual machine endpoint](/#tag/vps-virtual-machine/POST/api/vps/v1/virtual-machines/{virtualMachineId}/recreate). Use this endpoint to update administrator credentials for VPS instances. - **Method**: `PUT` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/root-password` #### VPS_setupPurchasedVirtualMachineV1 Setup newly purchased virtual machine with `initial` state. Use this endpoint to configure and initialize purchased VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/setup` #### VPS_getSnapshotV1 Retrieve snapshot for a specified virtual machine. Use this endpoint to view current VPS snapshot information. - **Method**: `GET` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/snapshot` #### VPS_createSnapshotV1 Create a snapshot of a specified virtual machine. A snapshot captures the state and data of the virtual machine at a specific point in time, allowing users to restore the virtual machine to that state if needed. This operation is useful for backup purposes, system recovery, and testing changes without affecting the current state of the virtual machine. **Creating new snapshot will overwrite the existing snapshot!** Use this endpoint to capture VPS state for backup and recovery purposes. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/snapshot` #### VPS_deleteSnapshotV1 Delete a snapshot of a specified virtual machine. Use this endpoint to remove VPS snapshots. - **Method**: `DELETE` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/snapshot` #### VPS_restoreSnapshotV1 Restore a specified virtual machine to a previous state using a snapshot. Restoring from a snapshot allows users to revert the virtual machine to that state, which is useful for system recovery, undoing changes, or testing. Use this endpoint to revert VPS instances to previous saved states. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/snapshot/restore` #### VPS_startVirtualMachineV1 Start a specified virtual machine. If the virtual machine is already running, the request will still be processed without any effect. Use this endpoint to power on stopped VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/start` #### VPS_stopVirtualMachineV1 Stop a specified virtual machine. If the virtual machine is already stopped, the request will still be processed without any effect. This is a compute-only power state change and does not affect billing. To stop future charges, disable auto-renewal on the owning subscription. Use this endpoint to power off running VPS instances. - **Method**: `POST` - **Path**: `/api/vps/v1/virtual-machines/{virtualMachineId}/stop` ### `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_importWordPressWebsiteV1 Import WordPress website to the specified domain. WARNING: this overwrites the website's existing contents and cannot be undone — verify this is intended before calling this endpoint. This endpoint allows you to import a WordPress website from archive and database files that have been uploaded to the website's directory. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/wordpress/import` #### 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_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. 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_deployWordPressPluginV1 Deploy a WordPress plugin from an already uploaded directory. This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website's directory. The plugin will be activated and made available in the WordPress admin panel. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/wordpress/plugins/deploy` #### 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_deployWordPressThemeV1 Deploy a WordPress theme from an already uploaded directory. This endpoint allows you to deploy a WordPress theme that has been uploaded to the website's directory. The theme can be optionally activated after deployment. - **Method**: `POST` - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/wordpress/themes/deploy` #### 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`