A Digital Consulting Plus methodology
English
← Full mapCurated public summary
Index
Handbook
01DCP Flow: what it is and why it exists02How DCP Flow works03How to start a project04Kai and working with AI agents04AKai operational capabilities05Institutional Prompt Cookbook06Solution Discovery explained for humans07Architecture, stack, and technology ecosystem07ATool & MCP Registry07BHostinger MCP for DCP websites and hosting08Quality Gates, QA, security, and evidence08AQuality profiles and testing strategy09Git, branches, PRs, and multi-agent work10Deploy, release, support, and operational evolution10AContainer First and standardized host operations10BPractical Container First demo11How DCP Flow evolves12Real cases and lessons learned13How to teach DCP Flow14Practical DCP Flow use cases15End-to-end playbooks: Web and Laravel
Entry 07B48%
48%10 / 21
Entry 07BPUBLIC HANDBOOK

Hostinger MCP for DCP websites and hosting

When Hostinger API MCP applies to Websites, Domains/DNS, shared hosting, and VPS; boundaries against Git/deployment/SSH/IaC, OAuth, minimum scope, and POC.

Source & authority

Public explanation

PUBLIC HANDBOOK
Based on
Human Handbook 07B — Hostinger MCP for DCP websites and hosting
Related normative sources
  • NORMATIVE SOURCEStandard · AI Project Context
Authority
Public explanation — NON-NORMATIVE
Summary

When Hostinger API MCP applies to Websites, Domains/DNS, shared hosting, and VPS; boundaries against Git/deployment/SSH/IaC, OAuth, minimum scope, and POC.

Hostinger API MCP is a specialized integration for Hostinger-supported operations. DCP Flow explicitly defines where it adds value and where Git, SSH, deployment pipelines, or IaC remain the correct layer.

Where it applies

It can support Websites, Domains/DNS, shared hosting, and selected Hostinger VPS surfaces. Authentication should use the supported mechanism with minimum scope and client isolation.

Key points
  • Websites.
  • Domains and DNS.
  • Shared hosting.
  • Hostinger VPS where the API supports it.

Boundaries and POC

It should not be treated as a universal replacement for Git, deployment, SSH, or IaC. Adoption starts with a low-risk POC, minimum permissions, traceability, and Manual Fallback.

Key points
  • Does not replace Git.
  • Does not replace deployment pipelines.
  • Does not replace SSH/IaC when needed.
  • POC before ADOPTED.

Hostinger MCP applies when the problem actually belongs to Hostinger

Its potential boundary covers Websites, Domains/DNS, shared hosting, inventory, and selected provider-level VPS capabilities. It remains EXPERIMENTAL: the official source was reviewed, but the POC is still pending, so it is not a default production dependency.

Key points
  • Websites / shared hosting.
  • Domains and DNS.
  • VPS provider-level capabilities.
  • EXPERIMENTAL until POC.

DNS, authentication, and multi-client use require minimum blast radius

DNS changes can affect web, mail, and APIs, so the flow must preserve current state, impact/TTL, authorization, mutation, independent verification, and evidence. For DCP agents, OAuth with minimum scope is preferred over broad static tokens when supported. An agent working for one client should not receive unnecessary access to other clients’ resources.

Key points
  • DNS mutations require second-source verification.
  • OAuth + minimum scope when viable.
  • Keep tokens out of repositories and prompts.
  • Multi-client isolation.

The MCP does not create a second deployment path

Git/GitHub remain the code source of truth and the runtime/deployment profile preserves the official Git → build → artifact → hosting flow. Hostinger MCP may help configure the provider, but it does not replace artifacts, backups, migrations, Quality Gates, SSH/Linux when operating-system access is required, or IaC when state must remain declarative.

Key points
  • Does not replace Git or artifacts.
  • Does not replace SSH/Linux for runtime inspection.
  • Does not replace IaC where applicable.
  • POC must prove auth, scope, evidence, and revocation.
Contextual glossary＋
MCP

Interface/protocol for exposing tools and resources to AI agents in a structured way.

Manual Fallback

Explicit, verifiable manual procedure used when Kai cannot execute an action directly.

Deployment

Technical act of placing a version into an environment.

Infrastructure

Infrastructure