hostinger/api-mcp-server

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:
Claude Code
This opens a browser window to authorize via OAuth. Once approved, the operations below are reachable through execute 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:
Installation
To install the MCP server, run one of the following command, depending on your package manager:
Update
To update the MCP server to the latest version, use one of the following commands, depending on your package manager:
Binaries
This package installs the following MCP server commands:
- hostinger-api-mcp — unified server over every operation (421 total)
- hostinger-agency-hosting-mcp — 42 operations for agency-hosting
- hostinger-agent-readiness-mcp — 3 operations for agent-readiness
- hostinger-billing-mcp — 9 operations for billing
- hostinger-dns-mcp — 8 operations for dns
- hostinger-domains-mcp — 42 operations for domains
- hostinger-ecommerce-mcp — 29 operations for ecommerce
- hostinger-horizons-mcp — 6 operations for horizons
- hostinger-hosting-mcp — 81 operations for hosting
- hostinger-mail-mcp — 38 operations for mail
- hostinger-reach-mcp — 56 operations for reach
- hostinger-vps-mcp — 67 operations for vps
- hostinger-wordpress-mcp — 40 operations for wordpress
Every binary exposes the same three tools; a scoped binary only searches and executes its own group's operations. 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)
- HOSTINGER_API_TOKEN: Your API token, which will be sent in the Authorization header. When set, OAuth is bypassed entirely.
- API_TOKEN: Deprecated alias for HOSTINGER_API_TOKEN. Will be removed in a future version — prefer HOSTINGER_API_TOKEN.
- OAUTH_ISSUER: OAuth server base URL (default: https://auth.hostinger.com). Only used when HOSTINGER_API_TOKEN is not set.
Authentication
The server supports two authentication methods:
API Token (recommended for CI/scripts)
Set HOSTINGER_API_TOKEN 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 HOSTINGER_API_TOKEN is not set and the server runs in stdio mode, OAuth 2.0 with PKCE is used automatically on the first authenticated tool call:
1. A dynamic OAuth client is registered with the issuer (RFC 7591) — once per machine.
2. A browser window opens to the authorization page.
3. After sign-in, the server captures the redirect on a local ephemeral port, exchanges the code for tokens, and stores them.
4. Subsequent calls reuse the stored access token; expired tokens are refreshed automatically. If a refresh token is revoked, the browser flow is re-launched.
Credentials are stored at:
- macOS / Linux: ~/.config/hostinger-mcp/credentials.json (mode 0600)
- Windows: %APPDATA%\hostinger-mcp\credentials.json
Credentials are shared across all Hostinger MCP binaries (hostinger-api-mcp, hostinger-vps-mcp, etc.).
**Manual commands:**
**HTTP transport note:** OAuth sign-in is not supported in --http mode. Set HOSTINGER_API_TOKEN before using --http.
Usage
JSON configuration for Claude, Cursor, etc.
Transport Options
The MCP server supports two transport modes:
Standard I/O Transport
The server can use standard input / output (stdio) transport (default). This provides local streaming:
Streamable HTTP Transport
The server can use HTTP streaming transport. This provides bidirectional streaming over HTTP:
Command Line Options
Using as an MCP Tool Provider
This server implements the Model Context Protocol (MCP) and can be used with any MCP-compatible consumer.
Example of connecting to this server using HTTP streaming transport:
Tools
Every server exposes three tools:
- search — find operations by keyword; returns each match with its inputSchema.
- execute — run one operation: { "operation": " ", "params": { ... } }.
- multi-execute — run up to 20 operations in order, stopping at the first failure. A params value that is exactly "$steps. . " is replaced by that value from an earlier step's result.