Title: Hostinger API MCP Server
URL Source: https://www.hostinger.com/support/11079316-hostinger-api-mcp-server/
Published Time: April 14, 2025
Markdown Content:
Running your own Hostinger API MCP server
Updated 7 days ago
The Hostinger API MCP Extensionenables seamless integration of Hostinger’s API with AI tools that support the Model Context Protocol (MCP) — such as Claude, Cursor, or other AI coding assistants. This extension exposes Hostinger API endpoints as callable tools across Websites, VPS, Domains (including DNS), Email Marketing, Subscriptions & Payments, and Ecommerce, allowing AI models to fetch live data or perform real-time actions on hosting infrastructure.
In other words, you can now “vibe sysadmin” your services on Hostinger.
Key capabilities
- API Integration: Connects directly to Hostinger’s Developer API
- AI Tool Compatibility: Built for environments supporting MCP, like Claude or Cursor
- Automated Operations: Enables AI to manage services and more
- Per-product MCP configuration: Enable or disable MCPs per product (Websites, VPS, Domains (includes DNS), Email Marketing, Subscriptions & Payments, Ecommerce) from the sidebar. DNS tools are bundled under Domains and do not appear as a separate toggle. Recommended since most IDEs have a ~100 tool limit for efficient performance.
- Email Marketing Tools support: Email Marketing (formerly Reach) is now included as a supported product.
- Per-site WordPress MCPs: WordPress sites now appear as individual MCPs (not bundled under a single Websites toggle), enabling per-site tool access for AI agents.
- Improved token security: API token is now passed via environment variable instead of being written to a config file on disk.
- Changelog introduced: A changelog is now available for the extension.
Hostinger Connector
The easiest way to connect is Hostinger Connector, a guided setup available from the Integrations page of Websites, Email Marketing, and other Hostinger products. Click Set up Connector, or Connect with ChatGPT to connect directly to ChatGPT, then sign in once to authorize access. No installation, token management, or configuration file is required.
Once connected, you can ask your AI assistant to manage your Hostinger resources directly, for example:
- Show me contacts added this week
- Rename the segment Winter leads to Q1 leads
- Add, update, or delete DNS records
- Check my VPS status
AI integration setup
Tools like Claude, Cursor, Devin Desktop (formerly Windsurf), and OpenAI Codex don’t require manually running the MCP server. This article provides instructions on how to provide Claude with the following configuration:
{
"mcpServers": {
"hostinger-api": {
"command": "hostinger-api-mcp",
"env": {
"DEBUG": "false",
"API_TOKEN": "YOUR API TOKEN"
}
}
}
}
- API_TOKEN: Your access token for authenticating with Hostinger’s API. This is passed as an environment variable for improved security — do not write it directly into a config file on disk.
- DEBUG: Optional, set to “true” if you want verbose logs for debugging.
Authentication
The Hostinger API MCP server supports two authentication methods:
API Token (original method — still supported)
- Generate a token in Hostinger dashboard → Account → API
- Pass it via the API_TOKEN environment variable in your MCP config
- Suitable for personal use and single-user setups
OAuth (new)
- Recommended for AI agents, external tools, and multi-user or production environments
- More secure and easier to set up without manual token management
- For setup instructions, refer to the GitHub repository
Both methods are supported simultaneously. Existing API token integrations do not require any changes.
Additional resources
The Hostinger MCP Server is a simple yet powerful bridge that connects AI interfaces to real-world hosting actions. Exposing Hostinger API endpoints as tools empowers AI tools to go beyond chat — enabling direct, intelligent, and automated management of hosting environments.