setup-hostinger-mcp

Configure Hostinger MCP integration with global or local MCP files and token storage.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/diegolirio/ai-showcase-skills --skill setup-hostinger-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-hostinger-mcp
Source: https://github.com/diegolirio/ai-showcase-skills/tree/main/skills/setup-hostinger-mcp
Command: npx skills add https://github.com/diegolirio/ai-showcase-skills --skill setup-hostinger-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill configures the Hostinger MCP integration, simplifying secure, centralized management of VPS, sites, and DNS from the IDE.

Core Features & Use Cases

  • Prompt-based scope selection (global or local MCP file) and token storage preferences.
  • Merge updates into existing MCP files without overwriting, preserving prior configurations.
  • End-to-end workflow from initial token collection to final MCP file configuration.

Quick Start

Configure Hostinger MCP from Claude Code by answering prompts to set scope, storage mode, and API token.

Frequently Asked Questions about setup-hostinger-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Hostinger MCP integration in Claude Code?

To configure Hostinger MCP in Claude Code, you follow a guided prompt workflow to set the configuration scope, choose token storage preferences, and input your API token. The skill validates the JSON structure and writes the MCP configuration safely without overwriting existing files.

Does the Hostinger MCP setup overwrite existing MCP file configurations?

No, the Hostinger MCP setup merges updates into existing MCP files without overwriting prior configurations. It safely integrates new VPS and DNS management settings while preserving your current JSON MCP_FILE structure.

Can I store my Hostinger API token as an environment variable instead of directly in the MCP file?

Yes, you can choose your token storage preference during the Hostinger MCP setup. The prompt-based workflow allows you to store the API token either as an environment variable or directly within the MCP configuration file.

What is the difference between global and local scope when managing Hostinger MCP?

Global scope applies the Hostinger MCP configuration across all your projects, while local scope restricts the VPS management settings to a single project. The setup workflow prompts you to select the appropriate MCP file scope for your needs.

How do I securely manage VPS and DNS settings from my IDE using the Hostinger API?

You can securely manage VPS, sites, and DNS from your IDE by configuring the Hostinger MCP integration in Claude Code. This centralized setup validates your JSON configuration and handles token collection safely to enable API-driven server management.