Hostinger MCP Server

Official Hostinger MCP server exposing 118 tools across VPS, domains, DNS, hosting, billing, and email marketing through the Hostinger API.

Cloud Infrastructure by Hostinger Bearer Token active

GitHub Docs npm: hostinger-api-mcp

Overview

The Hostinger API MCP Server is the official Model Context Protocol implementation maintained by Hostinger. It wraps the Hostinger developer API and exposes 118 tools that let AI agents manage hosting infrastructure: registering domains, configuring DNS zones, provisioning and operating VPS instances, deploying WordPress and JavaScript apps, handling subscriptions and payment methods, and running email marketing flows through Hostinger Reach.

The package ships seven specialized binaries so you can scope the agent to a single product area instead of loading the entire surface. hostinger-api-mcp is the unified server with all 118 tools, while hostinger-billing-mcp (7 tools), hostinger-dns-mcp (8 tools), hostinger-domains-mcp (18 tools), hostinger-hosting-mcp (13 tools), hostinger-reach-mcp (10 tools), and hostinger-vps-mcp (62 tools) cover individual domains. VPS coverage is the most extensive, including provisioning, firewall rules, Docker project deployment, backups and snapshots, Monarx malware scanning, PTR record management, SSH key management, and performance metrics.

The server supports both stdio (default) and HTTP streaming transport (via --http, default localhost:8100), making it usable inside Claude Desktop, Cursor, VS Code, and remote agent setups. Authentication is a single Hostinger API token passed via the API_TOKEN environment variable.

Tools

Tool	Description
`hostinger-api-mcp`	Unified binary exposing all 118 Hostinger API tools across billing, DNS, domains, hosting, reach, and VPS.
`hostinger-billing-mcp`	7 tools for browsing the catalog, managing payment methods, listing and inspecting subscriptions, and toggling auto-renewal.
`hostinger-dns-mcp`	8 tools for managing DNS zone records, taking and restoring snapshots, and validating record changes.
`hostinger-domains-mcp`	18 tools for domain availability checks, registration, forwarding, lock control, privacy protection, nameserver updates, and WHOIS contact profiles.
`hostinger-hosting-mcp`	13 tools for creating websites, deploying WordPress with plugins and themes, deploying JavaScript and static apps, and verifying domains.
`hostinger-reach-mcp`	10 tools for managing email marketing contacts, groups, segments, and profiles in Hostinger Reach.
`hostinger-vps-mcp`	62 tools for VPS provisioning, start/stop/restart, OS reinstall, root password reset, SSH keys, firewall rules, Docker project deployment, backups, snapshots, PTR records, Monarx malware scanning, and CPU/RAM/disk metrics.

Setup Guide

Prerequisites

Node.js v24 or higher (the README recommends managing Node with NVM)
A Hostinger account and an API token generated from your Hostinger dashboard

Install

npm install -g hostinger-api-mcp
# or: yarn global add hostinger-api-mcp
# or: pnpm add -g hostinger-api-mcp

Claude Desktop / Cursor config

Add the following to your MCP client config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "hostinger-api": {
      "command": "hostinger-api-mcp",
      "env": {
        "DEBUG": "false",
        "API_TOKEN": "YOUR_HOSTINGER_API_TOKEN"
      }
    }
  }
}

Scoped binaries

If you only need part of the API surface, use one of the specialized binaries instead of hostinger-api-mcp:

hostinger-billing-mcp
hostinger-dns-mcp
hostinger-domains-mcp
hostinger-hosting-mcp
hostinger-reach-mcp
hostinger-vps-mcp

HTTP transport (optional)

Run the server over HTTP streaming instead of stdio:

hostinger-api-mcp --http --host localhost --port 8100

Environment variables

API_TOKEN (required): your Hostinger API token, sent as a Bearer token in the Authorization header
DEBUG (optional): set to true for verbose logging, default false

Use Cases

Provision a VPS, configure its firewall rules, set up a PTR record, and deploy a Docker project end to end from an agent prompt
Register a new domain, set WHOIS privacy and contact profile, then point nameservers and create DNS A/CNAME records for it
Deploy a WordPress site with specific plugins and themes onto an existing Hostinger hosting plan
Audit subscriptions and payment methods, then disable auto-renewal on unused services to cut spend
Monitor VPS CPU, RAM, and disk metrics, take a snapshot, and run a Monarx malware scan as part of a routine ops check

Example Prompts

"Check if acme-shop.com is available, register it with WHOIS privacy, and create A records pointing to my VPS at 203.0.113.10."
"List all my VPS instances, show CPU and RAM usage for the last 24 hours, and restart any that are using over 90 percent RAM."
"Deploy a WordPress site on my hosting plan with the Yoast SEO and WooCommerce plugins installed."
"Take a DNS snapshot of example.com, then update the MX records to use Google Workspace."
"Show me all active subscriptions, their renewal dates, and turn off auto-renewal for any VPS I haven't used in 30 days."

Pros

Officially maintained by Hostinger under the hostinger GitHub organization
Very broad coverage: 118 tools spanning the full Hostinger product line
Modular binaries let you load only the surface you need (e.g. just VPS or just DNS)
Supports both stdio and HTTP streaming transports

Limitations

Only useful if you are already a Hostinger customer; tools map 1:1 to Hostinger services
Requires Node.js v24 or higher, which is newer than many default environments
Large unified surface (118 tools) can overwhelm agent context windows; you usually want a scoped binary

Alternatives

Cloudflare MCP server for DNS, domains, and edge infrastructure
DigitalOcean community MCP servers for VPS and droplet management
Namecheap or GoDaddy community MCP servers for domain registration workflows