It covers the account rather than one product, so a DNS record, a VPS state and an email-marketing segment are all the same connection away. That breadth is also the thing to manage: the unified server carries hundreds of tools, and the per-product binaries exist precisely so an agent is not handed all of them. The hosted endpoint is the shortest path in — OAuth in a browser, no local process to keep alive.
Hostinger's own server over its developer API. There is a hosted endpoint at https://mcp.hostinger.com you reach over HTTP with OAuth, and an npm package if you would rather run it yourself; either way Hostinger's API endpoints arrive as callable tools.
- Websites, VPS, domains including DNS, email, email marketing, billing and ecommerce — each as its own set of tools
- Live reads and real changes: check a VPS, add or update a DNS record, deploy an archive to an Agency Plan site, list the contacts added this week
- A per-product binary for each area — DNS, domains, hosting, VPS, mail, reach, WordPress, ecommerce, agency hosting, billing — so a client that chokes on hundreds of tools gets only the ones for the job
- The unified binary when you want everything: 369 tools in one server
- WordPress sites exposed one by one rather than bundled, so an agent can be given a single site
A Hostinger account. The hosted endpoint authorizes over OAuth in the browser and needs nothing installed. Running it locally means Node.js 24 or newer and the npm package, which then takes either an API token from hPanel in HOSTINGER_API_TOKEN or an interactive OAuth sign-in on the first call — credentials are stored under your home directory and shared across all the Hostinger binaries. Over the local HTTP transport, OAuth is not available and the token is required. MIT.
One command plus a key — npm install -g hostinger-api-mcp, then supply credentials