> For the complete documentation index, see [llms.txt](https://docs.hostinger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostinger.com/api-reference/tools.md).

# Tools & integrations

Every official way to automate Hostinger besides raw HTTP — the CLI, SDKs, Hostinger Connector and MCP servers, Terraform provider, Ansible collection, n8n node, WHMCS module, Postman collection, and

The [Hostinger API](/api-reference/overview.md) is the foundation for a set of official tools. Some are generated from the same OpenAPI specification and therefore cover every endpoint; others are hand-built for a specific platform and cover a focused slice of the API.

Pick by how you work: a terminal, an application, an infrastructure-as-code pipeline, a workflow builder, or an AI assistant. The [AI assistants](#ai-assistants-and-mcp) section also covers Hostinger's other MCP-based services, which don't use the API.

## Generated from the specification

These cover the whole API and pick up new endpoints automatically when the specification changes.

| Tool                                     | Install                                  | Use it for                                             |
| ---------------------------------------- | ---------------------------------------- | ------------------------------------------------------ |
| [Hostinger CLI](/api-reference/cli.md)   | `brew install hostinger/tap/hostinger`   | Terminal work, shell scripts, CI                       |
| [PHP SDK](/api-reference/sdks.md)        | `composer require hostinger/api-php-sdk` | PHP applications                                       |
| [Python SDK](/api-reference/sdks.md)     | `pip install hostinger-api`              | Python applications                                    |
| [TypeScript SDK](/api-reference/sdks.md) | `npm install @hostinger/sdk`             | Node and browser applications                          |
| MCP server                               | `npx @hostinger/mcp`                     | AI assistants — see [below](#hostinger-api-mcp-server) |

The [Email SDKs](/api-reference/email-sdks.md) are the equivalent set for the separate [Mail API](https://api.mail.hostinger.com), which reads and sends mail from your mailboxes.

## AI assistants and MCP

Hostinger offers four services based on the Model Context Protocol (MCP), each for a different job:

| Service                                                                               | What it's for                                                                                             | Runs on                         | Signs in with                                                         |
| ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------- | --------------------------------------------------------------------- |
| [**Hostinger API MCP server**](#hostinger-api-mcp-server)                             | Managing your Hostinger account: hosting, domains, DNS, mailboxes, VPS, and billing                       | Hostinger                       | Your Hostinger account or an API token                                |
| [**Mail MCP server**](/emails/agentic-mail.md#mcp-server)                             | Reading, searching, and sending mail from your mailboxes                                                  | Hostinger                       | A Mail API token                                                      |
| [**WordPress site MCP server**](/wordpress/hostinger-plugins/ai-plugin/mcp-server.md) | Managing what's inside one WordPress site: posts, pages, media, menus, and WooCommerce                    | Your WordPress site             | Hostinger Connector, an administrator account, or a site access token |
| [**Web2Agent**](https://www.hostinger.com/web2agent)                                  | Letting anyone's AI tools read and search your site. Read-only, though online stores can start a checkout | Hostinger, one address per site | None — the address is public                                          |

The easiest way to connect your own AI tools is [Hostinger Connector](/hostinger-connector/overview.md). It sets up the Hostinger API MCP server in your code editor, along with the WordPress site MCP server of each site that has the Hostinger AI plugin.

### Hostinger API MCP server

The [`@hostinger/mcp`](https://www.npmjs.com/package/@hostinger/mcp) package exposes the API as Model Context Protocol tools, so an AI assistant can manage your hosting, domains, DNS, VPS and billing directly.

Two ways to connect:

* **Hosted** — point your assistant at `https://mcp.hostinger.com`. Nothing to install; you sign in from the browser.
* **Local** — run `npx @hostinger/mcp` and authenticate with an API token or through the browser.

Source: [hostinger/api-mcp-server](https://github.com/hostinger/api-mcp-server).

## Infrastructure as code

Both tools below are focused on VPS provisioning rather than the whole API.

### Terraform

The [Hostinger Terraform provider](https://registry.terraform.io/providers/hostinger/hostinger/latest) manages VPS instances, SSH keys, post-install scripts and DNS zone records, with support for importing VPS instances you created elsewhere.

```hcl
terraform {
  required_providers {
    hostinger = {
      source  = "hostinger/hostinger"
      version = "0.1.23"
    }
  }
}
```

Requires Terraform 1.3 or later and an API token. Provisioning new servers also needs a payment method on the account. Source: [hostinger/terraform-provider-hostinger](https://github.com/hostinger/terraform-provider-hostinger).

### Ansible

The `hostinger.vps` collection provides modules for VPS power state, hostnames, firewalls, snapshots, SSH keys, post-install scripts, the malware scanner and metrics, plus a dynamic inventory plugin that discovers your VPS instances.

```bash
ansible-galaxy collection install hostinger.vps
```

Requires ansible-core 2.13 or later. Source: [hostinger/ansible-collection-hostinger](https://github.com/hostinger/ansible-collection-hostinger).

## Workflow automation

### n8n

The [`n8n-nodes-hostinger-api`](https://www.npmjs.com/package/n8n-nodes-hostinger-api) community node adds Hostinger as a step in [n8n](https://n8n.io) workflows — VPS management, domains, DNS, billing and Reach — so you can trigger Hostinger actions from any other service n8n connects to.

Install it through n8n's [community nodes](https://docs.n8n.io/integrations/community-nodes/installation/) screen. Source: [hostinger/api-n8n-node](https://github.com/hostinger/api-n8n-node).

### WHMCS

The [Hostinger WHMCS module](https://github.com/hostinger/api-whmcs-plugin) integrates VPS and Cloud services into a WHMCS billing system: automated provisioning, restarts and reinstalls, disk and bandwidth tracking, backups and snapshots, nameserver and PTR management, and a VPS control panel in the client area.

Requires WHMCS 8.0 or later, PHP 8.1 or later, and an API token.

## Postman

The [Hostinger public workspace](https://www.postman.com/hostinger-api) hosts a Postman collection covering the API, useful for exploring endpoints interactively before you write any code.

You can also work straight from the [endpoint pages](/api-reference/endpoints.md) in these docs — each one has a **Test it** panel that sends a real request from your browser.

## The OpenAPI specification

Everything above starts from one document: [`https://developers.hostinger.com/openapi/openapi.json`](https://developers.hostinger.com/openapi/openapi.json).

Fetch it directly if you want to generate a client for a language Hostinger doesn't publish, feed the API to a tool that consumes OpenAPI, or diff versions to see what changed.

***

*Last updated: October 9, 2026*