topmcps
Browse MCPs
Hostinger

Hostinger

Official

Buy a domain, provision hosting, deploy a site, and set its DNS — one official server covering the whole chain, now through three search-and-execute tools.

Score 82(?)HostingerMIT155Verified Top MCPs for Domains →
InstallView on GitHub

Quick answer

What it does

Exposes the Hostinger API as operations the agent discovers with `search` and runs with `execute`: `domains_availability_check` and `domains_availability_suggest-names-from-description`, `domains_portfolio_purchase`, `domains_portfolio_update-nameservers`, `domains_forwarding_*`, `dns_records_list` / `dns_records_update` / `dns_records_validate`, `dns_snapshots_get` / `dns_snapshots_restore`, `hosting_deploy-static-website`, `hosting_deploy-js-application`, `hosting_import-wordpress-website`, `billing_orders_create-purchase`, plus VPS, WordPress and Agency Plan groups. Each search result carries the operation's input schema and `readOnly` / `destructive` flags.

Best for

  • End-to-end domain → DNS → deploy in one server
  • AI-assisted domain name suggestions from a project description
  • DNS zone snapshots and point-in-time restore
  • WordPress plugin, theme and core management

Not for

  • Accounts held at another registrar or host
  • Unattended runs with billing operations reachable — `billing_orders_create-purchase` and `domains_portfolio_purchase` spend money

Source: top-mcps.com/mcp/hostinger — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "hostinger": {
      "command": "npx",
      "args": [
        "-y",
        "hostinger-api-mcp@latest"
      ],
      "env": {
        "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export HOSTINGER_API_TOKEN=your_hostinger_api_token
claude mcp add hostinger -- npx -y hostinger-api-mcp@latest

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "hostinger": {
      "command": "npx",
      "args": [
        "-y",
        "hostinger-api-mcp@latest"
      ],
      "env": {
        "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "hostinger": {
      "command": "npx",
      "args": [
        "-y",
        "hostinger-api-mcp@latest"
      ],
      "env": {
        "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "hostinger": {
      "command": "npx",
      "args": [
        "-y",
        "hostinger-api-mcp@latest"
      ],
      "env": {
        "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "hostinger": {
      "command": "npx",
      "args": [
        "-y",
        "hostinger-api-mcp@latest"
      ],
      "env": {
        "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "hostinger-api-mcp@latest"
          ],
          "env": {
            "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.hostinger]
command = "npx"
args = [
  "-y",
  "hostinger-api-mcp@latest",
]
env = { HOSTINGER_API_TOKEN = "${HOSTINGER_API_TOKEN}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "hostinger": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "hostinger-api-mcp@latest"
        ]
      },
      "env": {
        "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Hostinger doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set HOSTINGER_API_TOKEN in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

ToolDescriptionArgsSide effects
searchFind API operations by keyword; returns each match with its operation name, input schema and readOnly / destructive flags.—Read
executeRun one operation found with search, e.g. `domains_availability_check`, `dns_records_update` or `hosting_deploy-static-website`. Writes and purchases go through here.—Write
multi-executeRun up to twenty operations in order, stopping at the first failure; a later step can reference an earlier result with `$steps.<i>.<path>`.—Write

Security & scope

Access scope
Read + write
Sandbox
No sandbox. Operations act on the live Hostinger account the token belongs to.
Gotchas
  • Purchases are one `execute` away: `domains_portfolio_purchase` registers a name and bills the account, and `billing_orders_create-purchase` orders any catalog item on the default payment method. Neither has a dry run. Keep both behind a confirmation, or install a scoped bin that excludes billing.
  • `dns_records_update` with `overwrite = true` replaces the whole zone and `dns_records_reset` wipes it. Take a snapshot first — `dns_snapshots_get` and `dns_snapshots_restore` exist for exactly this — and run `dns_records_validate` before applying.
  • OAuth sign-in is not supported in `--http` mode; set `HOSTINGER_API_TOKEN` before using it.
  • The three-tool design means a `tools/list` probe tells you nothing about what the account can do. Search results carry `readOnly` and `destructive` flags — that is where the capability information lives now.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. domains work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-domains
Compare Hostinger against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Hostinger MCP vs [Cloudflare MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/hostinger
- top-mcps.com listing for Cloudflare
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Hostinger MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/hostinger (fetch https://top-mcps.com/mcp/hostinger.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (HOSTINGER_API_TOKEN) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 3 updates tracked.

  1. v2.4.0 probed: three tools (search, execute, multi-execute) over 403 operations; `HOSTINGER_API_TOKEN` is the env var and `API_TOKEN` a deprecated alias; also published as @hostinger/mcp.

  2. v2.0.0: the per-operation tool surface (396 tools on v1.61.0) replaced by search-and-execute.

  3. v1.61.0 released

More Domains MCPs

Other tools in the same category worth evaluating.

Cloudflare
Official

Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.

cloudflare, edge, workers, dns
5 minMedium
Name.com
Official

Register, transfer and manage Name.com domains and DNS from an agent — the official server, sandboxed by default.

name-com, domains, registrar, dns
5 minLow
Porkbun

At-cost registration and full DNS control from an agent — read-only until you explicitly turn writes on.

porkbun, domains, registrar, dns
5 minLow

Compared with Hostinger

Side-by-side breakdowns for the choices people most often weigh against this MCP.

HostingervsCloudflareHostingervsName.comHostingervsVercel (MCP server)HostingervsDigitalOcean

Exploring Top MCPs for Domains? See all Domains MCPs →