Hostinger
MCP server by Hostinger
Manage Hostinger VPS, domains, DNS, web hosting, email and billing through the Hostinger API from your assistant.
Connect to Hostinger
Hostinger needs sign-in. Connect with its own URL:
Your client opens Hostinger’s sign-in the first time you use it. The token stays between your client and Hostinger.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/hostingerAbout
Connects an assistant to the Hostinger API. The unified server covers about 400 operations across VPS, domains, DNS, web and agency hosting, WordPress, email, ecommerce, Reach and billing. Operations are found with a search tool and run through an execute tool.
The hosted endpoint at https://mcp.hostinger.com uses Streamable HTTP and OAuth sign-in in the browser. A local package, @hostinger/mcp, runs with npx on Node.js 24 or higher. It accepts a HOSTINGER_API_TOKEN, or falls back to interactive OAuth. Scoped binaries are available for single areas such as VPS, DNS or billing.
What you can do
- Search Hostinger API operations by keyword
- Execute API operations with parameters
- Manage VPS instances
- Register and manage domains
- Edit DNS records
- Manage web hosting and WordPress sites
- Work with email and billing catalog data
Tools
Hostinger lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.
Example prompts
List my Hostinger VPS instances and their status.
Show the DNS records for my domain on Hostinger.
Find the Hostinger billing catalog items for domains.
Which Hostinger operations are available for WordPress hosting?
Set up
Every client connects to mcp.hostinger.com, and Hostinger asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http hostinger https://mcp.hostinger.com- Start Claude Code, type
/mcp, pick hostinger and choose Authenticate. A browser window opens for the Hostinger sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it Hostinger and paste this URL:
https://mcp.hostinger.com- Click Add, then Connect, and sign in when Hostinger asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://mcp.hostinger.comand click Add. - Click Connect and sign in when Hostinger asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://mcp.hostinger.comas the server URL and choose OAuth. ChatGPT sends you to Hostinger to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"hostinger": {
"url": "https://mcp.hostinger.com"
}
}
}Cursor shows Needs login next to the server. Click it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"hostinger","type":"http","url":"https://mcp.hostinger.com"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"hostinger": {
"type": "http",
"url": "https://mcp.hostinger.com"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"hostinger": {
"serverUrl": "https://mcp.hostinger.com"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add hostinger --url https://mcp.hostinger.com
codex mcp login hostingerOr edit ~/.codex/config.toml directly:
[mcp_servers.hostinger]
url = "https://mcp.hostinger.com"Gemini CLI
gemini mcp add --transport http hostinger https://mcp.hostinger.comThen, inside Gemini CLI, run /mcp auth hostinger to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"hostinger": {
"type": "http",
"url": "https://mcp.hostinger.com"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.hostinger.com.
FAQ
Can I paste mcp.tc/i/hostinger into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://mcp.hostinger.com, so your client talks to Hostinger directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Hostinger need an API key or a sign-in?
Yes, you need a Hostinger account. The first time your client connects, it opens Hostinger’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is Hostinger a remote or a local server?
Remote. Hostinger hosts it at https://mcp.hostinger.com, and it speaks Streamable HTTP. There’s nothing to install.
What can Hostinger do?
You can search Hostinger API operations by keyword, execute API operations with parameters and manage VPS instances.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc’s robot read Hostinger’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Embed
Show Hostinger in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
README badge
[](https://mcp.tc/i/hostinger)<a href="https://mcp.tc/i/hostinger"><img src="https://mcp.tc/i/hostinger/badge.svg" alt="Hostinger on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/hostinger.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/hostinger" title="Hostinger on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/hostinger.jsonmcp.tc isn’t affiliated with Hostinger. This page was built from Hostinger’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.