Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Hostinger ConnectorNew to Visual Studio Code? Get it now.
Hostinger Connector

Hostinger Connector

Hostinger Official

|
33,401 installs
| (2) | Free
Deploy, Monitor, and Manage Hostinger - Without Leaving Your Code
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Hostinger Connector

Deploy and manage your websites directly from your IDE by connecting your Hostinger account. Handle websites, domains, DNS, VPS, ecommerce, email marketing, and billing in one place.


Supported IDEs

  • VS Code 1.99 or later (with GitHub Copilot)
  • Cursor
  • Windsurf
  • Devin Desktop
  • Antigravity (Google Gemini)
  • Claude Code CLI
  • OpenAI Codex CLI

What You Can Do

Once connected, your AI assistant (GitHub Copilot, Cursor AI, Windsurf Cascade, Devin, Gemini, Claude, Codex) gains access to your full Hostinger account through 434 tools spanning websites, domains, DNS, VPS, WordPress, ecommerce, mailboxes, email marketing, Horizons, and billing.

Websites

  • Deploy Node.js applications and static websites
  • List deployments and retrieve build logs
  • Manage hosting plans and SSH keys
  • Install and manage WordPress sites, plugins, and themes
  • Manage WordPress users and settings

Agency Plan Websites

  • Provision new Agency Plan websites and check setup status
  • Deploy Node.js/static and PHP applications from an archive
  • Link, unlink, and change website domains
  • Manage databases and database users
  • Manage cron jobs, clear cache, and inspect running processes
  • Manage WordPress core versions and settings

WordPress Site

  • Create, delete and list Posts and Pages (with support for Elementor)
  • Create, delete and list WordPress Users
  • List and manage navigation menus
  • List and manage post revisions
  • Manage WordPress site options
  • Manage WooCommerce Orders and Products

Domains & DNS

  • Search and register new domains
  • Manage domain portfolio, locking, and forwarding
  • Check WHOIS information and domain verification
  • View, update, and delete DNS records
  • Manage DNS snapshots and restore previous configurations

VPS

  • List and manage virtual machines
  • Control power state (start, stop, restart)
  • Manage firewalls, SSH keys, and OS reinstalls
  • Access action history and metrics

Ecommerce

  • Manage ecommerce-related resources
  • Access store data and product information

Email Marketing

  • Create and manage contacts and contact groups
  • Build contact segments with custom criteria
  • Manage email marketing profiles

Mailboxes

  • Create and delete mailboxes and change their passwords
  • Manage aliases, forwarders, catch-alls, and autoreplies
  • Inspect inbound, outbound, access, and action logs
  • Manage API tokens and webhooks for the Mail API

Horizons

  • Create a Hostinger Horizons website from a prompt
  • Check the status of a Horizons website

Subscriptions & Payments

  • View subscriptions and enable/disable auto-renewal
  • List payment methods
  • Browse catalog and create service orders

Example prompts

"Deploy my Node.js app to Hostinger"
"List all my Hostinger domains"
"What VPS servers do I have and are they running?"
"Show me the DNS records for example.com"
"What Hostinger subscriptions are active on my account?"
"Register the domain example.com"
"Restart my VPS server"
"Show my ecommerce store products"
"Create a post in example.com about pinneaple pizza"

Requirements

  • One of the supported IDEs listed above
  • Node.js 18 or later
  • A Hostinger account

Installation

Search for "Hostinger Connector" in the Extensions panel and click Install.


Connecting (OAuth — recommended)

  1. Click the Hostinger icon in the Activity Bar (left sidebar)
  2. Click Connect with Hostinger
  3. Complete sign-in in your browser when prompted
  4. The status badge turns green — you're connected!

The extension automatically registers the Hostinger MCP server for the current IDE and Claude Code CLI when you connect. OAuth credentials are stored by the MCP server in your user config directory (~/.config/hostinger-mcp/credentials.json on macOS/Linux).


Optional: API token (advanced)

If you prefer a manual API token (for example CI-style workflows), expand Advanced: use API token instead in the sidebar:

  1. Log in to hpanel.hostinger.com
  2. Open API in the left sidebar
  3. Click Generate new token, give it a name, and copy it
  4. Paste the token in the sidebar and click Connect with API token

You can also use the command palette: Hostinger: Set API Token (Optional).

Keep your token secure — it grants access to your Hostinger account data.


Managing your connection

Action How
Disconnect Click Disconnect in the sidebar (revokes OAuth session or clears API token)
Switch to API token Disconnect, then use the advanced API token path
Switch to OAuth Disconnect, then click Connect with Hostinger

Connection changes take effect immediately. Disconnecting removes the MCP server registration for the current IDE.


Using the Extension

VS Code (GitHub Copilot)

  1. Open Copilot Chat (Ctrl+Alt+I / Cmd+Alt+I)
  2. Click the 🔧 Tools button at the bottom of the chat input
  3. Confirm Hostinger is listed and enabled
  4. Ask anything about your Hostinger account

Cursor

  1. Open Cursor Chat (Ctrl+L / Cmd+L)
  2. The Hostinger tools are available automatically once connected
  3. Ask anything about your Hostinger account

Windsurf

  1. Open Cascade chat
  2. The Hostinger tools are available automatically once connected
  3. Ask anything about your Hostinger account

Devin Desktop

  1. Open Devin chat
  2. The Hostinger tools are available automatically once connected
  3. Ask anything about your Hostinger account

Antigravity

  1. Open the Agent panel
  2. The Hostinger tools are available automatically once connected
  3. Ask anything about your Hostinger account

