# hostinger-api-mcp [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/hostinger/api-mcp-server  
**GitHub Stars:** 163  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hostinger-api-mcp

## Description
MCP server for Hostinger API

## Tools
Capabilities this server exposes over MCP:

- **search** — find operations by keyword; returns each match with its `inputSchema`.
- **execute** — run one operation: `{ "operation": "<name>", "params": { ... } }`.
- **multi-execute** — run up to 20 operations in order, stopping at the first failure. A params value that is exactly `"$steps.<i>.<path>"` is replaced by that value from an earlier step's result.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "hostinger-api-mcp": {
    "command": "npx",
    "args": ["-y","@hostinger/mcp"],
    "env": {
      "DEBUG": "",
      "HOSTINGER_API_TOKEN": "",
      "API_TOKEN": "",
      "OAUTH_ISSUER": ""
    }
  }
}
```

**Requires environment variables:** `DEBUG`, `HOSTINGER_API_TOKEN`, `API_TOKEN`, `OAUTH_ISSUER` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What hostinger-api-mcp does

hostinger-api-mcp exposes Hostinger API functionality through the Model Context Protocol. Its unified binary covers 410 operations across areas including agency hosting, billing, DNS, domains, ecommerce, Horizons, hosting, mail, Reach, VPS, and WordPress. The server is useful when an MCP client or custom MCP application needs to discover Hostinger operations and invoke them without implementing each API endpoint as a separate client integration.

The npm package also installs scoped binaries for individual operation groups. These include agency hosting, agent readiness, billing, DNS, domains, ecommerce, Horizons, hosting, mail, Reach, VPS, and WordPress. Each binary provides the same MCP tool set while limiting searches and executions to its own group. The unified hostinger-api-mcp command remains the default covering all operations.

## How it works

The `search` tool accepts a keyword and returns matching operations with their `inputSchema`, allowing an agent to inspect the expected parameters before making a call. `execute` runs one named operation with a `params` object. `multi-execute` accepts up to 20 operations and processes them in order, stopping when one fails.

Multi-step calls can pass results forward. When a parameter is exactly formatted as `"$steps.<i>.<path>"`, the server substitutes the value found at that path in an earlier step's result. This supports workflows where one Hostinger API response supplies an identifier or other value needed by a later operation.

The server uses stdio by default and can also run with streamable HTTP. A hosted endpoint is available at `https://mcp.hostinger.com`, allowing compatible clients to connect without installing the package locally. Custom MCP consumers can connect over HTTP with the MCP SDK and call the exposed tools.

## Setup and configuration

Node.js 24 or newer is required for local installation. Install the package globally with npm, Yarn, or pnpm. The resulting `hostinger-api-mcp` command can be registered in an MCP client's configuration with its environment settings.

Authentication can use a Hostinger API token or interactive OAuth 2.0 with PKCE. Set `HOSTINGER_API_TOKEN` for CI, scripts, or other non-interactive use; it is sent in the authorization header and takes precedence over OAuth. Without that variable, stdio mode starts the OAuth flow on the first authenticated tool call, opens a browser for sign-in, and stores credentials for later use. `--login` starts that flow immediately, while `--logout` revokes stored credentials.

HTTP mode requires `HOSTINGER_API_TOKEN`; OAuth sign-in is not available in that mode. Run `hostinger-api-mcp --http` for HTTP on localhost port 8100, or provide custom values with `--host` and `--port`. `DEBUG` controls debug logging, and `OAUTH_ISSUER` changes the OAuth server base URL when token authentication is not configured. `API_TOKEN` remains available as a deprecated alias for `HOSTINGER_API_TOKEN`.

## Tools and capabilities

- `search`: Find operations by keyword and inspect each operation's input schema.
- `execute`: Invoke one named Hostinger operation with supplied parameters.
- `multi-execute`: Run up to 20 operations sequentially, with failure stopping the sequence and optional result references between steps.
- Unified coverage: Access the full operation set from one binary or use a scoped binary for a specific Hostinger service area.
- Transport choices: Connect through local stdio, streamable HTTP, or the hosted remote endpoint.

_Full upstream README: https://allmcps.com/mcp/hostinger-api-mcp/readme_