hostinger-api-mcp is an executable server designed to implement the Model Context Protocol (MCP), enabling AI agents and automated systems to interact with Hostinger API functionalities as discoverable tools. It provides a standardized interface for tool discovery and execution, facilitating integrations with AI platforms such as Claude or Cursor. The package is currently in early development at version `0.1.39`, indicating frequent, minor updates primarily for dependency maintenance rather than major feature releases. Its core differentiators include its specific focus on exposing Hostinger services through the MCP standard and its versatile support for both standard I/O and HTTP streaming transports, offering flexible deployment options for AI-driven workflows.
npm install hostinger-api-mcpVerified import paths — ran on the pinned version, not inferred.
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`.
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`).
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.
Consult the GitHub changelog (`https://github.com/hostinger/api-mcp-server/releases`) for specific breaking changes and migration steps with each new minor version.
Upgrade your Node.js installation to version 24 or higher. We recommend using `nvm` (`nvm install v24 && nvm use v24`).
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`).
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`).
No dependency data recorded yet.