Api MCP Server

hostinger-api-mcp

Model Context Protocol (MCP) server for Hostinger API.

Prerequisites

• Node.js version 24 or higher

If you don't have Node.js installed, you can download it from the official website. Alternatively, you can use a package manager like Homebrew (for macOS) or Chocolatey (for Windows) to install Node.js.

We recommend using NVM (Node Version Manager) to install and manage installed Node.js versions. After installing NVM, you can install Node.js with the following command:

nvm install v24
nvm use v24

Installation

To install the MCP server, run one of the following command, depending on your package manager:

# 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:

# 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 (146 total)
• hostinger-billing-mcp — 7 tools for billing
• hostinger-dns-mcp — 8 tools for dns
• hostinger-domains-mcp — 18 tools for domains
• hostinger-ecommerce-mcp — 7 tools for ecommerce
• hostinger-horizons-mcp — 2 tools for horizons
• hostinger-hosting-mcp — 30 tools for hosting
• hostinger-reach-mcp — 12 tools for reach
• hostinger-vps-mcp — 62 tools for vps

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:

# 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.

{
    "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:

# 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:

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-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_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.

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

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_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 10 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_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_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 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_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_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_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_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_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_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

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. 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.

• 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.

• 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. 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 archive will be extracted and deployed directly without any build steps. 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_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_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_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_createNodeJSBuildFromArchiveV1

Upload a project archive, auto-detect build settings, and immediately start a Node.js build.

This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website's file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.

Before archiving, exclude node_modules/ and any build output directories (e.g. dist/, .next/, build/) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.

Example (zip):

zip -r archive.zip . --exclude "node_modules/*" --exclude "dist/*"

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/from-archive

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_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_listWebsitesV1

Retrieve a paginated list of websites (main and addon types) 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.

Use the available query parameters to filter results 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_installWordPressV1

Install WordPress on an existing website.

The website must already exist before calling this endpoint. To create a new website first, use POST /api/hosting/v1/websites and poll GET /api/hosting/v1/websites until it appears.

Call GET /api/hosting/v1/wordpress/installations filtered by username and domain before proceeding to check whether WordPress is already installed on the target domain/path. If WordPress already exists and overwrite is false (the default), the async job will fail.

This operation is asynchronous: a successful response only means the install job has been queued, not that WordPress is ready. Installation typically takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered by username and domain to track progress. When the installation appears in that list, WordPress is ready.

• Method: POST
• Path: /api/hosting/v1/accounts/{username}/wordpress/installations

hosting_listWordPressInstallationsV1

List WordPress installations accessible to the authenticated client.

Use this endpoint to discover existing WordPress installations and to poll for installation status after calling the install endpoint. When a newly requested installation appears in this list, WordPress is ready. Filter by username and domain to narrow results to a specific website.

Each installation includes a valid flag and, when invalid, a validationError describing why.

• Method: GET
• Path: /api/hosting/v1/wordpress/installations

hostinger-reach-mcp

reach_deleteAContactV1

Delete a contact with the specified UUID.

This endpoint permanently removes a contact from the email marketing system.

• Method: DELETE
• Path: /api/reach/v1/contacts/{uuid}

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.

• 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_listSegmentsV1

Get a list of all contact segments.

This endpoint returns a list of contact segments that can be used to organize contacts.

• 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.

• Method: POST
• Path: /api/reach/v1/segmentation/segments

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_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.

• 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.

• Method: GET
• Path: /api/reach/v1/segmentation/segments/{segmentUuid}

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_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_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

Documentation truncated — see the full README on GitHub.