What it does

This server exposes the Hostinger API through 129 tools organized across seven specialized binaries—billing, DNS, domains, hosting, Reach (email and support), and VPS management. Callers choose the binary matching their scope or use the unified hostinger-api-mcp to access all tools. Authentication supports API tokens (recommended for scripts and CI) or OAuth 2.0 with PKCE for interactive sign-in; credentials are stored locally and refreshed automatically.

Who it's for

DevOps engineers and system administrators automating Hostinger infrastructure, hosting agencies provisioning and managing sites across multiple client accounts, and teams integrating Hostinger operations into Claude workflows for infrastructure-as-code or self-service platforms.

Common use cases

Query and scale VPS instances, snapshots, and backups
Automate DNS record updates and manage domain configurations
Retrieve billing data, invoices, and manage payment methods
Provision hosting accounts and configure databases
Inspect and manage email domains via the Reach API

Setup pitfalls

Requires Node.js 24 or higher; installation will fail on older versions
CI builds are currently failing—assess release stability and review recent commits before production use
OAuth credentials are stored at ~/.config/hostinger-mcp/credentials.json (Linux/macOS) or %APPDATA%\hostinger-mcp\credentials.json (Windows) with mode 0600; ensure read access
HTTP streaming transport does not support OAuth—set HOSTINGER_API_TOKEN before using --http