Skip to content
Hostinger API MCP Server

Hostinger API MCP Server

by Hostinger
Released
v1.27.0
MIT
Repository Docs npm
Cloud & Infrastructure

Summary

Hostinger's official MCP server, shipping 278 tools across VPS, hosting, domains, DNS, mail, WordPress and billing — split into per-domain binaries you can scope down.

Features

  • 278 tools covering VPS, hosting, domains, DNS, mail, WordPress, ecommerce and billing
  • Eleven per-domain binaries so you can expose a narrow tool surface
  • API-token auth for CI, or interactive OAuth 2.0 with PKCE for desktop use
  • Credentials stored locally at 0600 and shared across all Hostinger binaries
  • stdio and HTTP transports

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Hostinger API MCP Server" tools will be available.
{
  "mcpServers": {
    "hostinger-api-mcp": {
      "command": "hostinger-api-mcp",
      "env": {
        "DEBUG": "false",
        "HOSTINGER_API_TOKEN": "YOUR_API_TOKEN"
      }
    }
  }
}

Description

The Hostinger API MCP server puts a Hostinger account's full control surface behind MCP, so an agent can provision a VPS, edit DNS records, manage mailboxes or check billing without you clicking through hPanel.

Scope it by binary, not by trust

The unified hostinger-api-mcp binary exposes all 278 tools, but the package also installs eleven narrower servers so you can give an agent only the surface it needs: hostinger-vps-mcp (62 tools), hostinger-hosting-mcp (48), hostinger-mail-mcp (38), hostinger-wordpress-mcp (35), hostinger-agency-hosting-mcp (27), hostinger-domains-mcp (25), hostinger-ecommerce-mcp (12), hostinger-reach-mcp (12), hostinger-billing-mcp (9), hostinger-dns-mcp (8) and hostinger-horizons-mcp (2). Pointing a client at hostinger-dns-mcp is a far smaller blast radius than the default, and a much smaller tool list in the model's context.

Authentication

Set HOSTINGER_API_TOKEN for CI and scripted use — when present it takes precedence and no OAuth code runs. Otherwise, in stdio mode the server performs OAuth 2.0 with PKCE on the first authenticated call: it registers a dynamic client with the issuer once per machine, opens a browser, captures the redirect on a local ephemeral port and stores tokens at ~/.config/hostinger-mcp/credentials.json (mode 0600) or %APPDATA%\hostinger-mcp on Windows, refreshing them automatically. Credentials are shared across all the Hostinger binaries. --login and --logout drive the flow manually. OAuth is not available in --http transport mode, which requires the token.

Requirements

Node.js 24 or newer, installed globally via npm, yarn or pnpm. Published as hostinger-api-mcp under the MIT licence.

Related MCP Servers

MCP: WordPress Remote MCP

by Automattic

Automattic's official proxy that connects Claude, Cursor and other MCP clients to a WordPress site — posts, pages, media and WooCommerce — with OAuth 2.1, JWT or application-password auth.

Developer ToolsProductivity

MCP: Railway

by Railway

Railway's official MCP server, bundled with the Railway CLI — 40+ tools for projects, services, deployments, variables, domains and observability, with destructive actions gated behind explicit confirmation.

Cloud & Infrastructure
Browse all MCP servers →