Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Hostinger in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Manage a Hostinger account through its public API: VPS power, metrics, backups, snapshots, Docker projects and firewalls, domains, nameservers and DNS zones with snapshots, subscriptions and the price catalog, and web hosting websites, WordPress sites, databases and cache.
Try asking
Example prompts for Hostinger
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Hostinger, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Hostinger + Gemini
Manage a Hostinger account through its public API: VPS power, metrics, backups, snapshots, Docker projects and firewalls, domains, nameservers and DNS zones with snapshots, subscriptions and the price catalog, and web hosting websites, WordPress sites, databases and cache.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
HOSTINGER_API_TOKEN
Step 1 — Get credentials
Setting up takes about 2 minutes. You need a Hostinger account with access to hPanel.
- Sign in to hPanel and open Account, then API (https://hpanel.hostinger.com/profile/api), and create a new token. Pick an expiry; the token has the same rights as your hPanel user.
- Paste it into
HOSTINGER_API_TOKEN. It is sent as a Bearer token. - Install the connector and run
hostinger_list_subscriptionsto check the token.
Nothing here buys anything: ordering VPS plans or domains, changing payment methods and renewing subscriptions stay in hPanel.
VPS: the AI lists the machines and reads one in detail, with usage metrics (CPU, memory, disk, traffic and uptime) for a period. It can start, stop and restart a VPS and change its hostname; each of these answers with an action, which the AI follows until it succeeds or fails. While a VPS is busy with an action, a new one is refused. For recovery it lists and restores backups, and reads, takes or restores the single snapshot of a VPS. It also reads the root SSH keys, the OS templates and the data centers, and works with the projects of Hostinger's Docker manager: containers, the latest logs and a restart.
Firewalls: the AI lists firewalls, creates one, adds, changes and deletes rules, then syncs the firewall so the machines get the new rules, and activates or deactivates it on a VPS. A firewall drops everything no rule accepts, so the AI makes sure SSH (port 22) stays allowed before activating or syncing.
Domains and DNS: the domain portfolio with status, expiry, renewal, forwarding and WHOIS profiles, availability checks with suggestions, and nameserver changes. For domains on Hostinger nameservers the AI reads the zone, tests changes with hostinger_validate_dns_records, applies them, and deletes whole record sets. Every change leaves a snapshot, and restoring a snapshot undoes it. In a zone, name is relative to the domain (@ for the domain itself, www), CNAME and NS targets end with a dot, and MX content is the priority followed by the host.
Billing and web hosting: subscriptions, saved payment methods and the price catalog, read-only. On web and cloud hosting: hosting orders, websites, WordPress installations, MySQL databases, cron jobs, and clearing the cache of a website.
Confirm before writes: power changes, restores, snapshots, firewall, nameserver and DNS changes can take sites, email or SSH access offline. The AI names the machine or domain and the effect, shows the records or rules and waits for your yes. Restoring a backup or a snapshot overwrites all data on the VPS and cannot be undone.
Formats: VPS, action, backup, firewall and rule ids are integers. Times are ISO 8601 in UTC, and metrics are keyed by Unix timestamps. Prices are in cents of currency_code (1799 is 17.99). Memory, disk and bandwidth of a VPS are in MB. Domain contacts and WHOIS profiles hold personal data, and the AI shows only what the task needs.
Limits: about 90 requests a minute per token. On 429 the AI waits for Retry-After seconds, as repeated overruns can block the IP for a while. Paged lists return meta with current_page, per_page and total; VPS, domain, DNS and billing lists return everything at once.
Common errors: 401 means a wrong, revoked or expired token, 404 an id or domain that is not in this account, 422 invalid input (the answer names the field), and 409 or a locked action means the VPS is still busy with another action. Error answers carry a correlation_id for Hostinger support.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Gemini
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of
YOUR_MCP_API_KEY. - Save the file and restart
gemini. - Run
/mcpinside Gemini CLI (orgemini mcp listin your shell):anythingmcpshould show as connected. - Start prompting: Gemini CLI can now call the
Hostingertools.
Available tools
| Tool | What it does |
|---|---|
hostinger_list_virtual_machines | List every VPS (virtual machine) of the account: id, hostname, state (running, stopped, ...), plan, CPU count, memory and disk in MB… |
hostinger_get_virtual_machine | Read one VPS in detail: state, plan and resources, IP addresses, OS template, hostname, nameservers, data center, active firewall… |
hostinger_get_vm_metrics | Usage history of a VPS between two times: CPU, memory and disk usage, incoming and outgoing traffic, and uptime, as time series keyed by… |
hostinger_list_vm_actions | History of operations run on a VPS (start, stop, restart, backup restore, snapshot, OS change, ...), newest first, with name, state… |
hostinger_get_vm_action | Read one VPS action by id to see whether it is still running, succeeded or failed |
hostinger_start_vm | Power on a stopped VPS |
hostinger_stop_vm | Power off a VPS |
hostinger_restart_vm | Reboot a VPS (full stop and start; a stopped VPS is started) |
hostinger_set_vm_hostname | Change the hostname of a VPS |
hostinger_list_vm_backups | List the automatic backups of a VPS with their id, size, location and creation time |
hostinger_restore_vm_backup | Restore a VPS from one of its backups |
hostinger_get_vm_snapshot | Read the snapshot of a VPS (a VPS has at most one): id, creation time, expiry time and restore time |
hostinger_create_vm_snapshot | Take a snapshot of a VPS's current state |
hostinger_restore_vm_snapshot | Revert a VPS to its snapshot |
hostinger_list_vm_ssh_keys | List the SSH public keys of the root user on a VPS: key type, fingerprint data and comment name |
hostinger_list_vps_templates | List the OS templates a VPS can be installed with (Ubuntu, Debian, AlmaLinux, panels and app stacks): id, name and description |
hostinger_list_vps_data_centers | List Hostinger's VPS data centers: id, name, location code, city and continent |
hostinger_list_docker_projects | List the Docker Compose projects on a VPS that uses Hostinger's Docker manager: name, status, compose file path and containers with image… |
hostinger_get_docker_project_containers | List the containers of one Docker Compose project on a VPS with status, health, port mappings and CPU and memory stats |
hostinger_get_docker_project_logs | Read the latest log lines (up to 300 in total) of every service of a Docker Compose project on a VPS, grouped by service with timestamps |
hostinger_restart_docker_project | Restart all services of a Docker Compose project on a VPS (stop and start in dependency order; volumes are kept) |
hostinger_list_firewalls | List the VPS firewalls of the account: id, name, whether they are in sync with their machines, and their rules |
hostinger_get_firewall | Read one firewall with all its rules (protocol, port, source) and its sync state |
hostinger_create_firewall | Create an empty firewall |
hostinger_create_firewall_rule | Add an accept rule to a firewall |
hostinger_update_firewall_rule | Change a firewall rule |
hostinger_delete_firewall_rule | Delete a firewall rule |
hostinger_sync_firewall | Apply a firewall's current rules to every VPS it is activated on |
hostinger_activate_firewall | Activate a firewall on a VPS |
hostinger_deactivate_firewall | Deactivate a firewall on a VPS: all its ports are reachable again from everywhere |
hostinger_list_domains | List the domains in the account's portfolio: id, domain name, type (domain or free subdomain), status and creation and expiry dates |
hostinger_get_domain | Read one domain: status, nameservers, child nameservers, lock and privacy protection state, WHOIS contact profile ids and dates |
hostinger_get_domain_renewal | Read a domain's renewal information: status and current expiry date |
hostinger_check_domain_availability | Check whether a domain name is free to register in one or more TLDs |
hostinger_update_domain_nameservers | Point a domain to other nameservers (two to four) |
hostinger_get_domain_forwarding | Read the forwarding (redirect) of a domain: target URL, redirect type (301 or 302) and dates |
hostinger_list_whois_profiles | List the WHOIS contact profiles used to register domains: id, TLD, country, entity type and contact details |
hostinger_get_dns_records | Read the DNS zone of a domain managed by Hostinger nameservers: every record set with name, type, TTL and values |
hostinger_validate_dns_records | Check DNS record changes without applying them: answers success when hostinger_update_dns_records would accept them, or 422 with the… |
hostinger_update_dns_records | Add or change DNS records of a domain |
hostinger_delete_dns_records | Delete whole DNS record sets of a domain, selected by name and type |
hostinger_list_dns_snapshots | List the saved versions (snapshots) of a domain's DNS zone, taken before each change: id, reason and time |
hostinger_get_dns_snapshot | Read one DNS zone snapshot with all the records it contained, e.g. to compare with the current zone before restoring |
hostinger_restore_dns_snapshot | Restore a domain's DNS zone to a snapshot |
hostinger_list_subscriptions | List the account's subscriptions: id, name, status, billing period, currency, total and renewal price in cents, auto-renewal flag… |
hostinger_list_payment_methods | List the payment methods saved in the account: id, name, masked identifier, type, default, expired and suspended flags |
hostinger_get_catalog | List what can be ordered with prices: catalog items (VPS plans, domain TLDs, hosting, email) with their price items per billing period… |
hostinger_list_hosting_orders | List the web and cloud hosting orders (plans) the token can see, own and shared: order id, plan name, status, subscription id and creation… |
hostinger_list_websites | List the websites on web and cloud hosting: domain, hosting account user name, order id, root directory, whether it is enabled, and the… |
hostinger_list_wordpress_installations | List the WordPress installations on web and cloud hosting: id, user name, domain, title, URL, directory, admin login and email, and whether… |
hostinger_list_databases | List the MySQL databases of a hosting account: name, user, host and port, assigned domain, disk usage and size limit in MB, and dates |
hostinger_list_cron_jobs | List the cron jobs of a hosting account with their schedule and command |
hostinger_clear_website_cache | Clear the server-side cache of a website (and the Hostinger CDN cache when CDN is on), so updated content shows at once |
Example prompts
- "List my VPS machines with their state, plan and IP addresses."
- "How much CPU and memory did my VPS use over the last 7 days?"
- "Show the DNS records of example.com, then point the A record of www to 203.0.113.10 once I confirm."
- "Which of my domains expire in the next 60 days, and is auto-renewal on for them?"
- "Show the latest logs of the Docker project on my VPS and restart it if a container is unhealthy."
FAQ
Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Meta Muse
- Connect to Microsoft Copilot
Was this guide helpful?