Search in all categories
Search in all categories
About Hostinger
Affiliates and Referrals
Agency Hosting Plans
Billing
Codex
cPanel
DNS
Domains
Email
Features
Files Management
Getting Started
Hostinger AI Agents
Hostinger Ecommerce
Hostinger Horizons
Hostinger Reach
Hostinger Website Builder
hPanel
Managed Hermes
Managed OpenClaw
MySQL Databases
PHP
Profile Management
SSL Certificates
Uncategorized
VPS
Website

Hostinger API MCP Server

Running your own Hostinger API MCP server

Updated 1 day ago

The Hostinger API MCP Extension enables 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.

Remote MCP Server

Hostinger now hosts a remote MCP server at:

https://mcp.hostinger.com

This is the fastest way to connect an MCP-compatible AI tool to your Hostinger account — there’s nothing to install, no Node.js version to manage, and no local process to keep running. Authentication is handled entirely through OAuth in your browser.

Claude Code

claude mcp add --transport http hostinger https://mcp.hostinger.com

After running this command, Claude Code will open a browser window for you to authorize the connection via OAuth. Once authorized, all Hostinger tools (VPS, Domains, DNS, Billing, Ecommerce, Hosting, Reach) become available in that session.

Other MCP clients

Most MCP-compatible clients (Cursor, Claude.ai custom connectors, etc.) support adding a remote HTTP/SSE MCP server directly by URL. Point your client’s MCP configuration at:

https://mcp.hostinger.com

and follow its OAuth authorization prompt when connecting. Refer to your specific tool’s documentation for the exact steps to add a remote/custom MCP connector, since the UI differs between tools.

Installation guide

1. Install Node.js

Before installing the MCP server, make sure Node.js 24+ is installed. You can do this via Node Version Manager (nvm):

# Install nvm (if not already installed)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.6/install.sh | bash

# Reload shell
source ~/.bashrc

# Install Node.js 24
nvm install 24

# Set it as default
nvm use 24

2. Install the MCP server CLI

After Node.js is ready, install the MCP server globally:

# Install globally from npm 
npm install -g hostinger-api-mcp 

# Or with yarn 
yarn global add hostinger-api-mcp 

# Or with pnpm 
pnpm add -g hostinger-api-mcp

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 hPanel → 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.