Connect Hostinger

Once Hostinger is connected, an agent can list the domains, websites and VPS instances on your account, read and change DNS records, restart or inspect a VPS, and look up subscriptions and invoices.

Before you start

• A Hostinger account with the products you want to manage. The connection covers everything the Hostinger API can reach on that account: hosting, domains and DNS, VPS, billing, Ecommerce and Hostinger Reach (email marketing).
• You must be a workspace owner or admin in woble. Only owners and admins can connect integrations.
• Agents treat DNS changes, VPS restarts, purchases and anything billed as irreversible: they show you exactly what will change and wait for a yes. They never delete a domain, record or server without one.

Connect it

1. Open Marketplace, Integrations tab, find Hostinger and press Connect.
2. Press Continue with Hostinger. A new tab opens at Hostinger's remote server, mcp.hostinger.com, and sends you to the Hostinger sign-in.
3. Sign in to your Hostinger account. Hostinger then asks you to authorize the connection; the single permission requested is mcp:use, which lets the connection call the Hostinger API on your behalf. Hostinger recommends this sign-in over a pasted API token, so there is nothing to generate or copy.
4. Approve. The tab closes and the card says Connected. The agent panel lists the new tools.

Or ask an agent

Type "@ruby connect Hostinger" in any chat. The same card appears there. Only owners or admins can complete it.

Try it

• "@atlas list the DNS records for example.com and tell me where the MX records point."
• "@atlas which of our VPS servers are running, and when does each subscription renew?"

If it does not connect

• The wrong products show up: you signed in to a different Hostinger account. Press Test connection in Marketplace, Connected, then Remove and reconnect with the right login.
• Calls fail with an authorization error: the grant was revoked from the Hostinger side or expired. Remove and reconnect.
• The Hostinger tab never returns: check that the browser did not block the pop-up, then start again from the card.

Disconnect

Marketplace, Connected, Remove. The tokens are deleted and agents lose the Hostinger tools immediately.

More in this category

• GitHubRepos, issues, pull requests, Actions and code search.
• LinearIssues, projects and cycles for product teams.
• Jira and ConfluenceAtlassian issues, boards and pages.
• SentrySearch, triage and analyse issues, traces and releases.
• SupabaseTables, SQL, migrations, edge functions and logs of your projects.
• Neon PostgresProjects, branches and SQL on serverless Postgres.