Hostinger Connector
Deploy and manage your websites directly from your IDE by connecting your Hostinger account. Handle domains, website management, VPS, DNS, and billing in one place.
Supported IDEs
- VS Code 1.99 or later (with GitHub Copilot)
- Cursor
- Devin Desktop (ex-Windsurf)
- Antigravity (Google Gemini)
- Claude Code CLI
- OpenAI Codex CLI
What You Can Do
Once connected, your AI assistant (GitHub Copilot, Cursor AI, Devin, Gemini, Claude, Codex) gains access to your full Hostinger account through 100+ tools spanning websites, domains, VPS, email marketing, billing, and ecommerce.
Websites
- Deploy WordPress sites, plugins, and themes
- Deploy Node.js applications and static websites
- List deployments and retrieve build logs
- Manage hosting plans and SSH keys
Domains (includes 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
Email Marketing
- Create and manage contacts and contact groups
- Build contact segments with custom criteria
- Manage email marketing profiles
Subscriptions & Payments
- View subscriptions and enable/disable auto-renewal
- List payment methods
- Browse catalog and create service orders
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 online stores and product catalogs
- Access ecommerce-related tools and settings
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"
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)
- Click the Hostinger icon in the Activity Bar (left sidebar)
- Click Connect with Hostinger
- Complete sign-in in your browser when prompted
- The status badge turns green — you're connected!
The extension automatically registers Hostinger MCP servers for the current IDE, Claude Code CLI, and OpenAI Codex 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:
- Log in to hpanel.hostinger.com
- Open API in the left sidebar
- Click Generate new token, give it a name, and copy it
- 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)
- Open Copilot Chat (
Ctrl+Alt+I / Cmd+Alt+I)
- Click the 🔧 Tools button at the bottom of the chat input
- Confirm Hostinger is listed and enabled
- Ask anything about your Hostinger account
Cursor
- Open Cursor Chat (
Ctrl+L / Cmd+L)
- The Hostinger tools are available automatically once connected
- Ask anything about your Hostinger account
Devin Desktop (ex-Windsurf)
- Open the AI chat
- The Hostinger tools are available automatically once connected
- Ask anything about your Hostinger account
Antigravity
- Open the Agent panel
- The Hostinger tools are available automatically once connected
- Ask anything about your Hostinger account
Claude Code
- The MCP server is registered automatically when you connect via any IDE
- Start a Claude Code session and ask anything about your Hostinger account
OpenAI Codex
- The MCP server is registered automatically when you connect via any IDE (config written to
~/.codex/config.toml)
- Start a Codex session and ask anything about your Hostinger account
How It Works
This extension uses the Model Context Protocol (MCP), an open standard that lets AI assistants call external tools. When you connect:
- 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.
- 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.
- The extension registers MCP servers for the current IDE, Claude Code, and OpenAI Codex.
- The MCP server dynamically loads all available tools from the Hostinger OpenAPI spec.
- 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.
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-api-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 plus Claude Code and Codex (which are always configured as they are CLI tools without their own extension marketplace).
- 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 Devin Desktop (ex-Windsurf)
- Fully quit and reopen Devin Desktop
- 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/config/mcp_config.json
Tools not appearing in OpenAI Codex
- Start a new Codex session (MCP servers are loaded at session start)
- Check that the file exists:
cat ~/.codex/config.toml
- If
npx is slow on your connection, try adding --offline to the args after the package has been downloaded once
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.