hostinger-api-mcp

What is hostinger-api-mcp?

hostinger-api-mcp is a Model Context Protocol (MCP) server that exposes the Hostinger API as a set of tools. It enables AI assistants and automation scripts to manage Hostinger services—including billing, DNS, domains, hosting, VPS, e‑commerce, WordPress, and more—over stdio or HTTP transports.

How to use hostinger-api-mcp?

Install the package globally with npm install -g hostinger-api-mcp (or yarn/pnpm). Choose one of the provided binaries (e.g. hostinger-api-mcp for all 202 tools, or a focused binary like hostinger-dns-mcp). Configure authentication via the HOSTINGER_API_TOKEN environment variable or let OAuth 2.0 with PKCE handle sign‑in interactively. Then add the server to your MCP client’s JSON configuration (for example, in Claude or Cursor) and start calling tools.

Key features of hostinger-api-mcp

• 202 tools covering billing, DNS, domains, e‑commerce, horizons, hosting, reach, VPS, and WordPress
• Supports API token‑based (headless) and OAuth 2.0 with PKCE authentication
• OAuth credentials stored locally and shared across all Hostinger MCP binaries
• Two transport modes: stdio (default) and HTTP streaming (--http)
• Runs on Node.js 24 or higher; installable globally via npm, yarn, or pnpm

Use cases of hostinger-api-mcp

• Automate billing operations: view subscriptions, manage payment methods, toggle auto‑renewals
• Manage DNS zones: retrieve, update, delete, reset, and validate records; work with snapshots
• Administer domains: check availability, configure forwarding, manage domain locks
• Control web hosting and VPS resources: add/remove services via dedicated tools
• Supervise WordPress sites: deploy, configure, and manage WordPress installations programmatically

FAQ from hostinger-api-mcp

What authentication methods are supported?

The server supports two methods: an API token (set via HOSTINGER_API_TOKEN) for headless use, and OAuth 2.0 with PKCE for interactive sign‑in. When a token is set, OAuth is bypassed entirely.

Where are OAuth credentials stored?

On macOS/Linux: ~/.config/hostinger-mcp/credentials.json (mode 0600). On Windows: %APPDATA%\hostinger-mcp\credentials.json. Credentials are shared across all Hostinger MCP binaries.

What transport options are available?

The default transport is standard I/O (stdio). The server also supports HTTP streaming transport by passing the --http flag. When using HTTP, the HOSTINGER_API_TOKEN environment variable must be set (OAuth sign‑in is not supported in HTTP mode).

What are the runtime requirements?

Node.js version 24 or higher is required. The server can be installed globally via npm, yarn, or pnpm. Multiple ready‑to‑use binaries (e.g. hostinger-dns-mcp, hostinger-vps-mcp) are included.

Can I use hostinger-api-mcp in CI/scripting environments?

Yes. Set HOSTINGER_API_TOKEN in the environment and run the server without user interaction. OAuth is not required when the token is present, making it suitable for automated pipelines.