Hosting

Both: remote hosted service and local stdio package

Transport

Streamable HTTP (remote); stdio (local package)

Endpoint

https://mcp.hostinger.com

Authentication

Hosted remote connection uses browser OAuth. The local package accepts a Hostinger API token via HOSTINGER_API_TOKEN / APITOKEN configuration; interactive OAuth is also documented for local stdio when a token is not set. External third-party OAuth-client availability is restricted; follow Hostinger-supported client flow.

Requirements

• Hostinger account with relevant services for actions
• For the local package, Node.js runtime (Hostinger help article says Node.js 24+; current repository Gemini metadata states Node.js 20+), npm or another package manager
• API token for token-based local auth, or browser access for supported OAuth flow

Setup steps

1. Remote: configure a remote Streamable HTTP MCP server at https://mcp.hostinger.com in a supported client and follow its supported browser OAuth flow.
2. Local: install a supported Node.js runtime, then use the official package @hostinger/mcp via npx or its documented CLI.
3. Keep HOSTINGER_API_TOKEN (or the documented APITOKEN variable for applicable modes) in the process environment; never commit tokens in client configuration.
4. Select a product-specific server when fewer tools are preferred, or the all-products server if the client supports its larger catalog.
5. Verify the connection with a harmless read-only query before attempting account changes.

The MCP server interface exposes search, execute and multi-execute. These three are MCP tools; the many underlying Hostinger API operations discovered by search vary by binary/scope and are not a fixed exposed tools/list.

• search

  Find relevant Hostinger API operations for a task (support article description; exact schema varies by implementation).

  01
• execute

  Execute a selected Hostinger API operation.

  02
• multi-execute

  Execute multiple Hostinger API operations in one request.

  03

• Tool operations can change real hosting resources; use client approval and read-only verification before writes.
• Hostinger API documentation currently states a general 90 requests/minute rate limit, with some custom/per-endpoint limits.
• Published Hostinger help article says Node.js 24+, while the current repository Gemini extension lists no runtime version; use the stricter vendor help requirement for local install until docs reconcile.
• Do not assume external custom OAuth clients can use Hostinger OAuth; repository issue response says OAuth access for third-party external integrations is currently unavailable.

• Node.js minimum version differs between Hostinger support article (24+) and repository metadata/extension usage which does not declare a minimum; record conservative requirement and revisit.
• Support article describes both remote OAuth and generic other-client setup, but repository issue says third-party OAuth client access is currently unavailable. Do not advertise generic custom-client OAuth as guaranteed.

• official tool reference

  Hostinger-maintained server exposes three MCP meta-tools (search, execute, multi-execute); each binary has the same interface. Search discovers the underlying API operations, which vary by binary/scope and are not 372 simultaneously exposed MCP tools.

• official documentation or source

  Hostinger-maintained server exposes three MCP meta-tools (search, execute, multi-execute); each binary has the same interface. Search discovers the underlying API operations, which vary by binary/scope and are not 372 simultaneously exposed MCP tools.

Documentation checked 2026-10-28T12:53:18.000Z. Connection has not been runtime tested.