home / mcp / hostinger mcp server
Exposes Hostinger hosting, DNS, domains, billing, and VPS operations via MCP for programmatic control.
Configuration
View docs{
"mcpServers": {
"hostinger-api-mcp-server": {
"url": "http://localhost:8100/",
"headers": {
"DEBUG": "false",
"API_TOKEN": "YOUR_API_TOKEN"
}
}
}
}You are provisioning and operating a Model Context Protocol (MCP) server for Hostinger API. This MCP server enables you to expose hosting, billing, DNS, domains, VPS, and related services to MCP-compatible clients, supporting both HTTP streaming and local stdio transports for flexible integration and automation.
You connect to the MCP server using an MCP client over HTTP streaming to enable bidirectional communication. The server exposes a rich set of tools that cover WordPress deployment, static sites, JavaScript applications, domain operations, billing actions, DNS management, VPS provisioning, firewall rules, and more. After you connect, you can list available tools, then call any tool by name with the required arguments as described in each tool’s parameters. Use the API token you configure to authorize requests.
Prerequisites: ensure you have Node.js version 24 or higher installed on your machine.
Install the MCP server using your preferred package manager. Choose one of the following global installation commands.
# 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-mcpConfiguration and runtime enablement are controlled via environment variables. You can set the following when starting the server: DEBUG to enable debug logging, and API_TOKEN to supply your authorization token.
Transport options include Standard I/O transport (stdio) and Streamable HTTP transport. The HTTP transport is configured by running the MCP server with the --http flag and optional host/port overrides. The stdio mode is the default when the --http flag is not used.
Quick start example for HTTP transport: run the MCP server and then connect a client over HTTP to http://localhost:8100/. You can customize the host and port with the --host and --port options.
Example connection snippet for an MCP client using HTTP streaming transport: the client creates an HTTP transport to the server URL and includes the API token in the Authorization header. It then connects, lists available tools, and calls a tool by name with the required arguments.
Important usage notes: when deploying large WordPress sites, plugins, or themes, allow time for file transfers and server-side processing. For JS applications and static websites, ensure you provide the correct archive files or directories as instructed by each tool’s parameters.
Environment variables you configure are surfaced to the MCP server as part of the runtime environment. Keep your API_TOKEN secret and rotate it as needed. Avoid sharing tokens in logs or in client-side code.
The server supports a broad set of tools for hosting, billing, DNS, domains, and VPS management. Review each tool’s parameter list to understand required fields, optional filters, and behavior (for example, whether a request creates, updates, or deletes resources).
If you encounter connectivity issues, verify the MCP server is listening on the expected host/port and that your client uses a valid Authorization header with the API token.
For deployment status or error details, use the respective list or show tools to retrieve status, logs, or error messages from the server.
The MCP server provides a comprehensive set of capabilities for hosting management, billing, DNS, domains, and VPS operations. See individual tool entries in the tool list to learn required parameters and usage patterns.
Import a WordPress website from an archive to a hosting server by uploading the website archive and a database dump. The archive is extracted on the server and the site becomes available after extraction.
Deploy a WordPress plugin from a directory to a hosting server; uploads plugin files and triggers deployment.
Deploy a WordPress theme from a directory to a hosting server; can optionally activate the theme after deployment.
Deploy a JavaScript application from an archive to a hosting server. The archive should contain only source files (no build output). Build runs automatically on the server after upload; check deployment status with the related tooling.
Deploy a prebuilt static website archive to a hosting server. This bypasses any build steps and serves static assets directly.
List JavaScript deployments for a domain to monitor status, supporting pagination and optional state filtering.
Retrieve logs for a specific JavaScript deployment to help debug build or runtime issues.
Retrieve catalog items with pricing to review available services before purchasing.
Create a new service order by providing payment method, catalog items, and optional coupons; orders can renew automatically.
Set the default payment method for future orders.
Delete a payment method from your account.
List available payment methods for new orders.
List all subscriptions tied to your account for monitoring status.
Disable auto-renewal for a given subscription.
Enable auto-renewal for a given subscription.
Retrieve contents of a specific DNS snapshot for a domain.
List DNS snapshots for a domain.
Restore a DNS zone from a selected snapshot.
Retrieve DNS zone records for a domain.
Update DNS records for a domain with control over overwrite/append behavior.
Delete specific DNS records from a domain.
Reset DNS zone to default records for a domain.
Validate DNS records prior to updates to ensure correctness.
Retrieve domain verifications in progress or completed.
Check domain name availability across multiple TLDs.
Retrieve current domain forwarding configuration.
Delete domain forwarding configuration.
Create domain forwarding to a target URL with a specified redirect type.
Enable domain transfer lock to prevent unauthorized transfers.
Disable domain transfer lock to allow transfers.
Retrieve detailed information for a domain.
List all domains in your portfolio.
Register and purchase a new domain, providing ownership details and payment info.
Enable WHOIS privacy protection for a domain.
Disable WHOIS privacy protection for a domain.
Set custom nameservers for a domain.
Retrieve a WHOIS contact profile by ID.
Delete a WHOIS contact profile from your account.
List available WHOIS contact profiles for registration.
Create a new WHOIS contact profile with TLD and contact details.
List domains using a specific WHOIS contact profile.
List available datacenters for hosting plans and recommendations.
Generate a free subdomain for hosting without purchasing a custom domain.
Verify domain ownership by checking accessibility or by adding a DNS TXT record.
List hosting orders with pagination and filtering by status or IDs.
List websites associated with your hosting accounts, with filtering options.
Create a new website by providing a domain and associated order; specify datacenter on first site.
Delete a contact by UUID from the email marketing system.
List all contact groups for organizing contacts.
List contacts with optional filters by group and subscription status.
Create a new contact with basic information; supports double opt-in flow.
List all segmentation segments for organizing contacts.
Create a new contact segment with criteria and logic for grouping contacts.
Retrieve contacts belonging to a specific segment with pagination.
Get details about a specific contact segment.
Create a new contact under a specific profile for email marketing.
List all profiles available to the client.
Retrieve all available VPS data centers.
List containers for a Docker Compose project on a VM with status and port mappings.
Retrieve full project contents and deployment status for a Docker Compose project.
Delete a Docker Compose project and clean up resources on the VM.
List all Docker Compose projects on the VM with overview details.
Deploy a new Docker Compose project from a YAML/URL source; replaces existing project if name clashes.
Retrieve aggregated logs for services in a Docker Compose project.
Restart all services in a Docker Compose project in dependency order.
Start all services of a Docker Compose project.
Stop all services of a Docker Compose project while preserving data.
Update a Docker Compose project by pulling latest images and recreating containers.
Activate a firewall on a VM; only one firewall can be active at a time.
Deactivate a firewall on a VM.
Retrieve details and rules of a specific firewall.
Delete a firewall configuration.
List all available firewalls.
Create a new firewall configuration.
Update a single firewall rule within a firewall.
Delete a specific firewall rule.
Create a new firewall rule for a firewall.
Synchronize firewall rules with the virtual machine.
Retrieve a post-install automation script by ID.
Update a post-install automation script.
Delete a post-install automation script.
List all post-install automation scripts.
Create a new post-install automation script.
Attach existing public keys to a VM to enable SSH access.
Delete a public key from your account; keys remain on VMs unless removed individually.
List public keys available in your account.
Add a new SSH public key to your account.
Retrieve details of a specific OS template for VMs.
List available OS templates for virtual machines.
Retrieve detailed information about a specific action on a VM.
List actions performed on a VM to review history.
List public keys attached to a specific VM.
List available backups for a VM.
Restore a VM from a backup point.
Set a custom hostname for a VM with notes about DNS mapping.
Reset the VM hostname to the default.
Retrieve detailed information for a specific VM.
List all available virtual machines.
Purchase and set up a new VM with initial configuration.
Retrieve Monarx malware scanner metrics for a VM.
Install the Monarx malware scanner on a VM.
Uninstall the Monarx malware scanner from a VM.
Retrieve historical VPS metrics such as CPU, memory, disk, network, and uptime.
Configure custom DNS resolvers (nameservers) for a VM.
Create or update a PTR record for reverse DNS on a VM.
Delete a PTR record for a VM.
Set the control panel password for a VM.
Enter recovery mode for system rescue and repair operations.
Exit recovery mode and return VM to normal operation.
Recreate a VM from scratch with a fresh OS and clean state.
Restart the VM by fully stopping and starting it.
Set the root password for the VM.
Finalize setup for a newly purchased VM using initial configurations.
Retrieve VM snapshot details.
Create a new VM snapshot; this overwrites existing snapshot.
Delete a VM snapshot.
Restore a VM to a previous snapshot state.
Start a VM that is stopped.
Stop a running VM.