hostinger
Installation
SKILL.md
[HOSTINGER]
Hostinger's estate is one API surface with three entry transports, and the work's shape chooses the transport, never habit. Maghz — the durable second brain — runs on the Hostinger VPS, so VPS mutations are production operations: snapshot before destructive work, and route lifecycle through the sanctioned transports below.
| [INDEX] | [TRANSPORT] | [SURFACE] | [WHEN] |
|---|---|---|---|
| [01] | hostinger MCP |
domains DNS VPS hosting ecommerce reach billing |
Interactive agent operations — the default |
| [02] | REST API | https://developers.hostinger.com with HOSTINGER_API_TOKEN |
Scripts, CI, bulk loops, SDK-driven automation |
| [03] | SSH | Universal key in ~/.ssh/config |
On-box work: deploys, logs, compose, migrations |
MCP tool names mirror the REST resources one-to-one (VPS_createSnapshotV1 is POST /api/vps/v1/virtual-machines/{id}/snapshot), so every REST row in the references reads as an MCP row and vice versa. REST authenticates with Authorization: Bearer $HOSTINGER_API_TOKEN; official SDKs (Python, TypeScript, PHP) and the hapi CLI wrap the same endpoints.