# How to connect Hostinger to OpenClaw (paste one key, 24 tools) > Connect Hostinger to OpenClaw with ClawLink: paste your Hostinger key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/hostinger The usual route to Hostinger access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Hostinger setup: install one ClawHub skill, connect Hostinger in the browser, and OpenClaw can call real Hostinger actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/hostinger ## Setup It takes three steps to connect OpenClaw to Hostinger. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Hostinger** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect hostinger # connect Hostinger (browser OAuth) npx -y @useclawlink/cli actions hostinger # list available actions npx -y @useclawlink/cli run hostinger --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Hostinger in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Hostinger API key once. Verify the connection by asking OpenClaw: > Use Hostinger to check domain availability and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Hostinger is connected in the dashboard, that agent calls the same 24 Hostinger tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Hostinger MCP for OpenClaw Looking for a Hostinger MCP server for OpenClaw? ClawLink connects Hostinger to OpenClaw and exposes 24 Hostinger tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Hostinger integration](https://claw-link.dev/hermes/hostinger) works the same way. ## What the OpenClaw Hostinger integration can do 24 Hostinger tools are ready for OpenClaw once the account is connected. The 23 below are the ones people reach for most; your agent can call all 24. ### 23 of 24 Hostinger tools for OpenClaw | Tool | What it does | |---|---| | **Check domain availability** `hostinger_check_domain_availability` | Check if domain names are available for registration | | **Get dns records** `hostinger_get_dns_records` | Get DNS records for a domain | | **Get domain forwarding** `hostinger_get_domain_forwarding` | Get domain forwarding/redirect configuration | | **List data centers** `hostinger_list_data_centers` | List available data center locations | | **List dns snapshots** `hostinger_list_dns_snapshots` | List DNS backup snapshots for a domain | | **List domains** `hostinger_list_domains` | List all domains in your account | | **List orders** `hostinger_list_orders` | List hosting orders | | **List public keys** `hostinger_list_public_keys` | List SSH public keys | | **List subscriptions** `hostinger_list_subscriptions` | List account subscriptions | | **List templates** `hostinger_list_templates` | List available VPS OS templates | | **List virtual machines** `hostinger_list_virtual_machines` | List VPS virtual machines | | **List websites** `hostinger_list_websites` | List hosted websites | | **List whois profiles** `hostinger_list_whois_profiles` | List WHOIS contact profiles | | **Validate dns records** `hostinger_validate_dns_records` | Validate DNS records before updating | | **Verify domain ownership** `hostinger_verify_domain_ownership` | Verify domain ownership status | | **Get template details** `hostinger_get_template_details` | Get template details | | **Get whois profile** `hostinger_get_whois_profile` | Get WHOIS profile | | **Get whois profile usage** `hostinger_get_whois_profile_usage` | Retrieve domain list where provided WHOIS contact profile is used | | **List catalog items** `hostinger_list_catalog_items` | Get catalog item list | | **List payment methods** `hostinger_list_payment_methods` | Get payment method list | | **Create public key** `hostinger_create_public_key` | Create public key | | **Create whois profile** `hostinger_create_whois_profile` | Create a WHOIS contact profile for domain registration | | **Generate free subdomain** `hostinger_generate_free_subdomain` | Generate a free subdomain | ## Example prompts **Check Domain Availability** > Use Hostinger to check domain availability and walk me through the result in plain English. **Get Dns Records** > Pull the relevant data from Hostinger, summarize it in plain English, and point out anything that needs attention. **Get Domain Forwarding** > Pull the relevant data from Hostinger, summarize it in plain English, and point out anything that needs attention. **List Data Centers** > List the relevant items in Hostinger, group them by priority, and recommend what OpenClaw should do next. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Hostinger working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Hostinger API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hostinger account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Hostinger. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Hostinger actions to the runtime in a format your agent can reliably use. | 24 tools for Hostinger are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Hostinger to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Hostinger in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Hostinger key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Hostinger skill but can't call the tools The ClawHub skill teaches OpenClaw about Hostinger, but the calls run through the ClawLink plugin and your connected account. Make sure Hostinger is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Hostinger from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Hostinger tools Hostinger tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Hostinger call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Hostinger returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Hostinger has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Hostinger integration? Yes. ClawLink is the fastest way to connect OpenClaw to Hostinger: link your Hostinger account once in the browser and OpenClaw can call the Hostinger API through 24 ready-made tools — no custom code or token handling. ### How do I add Hostinger to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Hostinger skill from ClawHub, then you click Connect in the dashboard to authorize Hostinger. OpenClaw calls the tools from the next message — no config files, and the Hostinger key you paste is stored server-side instead of in your environment. ### How long does it take to connect Hostinger to OpenClaw? About two minutes. Sign in, click Connect next to Hostinger in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Hostinger up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Hostinger working from chat. ### OpenClaw installed the Hostinger skill but can't call the tools The ClawHub skill teaches OpenClaw about Hostinger, but the calls run through the ClawLink plugin and your connected account. Make sure Hostinger is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.