> For the complete documentation index, see [llms.txt](https://docs.hostinger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostinger.com/hostinger-connector/using-the-connector.md).

# Using the Connector

Once [installed and connected](/hostinger-connector/installation-and-setup.md), Hostinger Connector works through your AI assistant. This page covers choosing which products your assistant can access, how to use it in each editor, example prompts, and the full command reference.

## Choosing what your assistant can access

The Hostinger sidebar lists the available product groups with a checkbox for each. Only the products you enable are exposed to your AI assistant.

| Product group                | Enabled by default | What it covers                                                                      |
| ---------------------------- | ------------------ | ----------------------------------------------------------------------------------- |
| **Websites**                 | Yes                | Deployments (static, Node.js, WordPress), build logs, caching, databases, cron jobs |
| **Domains**                  | Yes                | Domain registration and management, plus DNS records and snapshots                  |
| **Subscriptions & Payments** | Yes                | Subscriptions, auto-renewal, payment methods                                        |
| **Email Marketing**          | Yes                | Hostinger Reach contacts, groups, and segments                                      |
| **Ecommerce**                | No                 | Stores, products, sales channels                                                    |
| **VPS**                      | No                 | Virtual machines, firewalls, SSH keys, snapshots, metrics                           |

Each product card shows a short description and the number of tools it provides. Toggle a checkbox and the change applies to your assistant right away (fork-based editors like Cursor may need a restart to pick it up).

Enabling only what you need keeps your assistant's tool list focused and reduces what it can act on.

> **Note:** Product selections reset to the defaults when you disconnect.

## Using it in your editor

| Editor                        | How to use                                                                                                      |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **VS Code (Copilot)**         | Open Copilot Chat, click the **Tools** button, and make sure Hostinger tools are enabled. Then prompt normally. |
| **Cursor**                    | Open chat (`Cmd+L` / `Ctrl+L`). Hostinger tools are available to the agent automatically.                       |
| **Windsurf**                  | Open Cascade. Hostinger tools appear in its tool list.                                                          |
| **Claude Code / Codex (CLI)** | The Connector writes their configuration automatically when you connect. Just run the CLI and prompt.           |

## Example prompts

**Websites & deployments**

* "Deploy this project to Hostinger as a static site"
* "Deploy my Node.js app to Hostinger"
* "Show the build logs for my latest deployment"
* "List all my websites and their status"
* "Clear the cache for mydomain.com"

**Domains & DNS**

* "Is mydomain.dev available? If so, how much does it cost?"
* "List all my Hostinger domains"
* "Add an A record for blog.mydomain.com pointing to 203.0.113.10"
* "Take a snapshot of my DNS zone before I make changes"

**VPS** (enable the VPS product first)

* "Show CPU and memory usage for my VPS"
* "Restart my VPS"
* "Add a firewall rule allowing port 8080"

**Billing**

* "Which of my subscriptions renew this month?"
* "Turn off auto-renewal for my VPS plan"

## How deployments work

Deployments are performed by your AI assistant calling Hostinger tools — there is no separate deploy button. Supported project types:

* **Static websites** — HTML/CSS/JS, or the built output of frameworks like React, Vue, or Astro. Deploys pre-built files only — no build step runs.
* **Node.js applications** — Express, Next.js, NestJS, and other Node.js apps. The uploaded archive is capped at **50 MB** and should exclude `node_modules` and build output — the build runs on Hostinger.
* **WordPress** — sites, plugins, and themes. Site imports take an archive plus a `.sql` dump and can run for several minutes.

When you ask your assistant to deploy, it selects the right tool, uploads your project through the Hostinger API, and reports the result — including build logs if a build is involved. For details on what happens on the hosting side, see [Node.js Hosting](/node.js/overview.md) and [Git](/websites/git.md).

## Command reference

All commands are available from the Command Palette (`Ctrl+Shift+P` / `Cmd+Shift+P`):

| Command                                 | Description                                                                              |
| --------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Hostinger: Set API Token (Optional)** | Connect using an API token instead of OAuth sign-in                                      |
| **Hostinger: Disconnect**               | Sign out, delete stored credentials, and remove all Hostinger MCP configuration          |
| **Hostinger: Refresh**                  | Refresh the sidebar status (also available as the refresh icon in the sidebar title bar) |

The extension adds no editor settings — everything is managed from the Hostinger sidebar.

## Where credentials are stored

* **OAuth:** tokens are stored by the Hostinger MCP server in `~/.config/hostinger-mcp/credentials.json` (macOS/Linux) or `%APPDATA%\hostinger-mcp\credentials.json` (Windows).
* **API token:** stored in your editor's encrypted secret storage and passed to MCP servers as the `HOSTINGER_API_TOKEN` environment variable.

Disconnecting removes both.

***

*Last updated: July 22, 2026*