A production-grade Claude Code & OpenClaw skill for managing Hostinger infrastructure — VPS, websites, domains, DNS, email (Reach), and billing — through the official Hostinger MCP server, across one or many accounts, with a safety rule on every write.
This is not just a tool reference. It is an operational playbook for running Hostinger responsibly: category-scoped tool loading (so you never drown in 127 tools at once), VPS provisioning and lifecycle, domain/DNS changes, and money-spending guardrails — with write-confirmation on anything that changes state or costs money.
These are the free skills behind Aura — one AI web-agency lifecycle you can run standalone or orchestrate across a whole client fleet from a single dashboard.
| Stage | Skill | Role |
|---|---|---|
| 🎨 Build | siteagent-elementor-studio | Design & build sites inside Elementor |
| 🔎 Audit + Content | wordpress-api-pro | REST content ops, SEO & site audits |
| 🖥 Host | cloudways-mcp · hostinger-mcp ← you are here | Provision & operate the infrastructure |
→ Orchestrate all of it across your client fleet with Aura — governed agent ops with approvals and a full audit trail on top of these skills.
This skill works standalone — point it at your own Hostinger account and run it from Claude Code. That's the solo path: you drive one account, and the write-confirmation guardrail on anything that changes state or costs money keeps you safe.
The Aura path is the same skill orchestrated across a whole client fleet — Aura proxies these provider ops through its governed MCP gateway, adds queued human approvals and a full audit trail, and runs them across every VPS and site you manage from one dashboard, no per-account token juggling.
| Solo (this skill) | With Aura | |
|---|---|---|
| Scope | one account you hold keys for | every client account in your org |
| Approvals | your own write-confirmation | queued admin approval + audit trail |
| Best for | your own infra, quick ops | agencies operating many clients |
Use it solo for your own boxes; reach for Aura when you operate a fleet on clients' behalf.
- ✅ Official Hostinger MCP — the npm
hostinger-api-mcpserver (Node 24+), stdio or HTTP. - ✅ Category-binary loading — connect only
hostinger-vps-mcp/hostinger-dns-mcp/ … instead of all 127 tools; keep context lean. - ✅ Full tool catalog — 127 tools across VPS, hosting, domains, DNS, Reach, and billing, tagged R / W / W!.
- ✅ Write- and cost-confirmation safety — state-changing and money-spending operations require explicit, account-scoped confirmation; destructive ops double-confirm.
- ✅ Multi-account — one connection per account/token, each with its own prefix; no cross-account mixing.
- ✅ VPS playbook — provision, lifecycle, firewall, recreate/snapshots, projects.
.claude/skills/hostinger-mcp/
├── SKILL.md # core: category-binary loading, safety, multi-account, auth
└── references/
├── installation.md # npm install, token, 7 binaries, Claude config, multi-account
├── tools-catalog.md # all 127 tools, 6 categories / 7 binaries, R / W / W!
└── workflows-vps.md # flagship VPS playbook
The skill activates when Hostinger is discussed and a hostinger-* MCP server is connected (tools appear as mcp__hostinger*__*). For setup — see installation.md and .mcp.json.example. Install with npm i -g hostinger-api-mcp; authenticate with a HOSTINGER_API_TOKEN from hPanel.
- hostinger/api-mcp-server (official MCP server)
- Hostinger API docs
- Repository: https://github.com/Digitizers/hostinger-mcp
- OpenClaw: https://openclaw.ai
- Hostinger: https://www.hostinger.com/
- Digitizer: https://www.digitizer.studio
MIT
Built with ❤️ for OpenClaw by Digitizer