Claude Code

  1. The MCP server is registered automatically when you connect
  2. Start a Claude Code session and ask anything about your Hostinger account

OpenAI Codex

  1. The MCP server is registered automatically when you connect
  2. Start a Codex session and ask anything about your Hostinger account

Skills

While you're connected with Websites enabled, the extension also gives your IDE's agent seven web hosting skills — step-by-step playbooks it follows for bigger jobs. Invoke one by typing / and its name in chat, or just describe the task:

Skill What it does
troubleshoot-website Finds why a site is down, slow, erroring or failing to build, and fixes it
connect-domain Connects a domain end to end — DNS without losing email records, SSL, HTTPS redirect
deploy-to-hosting Deploys a project the right way; Git auto-deploy, environment variables, databases
maintain-wordpress Checks WordPress sites for updates and vulnerabilities and updates them safely
audit-hosting Reviews the whole hosting account and returns a prioritised to-do list
migrate-to-hosting Moves a site from another host, testing it before DNS changes
hostinger-headless Builds a new site from a prompt

Where they go:

IDE Location
Cursor Registered through Cursor's plugin API — nothing is written to disk
VS Code (GitHub Copilot) ~/.copilot/skills/
Windsurf, Devin Desktop ~/.codeium/windsurf/skills/
Antigravity ~/.gemini/antigravity/skills/

The extension never overwrites a skill folder with the same name that you created yourself, and it removes the skills it added when you disconnect or turn Websites off. If you also use the Hostinger Connector plugin for Cursor, the skills appear twice — keep one of the two.

The skills come from hostinger/api-mcp-server and are bundled with each release (npm run sync-skills).


How It Works

This extension uses the Model Context Protocol (MCP), an open standard that lets AI assistants call external tools. When you connect:

  1. OAuth (default): The extension runs the MCP server's browser sign-in flow and registers MCP servers without passing a token in environment variables. The MCP server stores and refreshes OAuth credentials locally.
  2. API token (optional): Your token is stored in your IDE's encrypted SecretStorage and passed to MCP servers via HOSTINGER_API_TOKEN in each IDE's config.
  3. The extension registers MCP servers for the current IDE, Claude Code, and Codex.
  4. The MCP server dynamically loads all available tools from the Hostinger OpenAPI spec.
  5. Your AI assistant can call Hostinger API tools on your behalf.

The MCP server fetches the latest OpenAPI spec from Hostinger on startup, so you always have access to the newest API endpoints without updating the extension.


Using Hostinger MCP without this extension

Any MCP-compatible client can reach the same 434 tools without installing the extension.

Hosted remote server

Point your client at Hostinger's hosted endpoint. It uses OAuth 2.1, so there is nothing to install and no token to manage:

https://mcp.hostinger.com

Local server

Run the official @hostinger/mcp package over stdio:

npx -y @hostinger/mcp

The package also ships a server per product area, so you can load only the tools you need instead of all 434:

Command Tools
hostinger-api-mcp 434 — every product area
hostinger-hosting-mcp 88
hostinger-vps-mcp 67
hostinger-reach-mcp 62
hostinger-domains-mcp 42
hostinger-agency-hosting-mcp 42
hostinger-mail-mcp 38
hostinger-wordpress-mcp 40
hostinger-ecommerce-mcp 29
hostinger-billing-mcp 9
hostinger-dns-mcp 8
hostinger-horizons-mcp 6

Security

  • OAuth: Credentials live in the MCP server's config file (~/.config/hostinger-mcp/ or %APPDATA%\hostinger-mcp\ on Windows), managed by the official @hostinger/mcp package.
  • API token: Stored in your IDE's OS-level encrypted SecretStorage (Keychain on macOS, Credential Manager on Windows, Secret Service on Linux) and only injected when you use the optional token path.
  • MCP server registration is scoped to the current IDE — installing in one IDE does not modify other IDEs' configurations.
  • Disconnecting removes MCP server entries and revokes OAuth or clears the stored API token.

Troubleshooting

Browser sign-in did not open

  • Complete sign-in manually if the MCP process prints an authorize URL in the terminal output.
  • Ensure Node.js 18+ is installed: node --version

Tools not appearing in Copilot Chat

  • Make sure you're on VS Code 1.99 or later
  • Try reloading the window: Cmd+Shift+P → Reload Window
  • Disconnect and reconnect from the sidebar

Tools not appearing in Cursor

  • Fully quit and reopen Cursor — it reads ~/.cursor/mcp.json at startup
  • Check that the file exists: cat ~/.cursor/mcp.json

Tools not appearing in Windsurf / Devin Desktop

  • Fully quit and reopen the IDE
  • Check that the file exists: cat ~/.codeium/windsurf/mcp_config.json

Tools not appearing in Antigravity

  • Fully quit and reopen Antigravity
  • Check that the file exists: cat ~/.gemini/antigravity/mcp_config.json

Authentication errors from the MCP server

  • Open the Hostinger sidebar and click Disconnect, then Connect with Hostinger again
  • If using an API token, regenerate it in hPanel and reconnect via the advanced path

"node" not found error

  • Ensure Node.js 18+ is installed: node --version
  • If using nvm, make sure your shell sources nvm in non-interactive mode
  • Restart your IDE after installing Node

Before uninstalling

  • Click Disconnect in the sidebar first to clean up MCP configuration files

License

This project is licensed under the MIT License. See the LICENSE file for details. The use of this extension service is subject to Hostinger's Terms of Service.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft