集成

Hostinger MCP

试用

通过官方 hostinger-api-mcp 服务器管理 Hostinger VPS、主机、域名、DNS、Reach 邮件营销和账单。

它能做什么

对接官方 Hostinger MCP 服务器(本地 npm 进程,Node.js 24+,共 127 个工具),用于管理 VPS、网站主机、域名、DNS、Reach 邮件营销与账单,支持一个或多个 Hostinger 账户。按需加载对应类别的二进制(VPS / hosting / domains / Reach / DNS / billing),而不是一次性加载全部工具。所有写入操作都要先确认目标资源与具体动作;涉及扣费的操作额外确认费用;删除、重装 VPS、对生产环境执行 DNS 重置等破坏性操作则需要双重确认。

什么时候用它

  • 查看某个 Hostinger 账户下的 VPS、主机、域名、DNS 记录或 Reach 联系人
  • 创建、停机、重启或重装 Hostinger VPS(需确认)
  • 注册域名、购买 VPS 或变更账单/支付方式(需确认费用)
  • 修改 DNS 记录或部署、导入 Hostinger 托管的站点(需确认)

技能文档

Hostinger MCP — Operational Skill

Managing Hostinger infrastructure — VPS, hosting, domains, DNS, Reach, billing — through the official Hostinger MCP server.

Connection / tool loading: This skill targets the official Hostinger MCP server, which runs as a LOCAL npm process (hostinger-api-mcp, Node.js v24+) — not a hosted URL. The server exposes 127 tools split across category binaries. Load only the category binaries you need for the task — do not load all 127 tools at once. The binaries:

  • hostinger-vps-mcp — 62 (VPS)
  • hostinger-hosting-mcp — 22 (websites/hosting)
  • hostinger-domains-mcp — 18 (domains)
  • hostinger-reach-mcp — 10 (email marketing)
  • hostinger-dns-mcp — 8 (DNS)
  • hostinger-billing-mcp — 7 (billing)
  • hostinger-api-mcp — all 127 (everything; use only when a task genuinely spans categories)

Default to the smallest set covering the task. A pure DNS edit needs only hostinger-dns-mcp (8 tools), not the full 127. See references/installation.md.

Tool names match the upstream package. The catalog and workflows use the official hostinger-api-mcp tool names. Always treat the live mcp__hostinger*__* tools as the source of truth if Hostinger changes them (see "Versioning and source of truth" below).


Quick Route

IntentLoad
Initial installation/configuration of the MCP serverreferences/installation.md
Don't know which tool exists / searching for a tool by namereferences/tools-catalog.md
VPS operations (create, firewall, snapshot, recreate, etc.)references/workflows-vps.md
Multiple Hostinger accounts / multi-account configurationreferences/installation.md (Multi-account section)

Load only what's needed. Match the binary to the task (see Connection above), and don't load the full catalog just to "list my VPSes" — call VPS_getVirtualMachinesV1 directly.


Safety rules (read before every operation)

  1. Identify the account first (multi-account). Each Hostinger account is a separate MCP connection with its own prefix (mcp__hostinger-__*). Resource IDs are NOT interchangeable between accounts — VM ID 123456 in account A is a different resource (or nonexistent) in account B. Before every call, verify which account it belongs to. If it's unclear which account is meant, stop and ask — don't guess, and don't run across all of them "to be safe".

  2. Write operations require explicit confirmation. Before any write tool, present: the account, the tool name, the target resource (ID + name), the parameters, and the expected impact. Wait for an explicit "yes". One confirmation ≠ blanket consent for further operations, and a confirmation on one account never carries to another.

  3. Money-spending operations require cost-confirmation. domains_purchaseNewDomainV1, VPS_purchaseNewVirtualMachineV1, enabling billing auto-renewal, and billing_setDefaultPaymentMethodV1 spend real money (now or on the next renewal). Confirm the cost AND the account before executing.

  4. Destructive operations double-confirm (W!). Any *delete* tool, VPS_recreateVirtualMachineV1 (reinstalls the OS, wipes all data), and DNS_resetDNSRecordsV1 on production require confirmation of both the operation and the specific target.

  5. Multiple workloads per VPS. A single VPS may host several sites/services. VPS_stopVirtualMachineV1, VPS_restartVirtualMachineV1, and VPS_recreateVirtualMachineV1 affect everything on it. Make the user aware of what runs on the VM before any VPS-level operation.

  6. Credentials. Each account uses its own HOSTINGER_API_TOKEN — full account access, with no per-tool permission at the MCP layer. Never print the token in responses. If the user asks to see it, refer them to hPanel.

  7. Read-only by default. For "show / check / list", pick the read-only tool (e.g. VPS_getVirtualMachinesV1, domains_getDomainListV1, DNS_getDNSRecordsV1). Never suggest a destructive operation unless explicitly asked.


Confirmation pattern

Before executing a write, present a block like this:

🔒 Confirm operation?
   Account: clientA (mcp__hostinger-clientA-vps)
   Tool: VPS_recreateVirtualMachineV1
   Target: vps-prod-01 (ID: 123456)
   Impact: reinstalls the OS and WIPES ALL DATA on the VM
   Proceed? (yes / no / check for a snapshot first)

For money-spending operations, add an Estimated cost: line:

🔒 Confirm operation?
   Account: clientA (mcp__hostinger-clientA-domains)
   Tool: domains_purchaseNewDomainV1
   Target: example.co.il (new registration)
   Estimated cost:  for 
   Impact: charges the account's default payment method
   Proceed? (yes / no)

Wait for an explicit "yes" — implied consent is not enough. The account line is mandatory when more than one account is connected; it prevents executing on the wrong account.


Multi-account — working with multiple Hostinger accounts

Token-per-connection. Each account connects as a separate MCP connection with its own HOSTINGER_API_TOKEN, and appears in Claude with its own prefix:

mcp__hostinger-clientA__VPS_getVirtualMachinesV1
mcp__hostinger-clientB__domains_getDomainListV1
mcp__hostinger-clientA-dns__DNS_getDNSRecordsV1

Name each connection hostinger- — or, when loading per-category binaries, hostinger-- (e.g. hostinger-clientA-vps, hostinger-clientA-dns).

Rules

  • Identify the account before every operation. Single account connected → use it. Multiple → determine which from the request; if unclear, stop and ask. If a resource name unambiguously identifies one account you may infer, but state which account you're operating on.
  • IDs don't cross accounts. A VM/domain/subscription ID from one connection is valid only against that connection. Never pass it to another.
  • Never reuse a token across accounts. Each connection has its own HOSTINGER_API_TOKEN; don't assume the same token works elsewhere.
  • Per-account confirmation. A write confirmation on one account never applies to another — each write on a new account gets a fresh confirmation block (including the account line).
  • Cross-account reads are fine. For broad "which account owns example.com?" questions, run the same read on each connection separately and tag each result with the account name. Never run a broad write across accounts without individual confirmation for each.

Authentication — quick overview

  • HOSTINGER_API_TOKEN (default). A Bearer token generated in hPanel, passed to the MCP server via env. This is the standard path.
  • OAuth 2.0 PKCE (interactive alternative). Available on stdio transport only, via hostinger-api-mcp --login.

The token has full account access — every action the account can perform in hPanel. There is no granular / per-tool permission at the MCP layer: any connected client can call any tool. Treat it like a password and never print it in responses. If the user asks to see it, refer them to hPanel.

For the full connection and multi-account setup, see references/installation.md.


Versioning and source of truth

  • Tool names match the upstream package. The tool names and categories here are taken from the official hostinger-api-mcp package.
  • The live MCP wins if Hostinger changes them. If a tool name or capability differs from what's documented, the live mcp__hostinger*__* tools connected in Claude are the source of truth — check them and update the catalog accordingly.
  • Every write tool goes through the confirmation pattern. W = single confirmation; W! = double-confirmation for destructive ops (any *delete*, VPS_recreateVirtualMachineV1, DNS_resetDNSRecordsV1 on production), per references/tools-catalog.md. Money-spending ops additionally require cost-confirmation.

相关技能

把自然语言描述转为结构化 JSON,并由 mcp-diagram-generator MCP 服务生成 Draw.io、Mermaid 或 Excalidraw 图表文件。

作者 nssa.io1.0k 次安装47 星标

以 AI 机器人身份加入视频会议,提供语音、虚拟形象与屏幕共享四种模式。

作者 johnpatternai22 次安装8 星标

在本地磁盘以分类纯 Markdown 文件保存需要长期留存的事实,与智能体内置记忆并存。

作者 Iván561 次安装18 星标

诊断生产力系统反复失效的根因,给出最小干预——容量测算、瓶颈定位、可靠的本地记录。

作者 Iván857 次安装69 星标

从 AdMapix API 拉取广告创意、应用、榜单和收入预估等数据,原样返回结构化 JSON。

作者 fly0pants4.3k 次安装296 星标

benkalsky 的更多技能

浏览全部技能

通过官方 Cloudways MCP 运维服务器与应用,写操作需确认目标与影响,并按账号隔离。

作者 benkalsky12 次安装1 星标

通过 REST API 管理 WordPress 内容,带显式审批、批量演练与插件/CPT 工具支持。

作者 benkalsky62 次安装1 星标

Production-grade operational guide for creating, managing, optimizing, and documenting Meta (Facebook/Instagram) ad campaigns via the Facebook Ads MCP. Use w...

作者 benkalsky19 次安装1 星标

Helps with WordPress + Elementor work via the elementor-mcp MCP server — building new pages, editing existing ones, inspecting site state, or exploring what's possible. Auto-detects Elementor Pro (native Form, Theme Builder, Loop Grid, Popups, Dynamic Tags, Sticky/Motion vs free-tier workarounds) AND the page engine (classic vs Elementor 4 atomic/V4 — atomic uses add-flexbox/add-atomic-* tools since classic writes don't persist on a V4 page). Detects ACF + Crocoblock/JetEngine for dynamic-data binding (Tier-0; bind ACF via Pro dynamic tags, place Jet widgets via add-widget with runtime-verified types). On atomic (V4) sites, authors the Elementor 4 design system — Global Classes, Variables (design tokens), and per-element Interactions — and recovers from the fork's schema-in-error and governance responses. Asks what the user wants before acting. Use when the user references the Elementor MCP, invokes `/siteagent-elementor-studio`, or runs `mcp__elementor__elementor-mcp-*` tools. Also co

作者 benkalsky1 次安装1 星标