# Hostinger MCP server

> Manage Hostinger VPS, domains, DNS, web hosting, email and billing through the Hostinger API from your assistant.

- Listing: https://mcp.tc/i/hostinger
- Connect: use the server's own URL `https://mcp.hostinger.com` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: Hostinger
- Homepage: <https://www.hostinger.com/support/11079316-hostinger-api-mcp-server/>
- Repository: <https://github.com/hostinger/api-mcp-server>
- Package: npm `@hostinger/mcp`

## About

Connects an assistant to the Hostinger API. The unified server covers about 400 operations across VPS, domains, DNS, web and agency hosting, WordPress, email, ecommerce, Reach and billing. Operations are found with a search tool and run through an execute tool.

The hosted endpoint at https://mcp.hostinger.com uses Streamable HTTP and OAuth sign-in in the browser. A local package, @hostinger/mcp, runs with npx on Node.js 24 or higher. It accepts a HOSTINGER\_API\_TOKEN, or falls back to interactive OAuth. Scoped binaries are available for single areas such as VPS, DNS or billing.

## What it can do

- Search Hostinger API operations by keyword
- Execute API operations with parameters
- Manage VPS instances
- Register and manage domains
- Edit DNS records
- Manage web hosting and WordPress sites
- Work with email and billing catalog data

## Example prompts

- "List my Hostinger VPS instances and their status."
- "Show the DNS records for my domain on Hostinger."
- "Find the Hostinger billing catalog items for domains."
- "Which Hostinger operations are available for WordPress hosting?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http hostinger https://mcp.hostinger.com
```

2. Start Claude Code, type `/mcp`, pick **hostinger** and choose **Authenticate**. A browser window opens for the Hostinger sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Hostinger** and paste this URL:

```url
https://mcp.hostinger.com
```

3. Click **Add**, then **Connect**, and sign in when Hostinger asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Hostinger&connectorUrl=https%3A%2F%2Fmcp.hostinger.com>) (opens connector settings)

2. Check that the URL reads `https://mcp.hostinger.com` and click **Add**.

3. Click **Connect** and sign in when Hostinger asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.hostinger.com` as the server URL and choose **OAuth**. ChatGPT sends you to Hostinger to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=hostinger&config=eyJ1cmwiOiJodHRwczovL21jcC5ob3N0aW5nZXIuY29tIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "hostinger": {
      "url": "https://mcp.hostinger.com"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=hostinger&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.hostinger.com%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"hostinger","type":"http","url":"https://mcp.hostinger.com"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "hostinger": {
      "type": "http",
      "url": "https://mcp.hostinger.com"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "hostinger": {
      "serverUrl": "https://mcp.hostinger.com"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add hostinger --url https://mcp.hostinger.com
codex mcp login hostinger
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.hostinger]
url = "https://mcp.hostinger.com"
```

### Gemini CLI

```bash
gemini mcp add --transport http hostinger https://mcp.hostinger.com
```

Then, inside Gemini CLI, run `/mcp auth hostinger` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "hostinger": {
      "type": "http",
      "url": "https://mcp.hostinger.com"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.hostinger.com`.

## Details

- Server version: 2.7.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/hostinger (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report