hostinger-mcp-server
Related Servers
Alternatives to hostinger-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseBqualityAmaintenanceThe Hostinger MCP server enables seamless integration of Hostinger’s API with AI tools. This server exposes Hostinger API endpoints as callable tools, allowing AI models to fetch live data or perform real-time actions on hosting infrastructure.4012,941 npm155MIT- AlicenseAqualityDmaintenanceA complete MCP server enabling AI assistants to manage cPanel hosting through natural language, including file, database, email, subdomain, and system operations.161MIT
- FlicenseBqualityDmaintenanceA unified MCP server for managing hosting fleets, enabling natural language control over SSH, WordPress, Cloudflare, MySQL, GitHub, Docker, Coolify, and more.381-

agenthost MCP serverofficial
FlicenseNot gradedqualityCmaintenanceAgent-first web hosting driven entirely through a remote MCP server, enabling full hosting management via natural language with OAuth or token authentication.-- FlicenseBqualityBmaintenanceA comprehensive MCP server for managing cPanel hosting accounts through AI assistants. It supports DNS, email (DKIM/SPF), databases, domains, SSL, PHP, cron jobs, security, Git deployment, and more.10022-
- AlicenseCqualityBmaintenanceEnables conversational management of hosting account resources such as apps, domains, databases, files, PHP, SSL, and more through MCP-compatible clients.19414 npmMIT
TDQS
Scored across 284 tools
The sheer volume of 284 tools creates substantial selection ambiguity, with near-duplicates like list_all_domains_paginated versus domains_get_list and multiple plugin discovery tools (wp_plugins_available/search/suggested) that overlap significantly. While most tools are prefixed by service area, the boundaries between related utilities are often unclear without deep inspection, especially given the paginated and batch helper tools that duplicate existing operations.
Tool names broadly follow a domain_entity_action pattern (e.g., vps_firewall_create, hosting_db_delete, wp_plugins_activate), but significant inconsistencies exist: get/list are used interchangeably, create/add/enable/install all appear for similar operations, and some tools reverse the action/object order (vps_create_snapshot vs. vps_docker_create). Utility helpers like batch_dns_update and list_all_domains_paginated break the domain-prefix pattern entirely, making the naming scheme readable but not predictable.
With 284 tools, this server has a severe excess of endpoints that far exceeds the 50+ threshold for an extreme mismatch. Such a massive surface overwhelms agents and makes reliable tool selection impractical, even though the underlying Hostinger API does cover many services.
The tool set is remarkably comprehensive, providing CRUD and lifecycle coverage across billing, domains, DNS, VPS, hosting, WordPress, mail, ecommerce, agency, and Horizon services. Minor gaps exist—such as no WHOIS profile update endpoint, no mailbox quota modification, and no domain transfer initiation—but the overall domain coverage is extensive with few dead ends.