Hostinger API MCP Server

Common errors

• Error: The Node.js version is too old. Please update to Node.js v24 or higher.

  cause Attempting to run `hostinger-api-mcp` with an unsupported or outdated Node.js version (e.g., v20, v22).
  fix Upgrade your Node.js installation to version 24 or higher. We recommend using `nvm` (`nvm install v24 && nvm use v24`).

• 401 Unauthorized

  cause The Hostinger API token (`API_TOKEN`) is missing, incorrect, or expired, preventing authentication with the Hostinger API via the MCP server.
  fix Verify that the `API_TOKEN` environment variable is correctly set on the server-side and contains a valid, active Hostinger API token. For client applications, ensure the `Authorization` header is properly formatted (`Bearer YOUR_TOKEN`).

• Error: listen EADDRINUSE: address already in use 127.0.0.1:8100

  cause Another application or another instance of `hostinger-api-mcp` is already bound to the default HTTP port 8100.
  fix Either stop the process currently using port 8100, or run the `hostinger-api-mcp` server on a different port using the `--port` option (e.g., `hostinger-api-mcp --http --port 8150`).

Warnings

• gotcha The `hostinger-api-mcp` server officially recommends Node.js version 24 or higher in its `README`, despite the `package.json` specifying `>=20.0.0`. Running on versions older than 24 may lead to unexpected behavior or missing features.
  Fix: Ensure your Node.js environment is version 24 or newer. Use a Node Version Manager (like NVM) for easy switching (e.g., `nvm install v24 && nvm use v24`).
• gotcha Authorization is mandatory for interacting with the Hostinger API through the MCP server. The `API_TOKEN` environment variable must be set on the server-side, and client requests must include a valid `Authorization` header.
  Fix: Set the `API_TOKEN` environment variable before starting the `hostinger-api-mcp` server (e.g., `API_TOKEN=YOUR_SECRET_TOKEN hostinger-api-mcp`). For clients, ensure the `Authorization: Bearer <API_TOKEN>` header is correctly provided.
• gotcha As a pre-1.0 release, this package follows `0.y.z` versioning, which implies that minor (`y`) version increments might introduce breaking changes. Developers should review changelogs carefully before upgrading.
  Fix: Consult the GitHub changelog (`https://github.com/hostinger/api-mcp-server/releases`) for specific breaking changes and migration steps with each new minor version.

Install

• npm install hostinger-api-mcp npm
• yarn add hostinger-api-mcp yarn
• pnpm add hostinger-api-mcp pnpm

Imports

• Client
  wrong:

  const Client = require('@modelcontextprotocol/sdk/client/index.js');

  correct:

  import { Client } from '@modelcontextprotocol/sdk/client/index.js';

  The hostinger-api-mcp package is primarily a global CLI tool and does not export JavaScript symbols directly. These imports are for the companion `@modelcontextprotocol/sdk` client library, used to programmatically interact with the running MCP server.
• StreamableHTTPClientTransport
  wrong:

  const StreamableHTTPClientTransport = require('@modelcontextprotocol/sdk/client/streamableHttp.js');

  correct:

  import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';

  Used to establish an HTTP streaming connection to the hostinger-api-mcp server when it's running in HTTP mode.
• ListToolsResult

  import type { ListToolsResult } from '@modelcontextprotocol/sdk/client/index.js';

  A common pattern in SDKs is to export types for return values. This type would represent the structure of the response from `client.listTools()`.

Quickstart

This quickstart demonstrates how to use the `@modelcontextprotocol/sdk` to connect to a running `hostinger-api-mcp` server, list available tools, and call a specific tool like `billing_getCatalogItemListV1`.

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const API_TOKEN = process.env.API_TOKEN ?? 'YOUR_HOSTINGER_API_TOKEN';
if (API_TOKEN === 'YOUR_HOSTINGER_API_TOKEN') {
  console.warn('API_TOKEN environment variable not set. Replace with your actual token or set process.env.API_TOKEN.');
}

async function runMcpClient() {
  // Ensure the hostinger-api-mcp server is running, e.g., 'hostinger-api-mcp --http'
  const transport = new StreamableHTTPClientTransport({
    url: "http://localhost:8100/",
    headers: {
      "Authorization": `Bearer ${API_TOKEN}`
    }
  });

  const client = new Client({
    name: "my-hostinger-client",
    version: "1.0.0"
  }, {
    capabilities: {}
  });

  try {
    await client.connect(transport);
    console.log("Connected to Hostinger MCP server.");

    const { tools } = await client.listTools();
    console.log("Available tools:", tools.map(tool => tool.name));

    // Example: Call a tool if one is available
    const billingTool = tools.find(t => t.name === 'billing_getCatalogItemListV1');
    if (billingTool) {
      const result = await client.callTool({
        name: "billing_getCatalogItemListV1",
        arguments: { category: "DOMAIN" }
      });
      console.log("Result of billing_getCatalogItemListV1:", result);
    } else {
      console.log("Tool 'billing_getCatalogItemListV1' not found.");
    }
  } catch (error) {
    console.error("Error connecting to or interacting with MCP server:", error);
  } finally {
    await client.disconnect();
    console.log("Disconnected from Hostinger MCP server.");
  }
}

runMcpClient();