Hostinger API MCP server

hostinger-api-mcp

Model Context Protocol (MCP) server for Hostinger API.

Quick start: Hosted remote server

If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server:

https://mcp.hostinger.com

Claude Code

claude mcp add --transport http hostinger https://mcp.hostinger.com

This opens a browser window to authorize via OAuth. Once approved, all tools below are available in your session.

Other MCP-compatible clients

Add https://mcp.hostinger.com as a remote Streamable HTTP MCP server in your client's configuration and complete the OAuth prompt when it appears. Refer to your client's docs for how it exposes "add remote MCP server" / "custom connector" settings.

Prerequisites

• Node.js version 24 or higher

If you don't have Node.js installed, you can download it from the official website. Alternatively, you can use a package manager like Homebrew (for macOS) or Chocolatey (for Windows) to install Node.js.

We recommend using NVM (Node Version Manager) to install and manage installed Node.js versions. After installing NVM, you can install Node.js with the following command:

nvm install v24
nvm use v24

Installation

To install the MCP server, run one of the following command, depending on your package manager:

# Install globally from npm
npm install -g @hostinger/mcp

# Or with yarn
yarn global add @hostinger/mcp

# Or with pnpm
pnpm add -g @hostinger/mcp

Update

To update the MCP server to the latest version, use one of the following commands, depending on your package manager:

# Update globally from npm
npm update -g @hostinger/mcp

# Or with yarn
yarn global upgrade @hostinger/mcp

# Or with pnpm
pnpm update -g @hostinger/mcp

Binaries

This package installs the following MCP server commands:

• hostinger-api-mcp — unified server with every tool (396 total)
• hostinger-agency-hosting-mcp — 38 tools for agency-hosting
• hostinger-billing-mcp — 9 tools for billing
• hostinger-dns-mcp — 8 tools for dns
• hostinger-domains-mcp — 41 tools for domains
• hostinger-ecommerce-mcp — 29 tools for ecommerce
• hostinger-horizons-mcp — 6 tools for horizons
• hostinger-hosting-mcp — 73 tools for hosting
• hostinger-mail-mcp — 38 tools for mail
• hostinger-reach-mcp — 52 tools for reach
• hostinger-vps-mcp — 64 tools for vps
• hostinger-wordpress-mcp — 38 tools for wordpress

Pick the binary that matches your agent's scope. hostinger-api-mcp remains the backwards-compatible default.

Configuration

The following environment variables can be configured when running the server:

• DEBUG: Enable debug logging (true/false) (default: false)
• HOSTINGERAPITOKEN: Your API token, which will be sent in the Authorization header. When set, OAuth is bypassed entirely.
• APITOKEN: Deprecated alias for HOSTINGERAPITOKEN. Will be removed in a future version — prefer HOSTINGERAPI_TOKEN.
• OAUTHISSUER: OAuth server base URL (default: https://auth.hostinger.com). Only used when HOSTINGERAPI_TOKEN is not set.

Authentication

The server supports two authentication methods:

API Token (recommended for CI/scripts)

Set HOSTINGERAPITOKEN in the environment or .env file. When present it always takes precedence — no OAuth code runs.

OAuth 2.0 with PKCE (interactive sign-in)

When HOSTINGERAPITOKEN is not set and the server runs in stdio mode, OAuth 2.0 with PKCE is used automatically on the first authenticated tool call:

Shortened. The full README is on GitHub.