Hostinger API MCP

What it does

This is Hostinger's official server for its public API. The unified command can reach 409 operations covering web hosting, Agency Plan sites, domains and DNS, VPS, mailboxes, WordPress, e-commerce, the Horizons builder, Reach email marketing, billing, the GPU catalog and agent-readiness scans of a website.

You don't get those operations as separate tools. An assistant sees three: search finds operations by keyword and returns their input schemas, execute calls one, and multi-execute runs up to 20 in a row where a later step can reuse a value from an earlier result. Search gives 5 matches unless you pass limit, which goes up to 20 (src/core/catalog.js). To keep it to one area, start a scoped command like hostinger-dns-mcp or hostinger-gpu-mcp. The GPU one only lists pools, instance types and OS templates for now.

The easiest start is the hosted endpoint at https://mcp.hostinger.com, which signs you in with OAuth. You can also install @hostinger/mcp from npm and run it on your own machine with an API token in HOSTINGER_API_TOKEN, or let it open a browser sign-in on the first call. The README now asks you to register Node and the script by absolute path in your client config instead of npx or the bare command name, so a project folder cannot put its own code in front. Locally there is also a Streamable HTTP mode on 127.0.0.1:8100, but it won't start without the token.

Some operations make more than one API call. The website deploy operations upload an archive and replace the site's current files. Domain setup turns on WHOIS privacy and the default nameservers unless you change them later. Reading the public changelog and roadmap needs no token.

What it needs

The README asks for Node.js 24 or newer, while package.json declares engines node >=20. Install the package globally, then run node -p process.execPath for the Node path and npm root -g for the folder that holds @hostinger/mcp, and put both absolute paths in the client config. Create an API token in the Hostinger panel and set HOSTINGER_API_TOKEN, or leave it unset in stdio mode and sign in through the browser (hostinger-api-mcp --login does this ahead of time). The --http mode needs the token. Claude Code connects to the hosted endpoint and opens the OAuth page itself.

Limits

• Limit Local --http mode exits at start without HOSTINGER_API_TOKEN, because OAuth sign-in only works over stdio.
• Size cap multi-execute takes at most 20 steps and stops at the first failed step.
• Size cap search returns 5 matches by default and at most 20 with limit.
• Not covered Scoped commands only search and run their own group's operations, for example hostinger-dns-mcp has 9.
• Limit The README advises a client config with absolute paths to Node and src/servers/all.js rather than the bare hostinger-api-mcp shown here.
• Limit Website deploy operations overwrite the site's existing files, and the README warns this cannot be undone.
• Limit Website deploys refuse local paths in the home directory itself, system folders, credential folders such as .ssh or .aws, and secret files.
• Limit Operations replaced by newer ones are hidden from search but still run through execute until they are removed.
• Limit API_TOKEN still works as an alias for HOSTINGER_API_TOKEN but is deprecated and due for removal.

Who it suits

Suits Hostinger customers who want an assistant to look up and change their own hosting, domains, DNS, VPS or mailboxes from one place. The hosted endpoint needs no install and signs in with OAuth, so it is the easy start for Claude Code. Run the npm package locally when you want a fixed API token for scripts or CI, or want to narrow the reach with a scoped command. Because execute and multi-execute can buy domains, deploy sites and change DNS, pick a scoped command or a token on a limited account if you only need reads. It does nothing for accounts at other hosting providers.