Describes the environment variables required to run the server.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Hostinger API notes for agents. Find operations with search; the inputSchema it returns is authoritative for request shapes. Run one with execute, or chain several with multi-execute.

Databases (web hosting, hosting_* operations)

• MySQL runs on the same server as the website. From the deployed app connect to host 127.0.0.1, port 3306. PHP may also use localhost (Unix socket). Node.js should use 127.0.0.1: localhost can resolve to IPv6 (::1) and not every database user has that grant.

• The host from hosting_databases_list (srvNNNN.hstgr.io) is only for connections from outside Hostinger, after hosting_databases_create-remote-connection. Never use it from the app.

• Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.

Asynchronous operations

• A success response often means "queued", not "done". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.

• hosting_websites_create -> poll hosting_websites_list-setups with the domain until status is completed (a few minutes); file, deploy and database calls return 404/409 before that.

• A Node.js deploy or hosting_nodejs_start-build -> poll hosting_get-deployment with the domain until the build state is completed or failed; a failed build comes back with its logs and failure analysis.

• wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.

• agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.

• Website deletion, database repair and domain contact changes finish in the background.

Credentials

• Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.

• Node.js apps read them from environment variables: set the full set with hosting_nodejs_replace-environment-variables (full replace; values are masked on read). Build-time variables (Next.js) need a new build afterwards.

• PHP apps read them from a config file on the server, outside the repository.

• Generate strong passwords and do not echo them back once stored.

Deploying from a shell

• The Hostinger CLI deploys a website in one command and links the directory: hostinger up <dir> --domain <domain> --format json (--yes replaces content, --create makes a site, --dry-run shows the plan). It never prompts without a terminal.

Deploying a website (this server only)

• hosting_deploy replaces the upload, archive-deploy, build, WordPress import/plugin/theme and Git operations named above. Give it a local directory (it detects static/PHP, Node.js, a WordPress site, plugin or theme and packs it itself), a local archive with type, or git: { repository, branch }. Do not run those operations by hand.

• A Node.js deploy returns a buildUuid at once and builds on the server. Poll hosting_get-deployment with the domain, pausing longer each time, until the build state is completed or failed. A failed build comes back with its logs and analysis: fix the cause and deploy again. It replaces the build, log and settings operations.

• Static, PHP, plugin and theme deploys are complete when hosting_deploy returns. A WordPress site import only starts: its files are extracted and the site is ready a few minutes later.

• Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.

Product updates

• For what is new at Hostinger (release notes, recent changes, new features), call changelog_list-entries, filtered by product and since. For what is coming (the roadmap), call it with status: upcoming. It needs no API token.

For end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server

Features and capabilities supported by this server

Functions exposed to the LLM to take actions

Interactive templates invoked by user choice

Contextual data attached and managed by the client