Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

Hostinger MCP server (Hostinger Connector)

Hostinger's own MCP server for its whole account: deploy sites, edit DNS, manage email and VPS, through three search-and-run tools.

Reviewed by ReviewRamble editors · Updated

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

4.0/5

Hostinger's server reaches almost every corner of a hosting account and the three-tool redesign keeps it light, but it hands an agent live DNS, servers and billing with no read-only mode.

What is Hostinger MCP server (Hostinger Connector)?

The Hostinger MCP server gives an AI agent the Hostinger API: websites and hosting, domains and DNS, mailboxes, WordPress, online stores, email marketing, billing and VPS. It can deploy static sites, Node.js apps and PHP apps, import whole WordPress sites, connect domains and edit DNS records, and start, stop or rebuild virtual servers. It is MIT-licensed, written in TypeScript and published as the npm package @hostinger/mcp; Hostinger also runs it as a hosted server at https://mcp.hostinger.com with OAuth sign-in.

Since @hostinger/mcp 2.2.0 (28 September 2026) the server exposes only three tools, search, execute and multi-execute, instead of one tool per operation. The agent searches for the operation it needs, gets its input schema back, and runs it; multi-execute chains up to 20 operations and stops at the first failure. The README counts 423 operations behind the unified server, with 13 narrower binaries (DNS only, VPS only, WordPress only and so on) that expose the same three tools over one product area.

There are four ways in: the hosted URL from any MCP client, a local install, a Claude Code plugin that adds seven hosting skills (deploy, connect a domain, troubleshoot, migrate and others), and the Hostinger Connector extension for VS Code-based editors on Open VSX, which also registers the server for Claude Code and Codex. It is separate from the Hostinger Mail MCP server, which handles mailbox contents.

How to install Hostinger MCP server (Hostinger Connector)

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

Is Hostinger MCP server (Hostinger Connector) worth it?

The reason to install it is coverage. It reaches most of hPanel, from deployments and DNS snapshots to domain registration, WordPress imports, VPS firewalls and orders. The Claude Code plugin page lists it as Anthropic verified with 345 installs, the Open VSX extension shows 128,462 downloads, and the repository shipped eight releases on 19 and 20 November 2026 alone, reaching v4.15.0.

The three-tool interface is the sensible answer to an API this size. Loading hundreds of tool definitions into every session costs context; searching for the operation first keeps the visible list at three while the full set stays reachable. Hostinger's own pages disagree on the size of that set (372 tools in the Connector docs, 423 operations in the README), which suggests it changes quickly. Operations superseded by newer ones are hidden from search.

Risk deserves its own paragraph. An agent connected to this server can delete or reset DNS records, overwrite a live website (the deploy operations warn that this cannot be undone), stop or rebuild a VPS, delete databases and place orders. Whether the client asks before each call depends on its own settings, according to the Connector docs. The only ways to narrow access are the per-area binaries and the extension's product-area switches; no read-only mode or per-operation allow list is documented. Keep approvals on and use a scoped binary such as hostinger-dns-mcp when that is all the job needs.

The local install has a sharp edge that the README spells out. It tells you to register Node and the server script by absolute path rather than npx, because a cloned repository could otherwise run its own code with your Hostinger credentials. OAuth tokens are stored in ~/.config/hostinger-mcp/credentials.json with 0600 permissions; HTTP mode needs an API token, binds to 127.0.0.1:8100 by default and can be pointed at 0.0.0.0, which would expose the account to the network.

Where it earns its place

  • A freelance developer shipping client sites on a Hostinger Agency plan

    Deploy a built static site and point the client's domain at it

    Run `claude mcp add --transport http hostinger https://mcp.hostinger.com`, sign in once, and ask Claude Code to deploy the build folder and connect the domain; the deploy overwrites the site's current files, so confirm the target domain before approving. The server is free; the hosting plan is the cost.

  • An operations lead at a 10-person agency with 40 client domains

    Audit DNS records before a mail provider switch

    Install the DNS-only binary, hostinger-dns-mcp, with an API token so the agent can list records, check propagation and take a DNS snapshot, but cannot touch VPS or billing. Restore from the snapshot if a change goes wrong.

  • A backend developer running a side project on a Hostinger VPS

    Check server load and firewall rules without opening hPanel

    Install the Hostinger Connector extension in Cursor and enable only the VPS area; ask for metrics over the last 24 hours and proposed firewall changes, approving each call in the editor.

