# Hostinger > 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. [Canonical HTML page](https://top-mcps.com/mcp/hostinger) · [server.json](https://top-mcps.com/mcp/hostinger.json) · [methodology](https://top-mcps.com/about/methodology) ## Install ### Claude Desktop — `claude_desktop_config.json` Paste under mcpServers. Fully quit and reopen Claude after editing. ```json { "mcpServers": { "hostinger": { "command": "npx", "args": [ "-y", "hostinger-api-mcp@latest" ], "env": { "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}" } } } } ``` ### Claude Code — `CLI or .mcp.json` Run from your repo. Commit .mcp.json to share with your team. ```shell # export HOSTINGER_API_TOKEN=your_hostinger_api_token claude mcp add hostinger -- npx -y hostinger-api-mcp@latest ``` ### Cursor — `.cursor/mcp.json` Global path: ~/.cursor/mcp.json. Reload window after editing. ```json { "mcpServers": { "hostinger": { "command": "npx", "args": [ "-y", "hostinger-api-mcp@latest" ], "env": { "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}" } } } } ``` ### VS Code — `.vscode/mcp.json` VS Code uses the "servers" key (not "mcpServers"). ```jsonc { "servers": { "hostinger": { "command": "npx", "args": [ "-y", "hostinger-api-mcp@latest" ], "env": { "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}" } } } } ``` ### Windsurf — `~/.codeium/windsurf/mcp_config.json` Open via Cascade → hammer icon → Configure. ```json { "mcpServers": { "hostinger": { "command": "npx", "args": [ "-y", "hostinger-api-mcp@latest" ], "env": { "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}" } } } } ``` ### Cline — `cline_mcp_settings.json` Open via the Cline sidebar → MCP Servers → Edit. ```json { "mcpServers": { "hostinger": { "command": "npx", "args": [ "-y", "hostinger-api-mcp@latest" ], "env": { "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}" } } } } ``` ### Continue — `~/.continue/config.json` Continue uses modelContextProtocolServers with a transport block. ```json { "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": [ "-y", "hostinger-api-mcp@latest" ], "env": { "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}" } } } ] } } ``` ### Codex CLI — `~/.codex/config.toml` Codex uses TOML. Each server is a [mcp_servers.] subtable. ```shell # ~/.codex/config.toml [mcp_servers.hostinger] command = "npx" args = [ "-y", "hostinger-api-mcp@latest", ] env = { HOSTINGER_API_TOKEN = "${HOSTINGER_API_TOKEN}" } ``` ### Zed — `~/.config/zed/settings.json` Zed calls them "context_servers". Settings live-reload on save. ```jsonc { "context_servers": { "hostinger": { "command": { "path": "npx", "args": [ "-y", "hostinger-api-mcp@latest" ] }, "env": { "HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}" } } } } ``` ### ChatGPT — `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. ```none ``` ## At a glance - **Maintainer:** Hostinger - **Transport:** stdio, Streamable HTTP - **Auth model:** OAuth 2.1 - **Required secrets:** HOSTINGER_API_TOKEN - **Supported clients:** Claude, Cursor, VS Code, Windsurf, Any MCP-compatible client, Hostinger accounts - **License:** MIT - **Language:** TypeScript - **Latest version:** latest - **Last verified:** 2026-09-29 - **GitHub stars:** 155 (fetched 2026-10-15T10:09:13.484Z) - **Score:** 82/100 (rubric 2026-09 — see https://top-mcps.com/about/methodology) - **Source:** https://github.com/hostinger/api-mcp-server - **Homepage:** https://developers.hostinger.com/ ## Tools & permissions | Tool | Description | Args | Side effects | |------|-------------|------|--------------| | `search` | Find API operations by keyword; returns each match with its operation name, input schema and readOnly / destructive flags. | `—` | read | | `execute` | Run 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-execute` | Run up to twenty operations in order, stopping at the first failure; a later step can reference an earlier result with `$steps..`. | `—` | 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. ## 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 - Deploying static, JS or PHP builds from an archive **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 - Agents that cannot follow a two-step search-then-execute pattern ## Description Hostinger's official MCP wraps their public API — domain search and registration, DNS zones with snapshots, shared and VPS hosting, WordPress, the Horizons site builder, email and billing — behind three tools since v2.0.0 (2026-09-28): `search` finds an operation by keyword, `execute` runs one, `multi-execute` chains up to twenty. 403 operations sit behind them. It is the rare server where "register a name, point it at a deploy, and publish a site" is one credential rather than three. ## Why it matters Most of this category is single-purpose: a registrar MCP or a hosting MCP. Hostinger is both, plus the site builder, so an agent can run the entire "from nothing to a live site" chain without switching credentials. The v2 redesign also fixed the one thing that made it hard to use: 396 tool definitions no longer land in the context window — three do, and the agent searches for the rest. ## Key features - Three tools — `search`, `execute`, `multi-execute` — over 403 API operations (v2.4.0, probed 2026-09-29) - Per-product entry points so you can install one slice - OAuth 2.0 + PKCE by default; `HOSTINGER_API_TOKEN` bypasses it for CI - stdio and HTTP transports (`--http`) - MIT, released almost daily ## FAQ ### What happened to the 396 tools? They became operations. v2.0.0 (2026-09-28) replaced the one-tool-per-endpoint surface with `search`, `execute` and `multi-execute`; `search` returns operations such as `domains_availability_check` or `hosting_deploy-static-website` with their input schemas, and `execute` runs them. Hostinger documents 403 operations behind the three tools. The per-product entry points (`hostinger-domains-mcp`, `hostinger-dns-mcp`, `hostinger-hosting-mcp`, …) still exist for installing one slice. ### Can it buy a domain? Yes — `domains_portfolio_purchase` (Purchase new domain) registers a name and bills the account, and `billing_orders_create-purchase` orders any catalog item on the default payment method. Search flags neither as read-only, and there is no dry run, so treat them as confirm-first operations. ### Can it publish a site my AI built? Yes. `hosting_deploy-static-website` uploads a static site from an archive with no build step, `hosting_deploy-js-application` builds and deploys a JavaScript app from a source archive, and `hosting_import-wordpress-website` imports a WordPress site from an archive plus a database dump. The Agency Plan variant's own description warns that a deploy overwrites the website's existing contents and cannot be undone, and says to confirm with the user first — treat the shared-hosting deploys the same way. ### API token or OAuth? Both. Without `HOSTINGER_API_TOKEN` the server runs OAuth 2.0 with PKCE and opens a browser on the first authenticated call. With the token set, OAuth is bypassed entirely — which is what you want in CI. `API_TOKEN` still works as a deprecated alias. ### Does it work for domains I hold elsewhere? No. Every operation acts on the Hostinger account behind the token. For a domain at another registrar you need that registrar's own server. ## Changelog - **2026-09-29** — 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. - **2026-09-28** — v2.0.0: the per-operation tool surface (396 tools on v1.61.0) replaced by search-and-execute. - **2026-09-16** — v1.61.0 released