What it does
This MCP server provides programmatic access to Hostinger's API, exposing 139 tools across domains, DNS, hosting, VPS, billing, ecommerce, and related services. It runs as a Node.js application and supports two transport modes: standard I/O (default) and HTTP streaming. Authentication is handled via API token (recommended for automation) or OAuth 2.0 with PKCE flow (for interactive use), with automatic token refresh and persistent credential storage.
Who it's for
DevOps engineers and automation teams managing Hostinger infrastructure at scale. Backend developers integrating Hostinger services into Claude-driven workflows. Site operators who need programmatic access to domain management, DNS configuration, and billing without leaving their AI chat context.
Common use cases
- Query domain registrations, DNS records, and zone configurations from Claude
- Provision and manage VPS instances programmatically
- Generate billing reports and service usage across multiple accounts
- Batch operations on domains (updates, transfers, renewals)
- Ecommerce and hosting configuration management
Setup pitfalls
- Requires Node.js 24 or higher; older versions will not work
- OAuth sign-in (browser flow) is not supported when using
--httptransport mode—setHOSTINGER_API_TOKENenvironment variable for automated or CI deployments - Credentials are stored locally (mode 0600) and shared across all Hostinger MCP binaries; ensure proper secret management on the host machine
- High risk class due to filesystem read/write access—sandbox or review before granting access to sensitive environments