For the complete documentation index, see llms.txt. This page is also available as Markdown.

Installation & Setup

Guide to installing the Hostinger Connector extension in VS Code, Cursor, or other editors and connecting your Hostinger account via OAuth or an API token.

This guide walks through installing the Hostinger Connector extension and connecting it to your Hostinger account.

Prerequisites

  • A supported editor — Visual Studio Code 1.99+, Cursor, Windsurf, Devin Desktop, or Antigravity

  • Node.js 18 or later installed on your machine (the Connector can install it for you — see below)

  • A Hostinger account

Step 1: Install the extension

  1. Open the Extensions panel in your editor (Ctrl+Shift+X / Cmd+Shift+X).

  2. Search for "Hostinger Connector".

  3. Click Install.

After installation, a Hostinger icon appears in the Activity Bar (the vertical bar on the side of your editor).

Step 2: Check Node.js

The Hostinger Connector runs Hostinger's MCP servers using Node.js, so Node.js 18+ is required. The sidebar shows your Node.js status automatically:

  • Node.js X.Y.Z ✓ — you're ready to connect.

  • Node.js Required (red banner) — Node.js is missing or older than 18. Click Install (or Update) in the banner and the Connector installs it for you using your system's package manager (Homebrew on macOS, winget or Chocolatey on Windows, apt/dnf/pacman on Linux). The sidebar updates automatically once installation finishes — no restart needed.

If automatic installation isn't possible, the Connector opens the Node.js download page so you can install it manually. After a manual install, restart your editor.

Step 3: Connect your Hostinger account

There are two ways to connect. OAuth sign-in is recommended for most users.

  1. Click the Hostinger icon in the Activity Bar.

  2. Click 1-Click Connect.

  3. Your browser opens the Hostinger sign-in page. Log in and approve the connection.

  4. Return to your editor — the sidebar status turns green: Connected (via OAuth).

Sign-in must be completed within 3 minutes. If the browser doesn't open automatically, the sign-in link is printed in the editor's terminal so you can open it manually.

Option B: API token (advanced)

Use an API token if you prefer explicit credentials, or if you're connecting in an environment where a browser sign-in isn't possible.

  1. In hPanel, go to the API page and click Generate new token. Copy the token.

  2. In the Hostinger sidebar, expand Advanced: Connect with API token.

  3. Paste your token and click Connect with API token.

Alternatively, open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run Hostinger: Set API Token (Optional).

Your token is stored in the editor's encrypted secret storage. Only one connection method can be active at a time — setting a token while signed in with OAuth signs you out of OAuth first.

Step 4: Restart if needed

  • Visual Studio Code: tools become available immediately (reload the window if you don't see them).

  • Cursor, Windsurf, Devin Desktop, Antigravity: fully quit and reopen the editor once after connecting, so it picks up the new MCP configuration.

Step 5: Try it out

Open your AI assistant's chat and ask something like:

List my Hostinger websites

If the assistant responds with your websites, you're all set. See Using the Connector for more examples and configuration options.

Disconnecting

To disconnect your account, either:

  • Click Disconnect in the Hostinger sidebar, or

  • Run Hostinger: Disconnect from the Command Palette.

This signs you out, deletes stored credentials, and removes the Hostinger MCP configuration from all managed editors and tools.

Tip: If you plan to uninstall the extension, disconnect first. Uninstalling without disconnecting can leave stale MCP configuration entries behind.


Last updated: July 21, 2026

Last updated

Was this helpful?