America Hostinger

You run the Hostinger MCP server to expose Hostinger API tooling through the Model Context Protocol, letting MCP clients discover, connect, and run hosting-related operations securely and efficiently.

How to use

Connect to the MCP server using an MCP client that supports HTTP streaming transport. The server exposes a bidirectional stream over HTTP for real-time interactions and also supports a local stdio transport for in-process usage.

How to install

Prerequisites: you need Node.js version 24 or higher. Install Node.js from your preferred source or use a version manager to ensure you run the correct version.

Install the MCP server globally using one of the package managers shown below. Choose only one installation method.

# 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

Additional configuration and usage notes

Configuration requires setting environment variables when you run the server. Use DEBUG to enable debug logging and API_TOKEN to authorize requests from clients.

Two transport modes are supported: Standard I/O (stdio) for local usage and Streamable HTTP for remote access. If you run as a local tool, you can start it without any transport flags and it will use stdio by default. To enable HTTP transport, pass the --http flag.

Example startup commands you may use directly in your environment:

# Default HTTP transport on localhost:8100
hostinger-api-mcp --http

# Specify host and port
hostinger-api-mcp --http --host 0.0.0.0 --port 8150

Environment variables and tooling

Environment variables you may configure when running the server include DEBUG and API_TOKEN. DEBUG toggles debug logging (true/false), and API_TOKEN is used by clients to authorize with the MCP server.

Security and best practices

Treat API_TOKEN like a secret. Store it in a secure environment file or secret manager, and avoid printing it in logs. When exposing the HTTP transport, restrict access to trusted networks and consider enabling TLS in production deployments.

Examples of common MCP client interactions

Once connected, you can list available tools and call specific tools exposed by the server. For example, a client can query the catalog of hosting operations and initiate actions such as deploying WordPress slices, domains, or VPS configurations.

Available tools

hosting_importWordpressWebsite

Imports a WordPress site from an archive and database dump onto a hosting server. Uploads the site archive and db dump, then extracts and makes the site available after deployment.

hosting_deployWordpressPlugin

Deploys a WordPress plugin from a directory to the hosting server by uploading all plugin files and triggering deployment.

hosting_deployWordpressTheme

Deploys a WordPress theme from a directory and optionally activates it after deployment.

hosting_deployJsApplication

Deploys a JavaScript application from an archive to a hosting server. The archive should contain only source files; the server builds after upload.

hosting_deployStaticWebsite

Deploys a pre-built static website archive to a hosting server without a build step.

hosting_listJsDeployments

Lists JavaScript deployments for a domain to monitor status and progress.

hosting_showJsDeploymentLogs

Retrieves logs for a specific JavaScript deployment to aid debugging.

billing_getCatalogItemListV1

Retrieves catalog items with pricing for services available to order.

billing_createServiceOrderV1

Creates a new service order with payment options and catalog items.

billing_setDefaultPaymentMethodV1

Sets the default payment method for future orders.

domains_purchaseNewDomainV1

Purchases and registers a new domain with optional contacts and additional details.

DNS_getDNSRecordsV1

Retrieves DNS zone records for a domain.

DNS_updateDNSRecordsV1

Updates DNS records for a domain with overwrite semantics.

DNS_resetDNSRecordsV1

Resets DNS zone to default records for a domain.

VPS_getVirtualMachineDetailsV1

Provides detailed information about a specific VPS instance.

VPS_purchaseNewVirtualMachineV1

Creates a new virtual machine with specified options and setup.

VPS_recreateVirtualMachineV1

Recreates a virtual machine from scratch with a new OS image and password.