hostinger-mcp-server

Hostinger API MCP server for Perplexity custom MCP connector.
Wraps the official hostinger-api-mcp package (118 tools) in a Docker container running Streamable HTTP transport — the format Perplexity's custom MCP connector requires.

What this gives you

118 Hostinger API tools exposed over HTTP MCP:

• Domain registration, DNS records, transfers
• VPS management (start/stop/rebuild/snapshot)
• Billing, subscriptions, payment methods
• WordPress hosting, SSL, email, firewall
• Full hPanel API surface

Prerequisites

1. Hostinger API Token — hPanel → Profile → Account Information → API → Generate token
   Store in Doppler as HOSTINGER_API_TOKEN
2. Node.js 24+ in the Docker image (already set)
3. A running host — Northflank recommended (spec included)

Local development

# Run with docker-compose
API_TOKEN=your_token_here docker-compose up

# Test the server is alive
curl http://localhost:8100/

# Test MCP tools list
curl -X POST http://localhost:8100/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Deploy to Northflank

1. Create a new Deployment Service in Northflank from this repo
2. Use northflank.json as the service spec reference
3. Create a secret group hostinger-mcp-secrets with key API_TOKEN = your Hostinger token
4. Link the secret group to the service
5. Deploy — Northflank will build the Dockerfile and expose the public URL

Wire to Perplexity

Once deployed and the public URL is live (e.g. https://hostinger-mcp-server-xxx.northflank.app):

1. Go to Perplexity Settings → MCP Connectors → Add Custom MCP
2. URL: https://your-northflank-url/mcp
3. Auth: None required (the Hostinger token is server-side only)
4. Name: Hostinger API
5. Save — Perplexity will discover all 118 tools automatically on next session start

Environment variables

Variable	Required	Description
API_TOKEN	✅ Yes	Hostinger API token from hPanel
DEBUG	No	Set true for verbose logging (default: false)

Port

Default: 8100. Override with --port XXXX in the Dockerfile CMD if needed.

Transport

Runs in --http Streamable HTTP mode (not stdio). This is the correct transport for remote MCP clients like Perplexity, n8n, or any network-accessible MCP consumer.