What is Hostinger MCP?
Hostinger has launched an MCP (Model Context Protocol) server. This is the bridge that lets AI assistants like Claude Code actually *do* things in your account — like reading live domains, updating DNS records, or inspecting VPS resources — instead of just talking about it.
While graphical IDEs like VS Code and Cursor enjoy a simple one-click OAuth install process, Claude Code is entirely terminal-based. This means we need to connect it the manual way: copy a small JSON config, paste it into one file, and save. It is incredibly quick, taking less than three minutes to get fully connected. Let's do it!
Prerequisites
Before jumping into the setup, make sure your local environment is configured with these key dependencies:
Node.js 20 or Higher
Hostinger's MCP server runs locally on your machine using Node.js. You'll need version 20+ to run the connection. Verify your current version via command line.
Claude Code CLI
Anthropic's command-line agent must be installed globally. Note that CLI environments require a manual config, unlike the one-click OAuth flow in GUI editors.
node -vStep-by-Step Connection Setup
Follow these simple steps to configure your local Claude Code terminal environment:
Navigate to API Page in hPanel
Log in to your Hostinger hPanel, and in the sidebar under Dev tools, click on API. At the top of this page, you will see tabs for various IDE integrations (VS Code, Cursor, Antigravity, etc.).
Click the Claude Code tab. Then, select your current operating system (Mac, Windows, or Linux) so the system provides the correct configuration paths for your environment.
Select Only the Tools You Need
Under "Select MCP tools", you will see six checkboxes/product toggles:
- Websites
- Domains and DNS
- Subscriptions and payments
- Email Marketing
- VPS hosting
- Ecommerce
Generate API Token & Copy the Config
Generate your Hostinger API token directly on the page. When generated, Hostinger will automatically inject the token value into the JSON config snippet shown under Step 3, replacing the your-token-here placeholder.
Locate your global Claude configuration file. The file path depends on your operating system:
- Windows:
%USERPROFILE%\.claude.json - Mac / Linux:
~/.claude.json
Copy the generated JSON block from Hostinger and paste it into this file. If you already have existing MCP servers set up, merge the new hostinger-hosting object inside the mcpServers dictionary:
{
"mcpServers": {
"hostinger-hosting": {
"command": "npx.cmd",
"args": ["--package=hostinger-api-mcp@latest", "hostinger-hosting-mcp"],
"env": {
"HOSTINGER_API_TOKEN": "YOUR_ACTUAL_HOSTINGER_API_TOKEN_HERE"
}
}
}
}
*Note: For macOS and Linux, the command will be npx instead of npx.cmd.
Restart Claude Code and Verify
Restart your Claude Code CLI terminal session so it parses the new configuration parameters. Once restarted, run a quick prompt to verify the connection:
"List my Hostinger domains"If you enabled VPS hosting tools, you can also query:
"Show me the status of my VPS and its current resource usage"If the terminal prints your live account details, the connection is fully working!
Alternative: One-Line CLI Registration
If you would rather avoid opening and merging text files manually, you can instruct Claude Code to register Hostinger MCP in a single terminal line command:
claude mcp add hostinger -e HOSTINGER_API_TOKEN=YOUR_KEY -- npx -y hostinger-api-mcp@latest
This registers the MCP configuration server directly and produces the exact same setup. Make sure to swap YOUR_KEY with your real Hostinger API token.
Conclusion
Integrating Hostinger MCP into Claude Code removes the need to log into hPanel for simple adjustments. You can now manage hosting settings, review DNS structures, and run deployments in plain English.
In our next guide, we will look at how to deploy a full-stack Node.js application to a VPS without running a single manual terminal script. Stay tuned!
Discussion