How to Connect Hostinger to Microsoft Copilot via MCP

💡 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 + Microsoft Copilot

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.

1. 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.
2. Paste it into HOSTINGER_API_TOKEN. It is sent as a Bearer token.
3. Install the connector and run hostinger_list_subscriptions to 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 Microsoft Copilot

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 shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Hostinger tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

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

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse