Hostinger
Web hosting and domain management platform with APIs for billing, domains, DNS, and VPS management
Verdict
Common use cases
- Check domain availability before client pitches
- Update DNS records during incident response
- Deploy VPS instances for staging environments
- Verify WHOIS profiles before domain registration
- Generate free subdomains for prototype demos
Integration
- Vendor
- Hostinger
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 24
- Composio slug
hostinger
Tools
- Check Domain Availability
Check domain availability. Verify if domain names are available for registration across multiple TLDs. Use this endpoint to check domain availability before purchase. Multiple TLDs can be checked at once. TLDs should be provided without lea
- Create VPS Public Key
Create public key. Add a new public key to your account for VPS SSH authentication. Use this endpoint to register SSH keys that can be used for authenticating to VPS instances. The public key will be associated with your account and can be
- Create WHOIS Profile
Create a WHOIS contact profile for domain registration. Use this endpoint to add new contact information that can be used when registering domains. The WHOIS profile is required for domain registration and contains contact details such as n
- Delete Public Keydestructive
Delete public key. Use this endpoint to remove unused SSH public keys from your account. Note: Deleting a public key from your account does not remove it from any virtual machines.
- Generate Free Subdomain
Generate a free subdomain. Create a unique free subdomain that can be used for hosting services without purchasing custom domains. Free subdomains allow you to start using hosting services immediately, and you can always connect a custom do
- Get DNS Records
Tool to retrieve DNS records for a domain. Use this endpoint to view current DNS configuration for domain management purposes. Example use cases: - Review current DNS settings before making changes - Check propagation status after DNS updat
- Get Domain Forwarding
Tool to retrieve domain forwarding configuration. Use when you need to view the current redirect settings for a domain, including the target URL and redirect type (301/302).
- Get VPS Template Details
Get template details. Retrieve detailed information about a specific OS template for virtual machines. Use this endpoint to view specific template specifications before deployment. Example use cases: - Review template details before VPS dep
- Get WHOIS Profile
Get WHOIS profile. Retrieve a WHOIS contact profile for domain registration contact information. Use this endpoint to view domain registration contact information including registrant, admin, and technical contacts.
- Get WHOIS Profile Usage
Tool to retrieve domain list where provided WHOIS contact profile is used. Use this endpoint to view which domains use specific contact profiles.
- List Catalog Items
Get catalog item list. Retrieve catalog items available for order. Use this endpoint to view available services and pricing before placing orders. Prices in catalog items are displayed as cents (without floating point), e.g., float 17.99 is
- List DNS Snapshots
Tool to retrieve DNS snapshots for a domain. Use when you need to view available DNS backup points for restoration or audit purposes.
- List Domains
Get domain list. Retrieve all domains associated with your account. Use this endpoint to view user's domain portfolio.
- List Hosting Orders
Tool to list hosting orders. Retrieve a paginated list of orders accessible to the authenticated client. This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with y
- List Payment Methods
Get payment method list. Retrieve available payment methods that can be used for placing new orders. Use this endpoint to view available payment options before creating orders. This action requires no request parameters. Note: To add a new
- List Public Keys
Get public keys. Retrieve public keys associated with your account. Use this endpoint to view available SSH keys for VPS authentication.
- List Subscriptions
Get subscription list. Retrieve a list of all subscriptions associated with your account. Use this endpoint to monitor active services and billing status.
- List Virtual Machines
Get virtual machines. Retrieve all available virtual machines. Use this endpoint to view available VPS instances. Returns a list of all virtual machines with their configuration details including CPU, memory, disk, IP addresses, and current
- List VPS Data Centers
Get data center list. Retrieve all available data centers. Use this endpoint to view location options before deploying VPS instances. Returns a list of all available data centers with their city, continent, country code, and name informatio
- List VPS Templates
Get templates. Retrieve available OS templates for virtual machines. Use this endpoint to view operating system options before creating or recreating VPS instances. Returns a list of all available templates with their ID, name, description,
- List Websites
List websites. Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client. This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have s
- List WHOIS Profiles
Retrieve WHOIS contact profiles for domain registration. Use this endpoint to view available contact profiles that can be used when registering domains. Optionally filter by TLD to get profiles applicable to specific domain extensions.
- Validate DNS Records
Validate DNS records. Validates DNS records prior to update for the selected domain. Use this endpoint to verify DNS record validity before applying changes. If the validation is successful, the response will contain 200 Success code. If th
- Verify Domain Ownership
Verify ownership of a single domain and return the verification status. Use this endpoint to check if a domain is accessible for you before using it for new websites. If the domain is accessible, the response will have `is_accessible: true`
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings → Integrations → Developer Tools. 2. Click 'Connect' next to Hostinger. 3. Log into your Hostinger account at hostinger.com and go to API settings (usually under Account → API or Developer Tools). 4. Generate a new API key — copy it immediately as Hostinger won't show it again. 5. Paste the key into Switchy's connection dialog and click 'Authorize'. 6. Switchy will verify the key by fetching your account details — this takes 5-10 seconds. 7. Once connected, open any Space and type '@Hostinger check if example.com is available' to test. 8. If the MCP responds with availability data, the connection works. 9. To invoke other tools, @mention Hostinger and describe the task (e.g. '@Hostinger show DNS records for mydomain.com'). 10. The MCP will confirm each action before making changes to your infrastructure.
What teammates see: by default, memories from Hostinger are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Domain Availability
@Hostinger check if acme-solutions.com, acme-solutions.io, and acme-solutions.dev are available for registration
Review DNS Configuration
@Hostinger show me all DNS records for staging.myapp.com so I can verify the CNAME is pointing to the right CDN
Deploy Test VPS
@Hostinger what Ubuntu templates are available for VPS deployment, and which one includes Docker pre-installed
Add SSH Key
@Hostinger create a new public key named 'ci-runner' with this key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC...
Generate Free Subdomain
@Hostinger generate a free subdomain for our hackathon project so we can deploy the prototype tonight
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@hostinger check if example-startup.com, example-startup.io, and example-startup.dev are available for registration
I checked domain availability across those three TLDs. **example-startup.com** is already registered. **example-startup.io** is available for $39.99/year. **example-startup.dev** is also available at $14.99/year. Both available domains support instant registration with your existing WHOIS profile. Would you like me to proceed with registering either of them?
This example shows the MCP's domain-search capability. Real availability and pricing fluctuate; you'll need a WHOIS contact profile created before registration. The MCP can check multiple TLDs in one call, useful for brand-name research.
@hostinger add an A record pointing staging.myapp.com to 203.0.113.42 with TTL 3600
I've created the A record for **staging.myapp.com** → **203.0.113.42** with a TTL of 3600 seconds (1 hour). DNS propagation typically takes 15–60 minutes globally. You can verify the change by running `dig staging.myapp.com` after a few minutes. The record is now live in Hostinger's DNS management console.
This demonstrates the MCP's DNS-write capability. It modifies live DNS records, so typos can break production traffic. Always double-check the IP and subdomain before confirming. The MCP requires API_KEY auth with DNS management scope.
@hostinger list all my VPS instances and summarize which ones are running Ubuntu 22.04 or newer, then show me available SSH keys for those servers
You have 3 VPS instances. Two are running **Ubuntu 22.04 LTS** (vps-prod-01, vps-staging-02), and one is on **Debian 11** (vps-legacy-03). For the Ubuntu servers, you have two SSH keys registered: **macbook-pro-2023** (RSA 4096) and **ci-deploy-key** (ED25519). Both keys are already authorized on vps-prod-01. vps-staging-02 has no keys attached yet—would you like me to add one?
This example pairs the MCP's VPS-listing and SSH-key tools with AI reasoning to filter and cross-reference data. Useful for auditing server configs before deployments. The MCP won't execute SSH commands directly—it only manages keys and metadata via Hostinger's API.
Use-case deep-dives
When Hostinger MCP beats manual domain config for solo devs
A solo developer shipping a weekend side project needs to register a domain, spin up a VPS, and wire DNS records—all from their terminal without context-switching to a web dashboard. The Hostinger MCP handles this in one conversation: check domain availability across TLDs, register the winner, create a free subdomain for staging, deploy a VPS with the right OS template, and set DNS A records pointing to the new IP. The 24-tool scope covers the full launch checklist. This wins when you're moving fast and the domain+hosting live in one vendor account. If your DNS is split across providers (Cloudflare for prod, Hostinger for dev), you'll still need manual steps. For a $20/month side project with everything at Hostinger, this MCP cuts launch day from 45 minutes of clicking to a 3-minute chat.
Hostinger MCP for batch domain setup across client accounts
A 6-person web agency onboards 4-8 new clients per month, each needing domain registration, WHOIS profile creation, and initial DNS config. The Hostinger MCP lets the ops lead script these steps in a shared Switchy workspace: check domain availability for the client's shortlist, create a WHOIS profile with their contact info, register the domain, and set up forwarding or DNS records for their existing site during migration. The SSH key tools (create/delete public key) support the dev team's VPS access without touching the Hostinger dashboard. This scales when your agency standardizes on Hostinger for client hosting. If clients bring their own registrars or you manage 50+ domains, the API key scope (one account) becomes a bottleneck—you'd need separate MCP instances per client or a custom integration. For agencies under 30 active domains, this MCP turns onboarding into a repeatable runbook.
When to use Hostinger MCP for quarterly VPS and DNS hygiene
A 10-person startup runs 12 VPS instances and 8 domains at Hostinger, accumulated over 18 months of pivots and experiments. The engineering lead uses the Hostinger MCP in a quarterly audit: list all VPS templates to confirm OS versions, retrieve DNS records for each domain to spot stale entries, delete unused SSH public keys from the account, and check if parked domain names are still worth renewing. The MCP surfaces this data in a Switchy thread where the team can discuss and act without logging into the Hostinger panel. This works when your infra lives in one Hostinger account and the audit is collaborative (not just the lead clicking around solo). If your stack spans AWS, Vercel, and Hostinger, you'll need multiple MCPs or manual cross-checks. For startups with <20 Hostinger resources, this MCP makes quarterly cleanup a 20-minute team exercise instead of a half-day chore.
Frequently asked
What does the Hostinger MCP let me do in Switchy?
It connects your Hostinger account so AI can check domain availability, manage DNS records, create VPS instances, and handle SSH keys — all without leaving the chat. You can ask questions like 'Is example.com available?' or 'Add an A record for my domain' and the MCP executes those operations directly against your Hostinger services.
Do I need admin access to connect Hostinger MCP?
You need a Hostinger API key with permissions matching what you want the AI to do. If you only want domain checks, a read-only key works. If you want the AI to create VPS instances or modify DNS, you need a key with write access to those resources. Generate the key in your Hostinger dashboard under API settings.
Can the Hostinger MCP deploy a full website for me?
No. It handles infrastructure tasks like domain registration, DNS configuration, and VPS provisioning, but it won't upload files or configure web servers. You still deploy code via FTP, SSH, or your CI/CD pipeline. Think of it as automating the Hostinger control panel, not replacing your deployment workflow.
How is this different from just using Hostinger's dashboard?
The MCP lets AI execute Hostinger operations mid-conversation, so you can ask 'Set up DNS for my new project' and it happens inline. The dashboard requires you to context-switch, navigate menus, and remember syntax. For one-off tasks the dashboard is fine; for workflows involving multiple services or repeated operations, the MCP is faster.
Who on my team should connect the Hostinger account?
Whoever manages your infrastructure or has the Hostinger credentials. The API key they connect determines what the AI can do, so if you want the team to provision VPS instances, that person needs admin-level access. If you only want domain checks, a junior dev with a restricted key is fine.