Hostinger’s Week 39 product releases concentrated on operational workflow: a smaller MCP interface for AI tools, multi-intent requests in Hostinger Agent, automatic detection of Node.js environment-variable names, and clearer shared-access permissions. The changes were announced mainly on September 28, 2026, with additional smaller updates through September 30.
What Happened
Hostinger reduced its Model Context Protocol interface to three tools: list_capabilities, get_capability, and execute_capability. The company says the change, included in package version 2.2.0, is intended to expose available actions without loading a large tool list into an AI assistant’s context.
Hostinger Agent can now handle multiple intents in one request—for example, creating a site and then configuring related settings—and can use uploaded images as part of the task. Hostinger also added automatic detection of required environment-variable names during Node.js deployment. Users still have to supply the actual values.
A separate shared-access update now shows what an invited collaborator can access before the invitation is sent. Other Week 39 items included email conversation views, webmail file import, clearer domain-extension pricing conditions, WhatsApp campaigns in Hostinger Reach, and a shortcut from Website Analytics to a human expert.
Why It Matters
The important pattern is the movement from isolated AI features toward operational control. A compact MCP layer can make tools easier for an agent to discover and invoke, while multi-intent requests reduce the number of manual steps required for common workflows.
That convenience also raises the cost of a mistaken instruction. Hosting customers should pay close attention to account permissions, irreversible actions, audit trails, and whether an agent clearly previews changes before executing them.
What the Company Says
Hostinger says the three-tool MCP design improves efficiency and scalability, and that capability documentation is fetched only when needed. It says multi-intent Agent requests can sequence several actions from a single message and use native image understanding. For Node.js deployments, Hostinger says the platform scans the project, identifies required variable names, and prompts the user for values before deployment.
HostingReviewLab Context
Compared with Hostinger’s Week 38 releases, which emphasized business tools and referral features, Week 39 leans more heavily into developer and operator workflows. The MCP change is particularly relevant because interface size and tool discovery can materially affect how reliably an AI assistant chooses an action.
For the broader product and cost picture, see our Hostinger review and Hostinger pricing guide.
What We Haven’t Independently Verified
HostingReviewLab has not run the MCP package against a production Hostinger account, tested multi-intent tasks for partial failures, measured context savings, or verified that environment-variable detection covers every supported Node.js framework. The feature descriptions are based on Hostinger’s changelog.
What Customers Should Know
- Review the requested actions and affected resources before allowing an agent to execute a multi-step task.
- Use shared access rather than handing over primary account credentials, and verify the invitation summary before sending it.
- Environment-variable detection identifies names, not secret values; customers remain responsible for supplying and rotating credentials securely.
- Teams using the MCP package should confirm they are on version 2.2.0 or later and retest existing automations after the interface change.
Event dates: September 28–30, 2026. Source checked: October 5, 2026. Updated: October 6, 2026. Verification status: Reported.
Verify the changed feature in your own workflow
For environment-variable detection, compare the suggested names with the application's actual requirements; detection alone does not prove that values are correct or production secrets are isolated. For shared access, inspect the permissions of a delegated test account. Record the feature and plan used. These are suggested acceptance checks, not evidence that HRL tested this release or that every existing account has identical behavior.