Hostinger MCP Server

Connect Hostinger to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Deploy and manage your websites directly from your IDE by connecting your Hostinger account. Handle websites, domains, DNS, VPS, ecommerce, email marketing, and. The hostinger mcp server is what makes that connection.

What the server does

We recommend using NVM (Node Version Manager) to install and manage installed Node.js versions. After installing NVM, you can install Node.js with the following command: bash nvm install v24 nvm use v24

Installation

The server ships on npm as hostinger-api-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• agencyHosting_deployNodeStaticWebsite — Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone —
• agencyHosting_deployPhpApplication — Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot
• billing_getCatalogItemListV1 — Prices in catalog items is displayed as cents (without floating point), e.g: float 17.99 is displayed as integer 1799
• billing_createPurchaseOrderV1 — This unified endpoint places an order for one or more catalog items and works across all Hostinger products, leveraging the existing billing
• billing_setDefaultPaymentMethodV1 — Use this endpoint to configure the primary payment method for future orders
• billing_deletePaymentMethodV1 — Use this endpoint to remove unused payment methods from user accounts
• billing_getPaymentMethodListV1 — Retrieve available payment methods that can be used for placing new orders
• billing_getSubscriptionListV1 — The billing_getSubscriptionListV1 tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: DEBUG, HOSTINGER_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js version 24 or higher If you don't have Node.js installed, you can download it from the official website. Alternatively, you can use a package manager like Homebrew (for macOS) or Chocolatey (for Windows) to install Node.js. We recommend using NVM (Node Version Manager) to

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Hostinger's toolset — agencyHosting_deployNodeStaticWebsite, agencyHosting_deployPhpApplication, billing_getCatalogItemListV1 and 5 more — is a fair guide to whether it matches your workflow.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.