Log inSubmit server
Hostinger API MCP logo

Hostinger API MCP

Connects MCP clients to Hostinger API operations through search, single-operation execution, and batched workflows.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Hostinger API MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "hostinger-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hostinger/mcp"
      ],
      "env": {
        "HOSTINGER_API_TOKEN": "YOUR_VALUE_HERE",
        "DEBUG": "YOUR_VALUE_HERE",
        "OAUTH_ISSUER": "YOUR_VALUE_HERE",
        "API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The hostinger-api-mcp MCP server exposes Hostinger API operations to MCP-compatible clients through three tools: search, execute, and multi-execute. It can run locally over stdio, serve streamable HTTP, or connect to Hostinger's hosted endpoint at https://mcp.hostinger.com. Authenticate with a Hostinger API token for automation, or use OAuth 2.0 with PKCE for interactive local sessions. Reach for it when an agent needs to discover and call Hostinger operations across domains, hosting, DNS, billing, VPS, WordPress, and other supported API groups.

Use cases

  • Discover Hostinger operations by keyword
  • Execute domain and hosting API actions
  • Chain dependent Hostinger calls
  • Connect an MCP client to Hostinger's hosted endpoint

Key features

  • Search operations with input schemas
  • Execute individual Hostinger operations
  • Run up to 20 dependent operations
  • Support stdio and streamable HTTP transports
  • Authenticate with API tokens or OAuth 2.0 with PKCE

Tools3

What Hostinger API MCP lets your agent do. Expand a tool for its parameters.

Self-reported~84 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 34d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @hostinger/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars163Stargazers on the source repository.
Last commit3d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Hostinger API MCP works

What hostinger-api-mcp does

The hostinger-api-mcp MCP server makes Hostinger API operations available to an MCP client. Its unified binary covers 403 operations across the API, while the same package also provides narrower binaries for groups such as domains, hosting, DNS, billing, mail, VPS, and WordPress. The unified command remains the backwards-compatible default.

This fits the Cloud Platforms category because agent workflows can use Hostinger account and infrastructure operations without requiring each workflow to implement direct API calls. The server is useful for tasks that need operation discovery, one API call, or a sequence of dependent calls.

How it works

The server exposes three MCP tools:

  • search looks up operations by keyword and returns matching input schemas.
  • execute invokes one named operation with a parameters object.
  • multi-execute runs as many as 20 operations in order and stops when one fails.

A later step in multi-execute can receive a value from an earlier result when its parameter is exactly formatted as $steps.<i>.<path>. This supports workflows where one Hostinger result supplies input to the next operation.

The process supports local stdio transport by default and streamable HTTP transport with configurable host and port settings. A hosted remote endpoint is also available at https://mcp.hostinger.com.

Setup and configuration

Install Node.js 24 or newer, then install the package globally with npm, Yarn, or pnpm. The installed hostinger-api-mcp command can be added to an MCP client configuration such as Claude or Cursor.

For token-based use, set HOSTINGER_API_TOKEN. The value is sent in the Authorization header and takes precedence over OAuth. API_TOKEN is a deprecated alias. DEBUG enables debug logging, and OAUTH_ISSUER changes the OAuth server base URL when a token is not supplied.

Local stdio sessions can authenticate through OAuth 2.0 with PKCE. The --login option starts that flow immediately, while --logout revokes stored credentials. The hosted endpoint uses an OAuth authorization prompt when added as a remote Streamable HTTP server.

Tools and capabilities

The hostinger-api-mcp MCP server provides access to the unified operation set through the three common tools. Scoped binaries use the same interface but restrict searches and executions to their own operation group. This lets a deployment choose broad API access or a narrower command where appropriate.

HTTP mode runs on localhost port 8100 by default and accepts custom host and port values. HTTP mode requires HOSTINGER_API_TOKEN; OAuth sign-in is not supported in that mode. Stdio mode is the default for local client integrations.

Limitations and notes

The server does not describe every operation directly through separate MCP tools; agents should use search to find an operation and inspect its returned schema before calling execute. Batched execution is limited to 20 operations and halts at the first failure. API behavior, permissions, and available results remain subject to the Hostinger API and the credentials in use.

OAuth credentials are stored locally in a credentials file and shared by the Hostinger MCP binaries. The package also hides operations that have been superseded by newer tools from search, although those older operations may continue to work through execute until removed.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Hostinger API MCP

hostinger-api-mcp is an MCP server that connects MCP-compatible clients to the Hostinger API. Its main tools are search for discovering operations, execute for running one operation, and multi-execute for running up to 20 ordered operations with references to earlier results.

Install Node.js 24 or newer, then run `npm install -g @hostinger/mcp`, `yarn global add @hostinger/mcp`, or `pnpm add -g @hostinger/mcp`. The package installs the `hostinger-api-mcp` command for local MCP client configuration.

Set `HOSTINGER_API_TOKEN` for token-based authentication, or use the local OAuth 2.0 with PKCE flow when no token is configured. Run `hostinger-api-mcp --login` to start OAuth manually; token authentication is required for HTTP mode.

Yes, hostinger-api-mcp can be added to Cursor as an MCP server. Configure the local `hostinger-api-mcp` command with its environment variables, or add Hostinger's remote Streamable HTTP endpoint according to Cursor's MCP configuration.

Yes, it supports streamable HTTP transport. Run `hostinger-api-mcp --http`, optionally provide `--host` and `--port`, and set `HOSTINGER_API_TOKEN`; OAuth sign-in is not supported in HTTP mode. Hostinger also provides a hosted endpoint at `https://mcp.hostinger.com`.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHostinger API MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hostinger-api-mcp?style=directory)](https://allmcps.com/mcp/hostinger-api-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/hostinger-api-mcp"><img src="https://allmcps.com/api/badge/hostinger-api-mcp?style=directory" alt="Hostinger API MCP on AllMCPs" /></a>