PageMotor on Hostinger with Claude Code

Hostinger has a native MCP server for Claude Code. Give it access to your account once, then tell it what you want. It provisions the VPS, sets the DNS record, and deploys PageMotor — without you leaving your editor.

1Go to the Hostinger API page

Log into hPanel and click API in the left sidebar (under Dev tools). You land on the page Hostinger have built specifically for AI coding tools.

3Generate your API token

Scroll down on the same page and click Generate API token. It creates a token instantly. Give it a name you will recognise, for example hostinger-cc-api.

4Copy the token before the page refreshes

The token appears once. Hostinger will not show it again if you refresh or leave the page. Copy it now.

Missed it? If you accidentally refreshed, delete the old token and click Generate again. Tokens are cheap, security is not.

5Copy the MCP JSON config

Scroll back up. The page shows a ready-made JSON block you copy straight into your Claude Code config. It looks like this:

Replace every your-token-here with the token you just copied. The full block, with your token in place, is what goes into Claude Code next.

Copy

"mcpServers": {
  "hostinger-hosting": {
    "command": "npx",
    "args": ["--package=hostinger-api-mcp@latest", "hostinger-hosting-mcp"],
    "env": { "HOSTINGER_API_TOKEN": "YOUR-TOKEN-HERE" }
  },
  "hostinger-domains": {
    "command": "npx",
    "args": ["--package=hostinger-api-mcp@latest", "hostinger-domains-mcp"],
    "env": { "HOSTINGER_API_TOKEN": "YOUR-TOKEN-HERE" }
  },
  "hostinger-dns": {
    "command": "npx",
    "args": ["--package=hostinger-api-mcp@latest", "hostinger-dns-mcp"],
    "env": { "HOSTINGER_API_TOKEN": "YOUR-TOKEN-HERE" }
  },
  "hostinger-vps": {
    "command": "npx",
    "args": ["--package=hostinger-api-mcp@latest", "hostinger-vps-mcp"],
    "env": { "HOSTINGER_API_TOKEN": "YOUR-TOKEN-HERE" }
  }
}

{
  "mcpServers": {
    /* paste the hostinger-hosting, hostinger-domains,  */
    /* hostinger-dns, and hostinger-vps blocks here     */
  }
}

POST /api/vps/v1/virtual-machines
{
  "item_id": "hostingercom-vps-kvm2-usd-1m",   // KVM 2, billed monthly
  "setup": {
    "template_id": 1096,               // Ubuntu 24.04 with CloudPanel
    "data_center_id": 18,             // Manchester, UK
    "hostname": "pagemotor-mysite",
    "public_key": "ssh-ed25519 ..."   // from ~/.ssh/id_ed25519.pub
  }
}

Migrating an existing site onto this VPS?

A fresh install can skip this section. If you are moving an existing PageMotor site here from another host, two things break silently on the way in. Both come from a real migration reported on the PageMotor developers forum, so this is field experience, not theory.

1. Apache protection does not follow you to nginx. PageMotor guards its sensitive directories (error logs, Skill state, and protected uploads including Brain files) with per-directory .htaccess files, which is automatic on Apache and LiteSpeed. CloudPanel serves your site with nginx, and nginx ignores .htaccess entirely. So the moment nginx starts serving a migrated site those directories are publicly readable over the web, and nothing looks broken. Current PageMotor releases probe for this themselves and raise an admin warning with the exact paths for your install. The fix is three rules. In CloudPanel open Sites → your site → Vhost, add these inside the server { } block, and save:

location ^~ /user-content/logs/              { deny all; }
location ^~ /user-content/skills/            { deny all; }
location ^~ /user-content/uploads/protected/ { deny all; }

Always edit the vhost through the CloudPanel page, not the file on disk: the panel regenerates that file, and panel edits are what survive. To confirm the rules are live, request https://yourdomain.com/user-content/logs/ in a browser. You want a 403, not a log file.

2. Zip extraction can strip the write bits. If you carry the site over as a zip and extract it on the server, directories can come out as 555 (read and execute, no write) depending on what built the zip. Ownership then looks perfect, every file belongs to the site user, but PHP cannot write anywhere, and the first symptom is usually a plugin install failing with “staging directory could not be created”. The scripted provision on this page sets the permission bits explicitly, so a from-scratch build never hits this; a hand-carried zip is the case it cannot see. The fix is one pass in a server terminal:

cd /home/SITEUSER/htdocs/yourdomain.com
chown -R SITEUSER:www-data .
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;

No Claude Code? There is still an AI path

This guide assumes Claude Code or Cursor, but the same job has been done end to end from plain browser chat at claude.ai, reported working on the forum. The recipe: connect your PageMotor site’s own MCP connector to the chat (the manual guide shows how), and when a step needs a real shell, open the browser terminal from your hPanel VPS overview, which is a root shell with no SSH keys to set up. You type the commands the AI gives you and paste the output back for it to read. Slower than the MCP setup on this page, where the two tools talk directly, but it reaches the same finish line: run EP Host Check at the end and look for green.

Who looks after this server?

You do. Hostinger sell a self-managed VPS, and say so plainly on their own VPS page: “As our VPS solutions are self-managed, you will get full freedom to configure and manage the virtual server.”

Hostinger looks after the hardware, the network, DDoS filtering at the edge, and whatever backups your plan includes. Everything from Ubuntu upwards is yours: security patches, your control panel, PHP, the database, your TLS certificate, and PageMotor itself.

That is not a catch. It is the same freedom that makes a VPS fix the problems shared hosting gives PageMotor. But nobody emails you when a patch is published, and a server left alone for a year is running a year of known, catalogued, publicly indexed vulnerabilities. Budget about fifteen minutes a month.