api

This MCP server exposes a set of Hostinger API related tools via the Model Context Protocol. It runs as a standalone MCP server managed by the hostinger-api-mcp binary. You can connect to it using an MCP client over the chosen transport (stdio by default or HTTP streaming when enabled with the --http option). The server implements multiple tools for interacting with Hostinger-like functionality, including WordPress deployment/import workflows, plugin and theme deployment, and JavaScript application deployments. Clients can query the list of available tools and then invoke a specific tool by name with the required arguments. Typical usage involves starting the server with the appropriate environment variables (notably API_TOKEN for authorization) and then using an MCP client to discover tools and call them with domain, paths, and other parameters as documented for each tool. The included example shows listing tools and calling a tool like billing_getCatalogItemListV1 with a category argument, which demonstrates how tool calls and responses flow over the MCP transport.

Two transport modes are supported: the standard I/O (stdio) transport, which is convenient for local usage and scripting, and the Streamable HTTP transport, which provides bidirectional streaming over HTTP and allows remote clients to connect over HTTP(S). If you enable HTTP transport, you’ll typically run the server with host and port options (for example, --host 0.0.0.0 --port 8150) and connect clients via HTTP to exchange MCP messages. The MCP client workflow remains consistent: connect, list tools, call a tool with the required arguments, and process the response.

Prerequisites:

• Node.js version 24 or higher
• Access to a terminal with npm, yarn, or pnpm as alternative package managers

Install globally from npm (recommended):

npm install -g hostinger-api-mcp

Or install using Yarn:

yarn global add hostinger-api-mcp

Or install with pnpm:

pnpm add -g hostinger-api-mcp

After installation, verify the CLI is available:

hostinger-api-mcp --version

Configuration (environment variables):

• Set DEBUG to true or false to enable debug logging as needed.
• Set API_TOKEN to your Hostinger API token which will be forwarded in Authorization headers by clients.

Optional: Run with HTTP transport enabled

hostinger-api-mcp --http

Tips and caveats:

• Ensure NODE_VERSION meets the minimum requirement (v24 or higher). Consider using NVM to manage Node versions.
• Store your API_TOKEN securely and do not hard-code it in code or public repositories.
• When using HTTP transport, beware of network permissions and firewall rules that may block port 8100 (default) or your configured port.
• If you update the MCP server, use the appropriate package manager command to update globally (npm update -g hostinger-api-mcp, yarn global upgrade hostinger-api-mcp, or pnpm update -g hostinger-api-mcp).
• The Available Tools section documents each tool’s required parameters. Ensure paths (archivePath, pluginPath, etc.) are absolute or correctly resolved relative to the running process.
• If you encounter issues with tool execution times (e.g., large WordPress imports), consider increasing timeout expectations on the client side or adjusting server resources as needed.