The Hostinger MCP server connects a Hostinger hosting account to Claude and any MCP-compatible agent. Its 363 listed tools deploy websites, start and stop VPS instances, register and forward domains, edit DNS, run mailboxes and manage WordPress and ecommerce stores. Sign-in is OAuth 2.1 with a single scope.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
47 destructive tools with no documented confirmation step. Deleting a website, a VPS snapshot, DNS records or a payment method are all single calls. The gate is your client's approval prompt.
A token connected through the extension lands in every managed editor's config. Hostinger documents this explicitly; the OAuth route avoids it.
The local server needs Node.js 20+, and the Connector extension needs Node.js 18+.
OAuth sign-in must complete within three minutes, and on Windows closing the "Hostinger OAuth" terminal cancels it.
Some editors only read MCP config at startup — Cursor, Windsurf, Devin Desktop and Antigravity need a full quit and reopen, not a window reload.
We did not read tool schemas. The endpoint requires OAuth, so names and the count come from Anthropic's directory and behaviour from Hostinger's documentation. We exercised no tool.
Frequently asked questions
How many tools does the Hostinger MCP server have?
Anthropic's directory lists 363. Hostinger's own documentation says 372 across eleven product areas, and publishes a per-area breakdown: 63 for VPS, 58 for Websites, 49 for Email Marketing, 40 for Domains, then Agency Hosting, Mailboxes and WordPress at 38 each. Hostinger's count is the larger and more recent.
Can the Hostinger MCP server delete my websites or servers?
Yes. Of the 363 tool names Anthropic lists, 47 are delete, reset or cancel operations, including deleting a website, a VPS snapshot, DNS records and a payment method. There is no documented two-phase confirmation, so the safeguard is whatever approval prompt your client shows before a call runs.
Do I need the Hostinger Connector extension to use MCP?
No. The extension configures editors for you, but Hostinger documents manual configuration against the hosted remote server at mcp.hostinger.com with OAuth 2.1 and nothing to install. Hostinger calls the hosted route the better choice for most clients, with a local npm package as the alternative.
Where does the Hostinger Connector store my API token?
In the MCP configuration of every editor it manages, which Hostinger flags as worth knowing because it is not obvious. If you connect with a token rather than OAuth, that token is written to each editor's config file. Use the OAuth route if you would rather not have a token on disk.
Why are Hostinger tools missing from my AI assistant?
Usually the client needs a full restart rather than a reload. Hostinger documents that Cursor, Windsurf, Devin Desktop and Antigravity read MCP configuration only at startup, so quitting and reopening the whole editor is required. In VS Code with Copilot, reload the window and check Hostinger tools are enabled in the Tools menu.
Why does Hostinger OAuth sign-in keep failing?
The sign-in has a three-minute window. Hostinger documents that you must complete it within three minutes, and that on Windows the flow runs in a terminal named Hostinger OAuth which cancels the login if closed. If no browser opens, the sign-in link is printed in the editor terminal.
Live OAuth posture check against https://mcp.hostinger.com/ — HTTP 401 with a www-authenticate Bearer challenge, and RFC 9728 metadata at https://mcp.hostinger.com/.well-known/oauth-protected-resource returning the single scope mcp:use and https://auth.hostinger.com as the authorization server (2026-09-12) · retrieved 2026-09-12
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Hostinger Connector to work.
Connect Hostinger Connector once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.