Before you commit

Setup
Hosted: `claude mcp add --transport http hostinger https://mcp.hostinger.com` and approve OAuth in the browser. Claude Code plugin: `/plugin install hostinger@claude-plugins-official`. Local: `npm install -g @hostinger/mcp` (Node.js 24+), then register the script by absolute path; `npx -y @hostinger/mcp` also works but the README warns against it.
Integrations
Any MCP client over Streamable HTTP or stdio; Claude Code plugin with seven hosting skills; Hostinger Connector extension for VS Code, Cursor, Windsurf, Antigravity and Devin Desktop that also configures Claude Code and Codex.
Data and privacy
Calls go to the Hostinger API under your account. OAuth credentials are stored locally in ~/.config/hostinger-mcp/credentials.json (mode 0600); the extension keeps an API token in the editor's encrypted storage but also writes it into the MCP config files it manages.
Cost at scale
The server costs nothing; spending comes from what the agent orders through the billing, domain and VPS purchase operations, so keep approvals on for those.
Limits
No published rate limits; multi-execute runs at most 20 operations and stops at the first failure; OAuth is not available in local HTTP mode, which needs HOSTINGER_API_TOKEN.

What’s good

  • Covers deployments, DNS, domains, email, WordPress, stores, billing and VPS
  • Three tools keep context small over 400-plus operations
  • Hosted endpoint with OAuth; nothing to install
  • Per-area binaries limit an agent to one product group
  • MIT-licensed and updated several times a day

What’s not

  • Can change live DNS, overwrite sites and rebuild servers
  • No read-only mode or per-operation allow list
  • Some operations spend money on your account
  • Tool and operation counts differ across Hostinger's own pages
  • npx install can run a project's code with your credentials, per the README

Best for

Developers and small agencies who host with Hostinger and want Claude Code, Cursor or Codex to deploy and manage sites and DNS from the editor.

Hostinger MCP server (Hostinger Connector) alternatives

Hostinger MCP server (Hostinger Connector): common questions

Is Hostinger MCP server (Hostinger Connector) worth it?
Hostinger's server reaches almost every corner of a hosting account and the three-tool redesign keeps it light, but it hands an agent live DNS, servers and billing with no read-only mode. We rate it 4.0 out of 5.
How much does Hostinger MCP server (Hostinger Connector) cost?
Free and open source (MIT). You pay for the Hostinger hosting, domains, VPS and email it manages, and some operations (domain registration, VPS and other purchases) spend money on your account.
What are the downsides of Hostinger MCP server (Hostinger Connector)?
Can change live DNS, overwrite sites and rebuild servers; no read-only mode or per-operation allow list; some operations spend money on your account; tool and operation counts differ across Hostinger's own pages; npx install can run a project's code with your credentials, per the README.
Who is Hostinger MCP server (Hostinger Connector) best for?
Developers and small agencies who host with Hostinger and want Claude Code, Cursor or Codex to deploy and manage sites and DNS from the editor.
How much does Hostinger MCP server (Hostinger Connector) cost for a team or in production?
The server costs nothing; spending comes from what the agent orders through the billing, domain and VPS purchase operations, so keep approvals on for those.
Is Hostinger MCP server (Hostinger Connector) safe for company data?
Calls go to the Hostinger API under your account. OAuth credentials are stored locally in ~/.config/hostinger-mcp/credentials.json (mode 0600); the extension keeps an API token in the editor's encrypted storage but also writes it into the MCP config files it manages.
What are the best Hostinger MCP server (Hostinger Connector) alternatives?
The closest alternatives we have reviewed are Hostinger Mail MCP server, Cloudflare MCP Server, Vercel MCP and Netlify MCP Server.

Answers checked Nov 20, 2026.

Make Hostinger MCP server (Hostinger Connector)? Show this rating on your siteHostinger MCP server (Hostinger Connector) rated 4.0 out of 5 on ReviewRamble