hostinger-api-mcp 3.11.0 → 3.12.0

package/CHANGELOG.md

@@ -4,6 +4,41 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v3.12.0 — 2026-10-27
+
+### Operations
+
+- Added `reach_integrations_disconnect-ecommerce-store` — Disconnect Ecommerce store
+- Added `reach_integrations_list-ecommerce-stores` — List Ecommerce stores
+- Added `reach_templates_email` — Get email template
+- Added `reach_integrations_list-connected-websites` — List connected websites
+- Added `reach_integrations_connect-ai-website-builder-site` — Connect AI Website Builder site
+- Added `reach_integrations_disconnect-ai-website-builder-site` — Disconnect AI Website Builder site
+- Added `reach_integrations_disconnect-wordpress-site` — Disconnect WordPress site
+- Changed the description of `reach_campaigns_get`
+- Changed the description of `reach_templates_list-email`
+
+### Also in this release
+
+- Documentation: `README.md`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Build and packaging: `types.d.ts`
+
+## v3.11.1 — 2026-10-27
+
+### Operations
+
+- Hid 1 operation from search (it still runs through `execute`): `hosting_nodejs_build-settings-from-repository`
+- Changed the description and input schema of `hosting_deploy`
+
+### Also in this release
+
+- Documentation: `README.md`
+- Bundled agent skills: `skills/deploy-to-hosting/SKILL.md`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Other files: `src/core/skills.js`, `src/core/skills.ts`
+- Build and packaging: `types.d.ts`
+
 ## v3.11.0 — 2026-10-27
 
 ### Also in this release

package/README.md

@@ -69,7 +69,7 @@ pnpm update -g @hostinger/mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server over every operation (410 total)
+- `hostinger-api-mcp` — unified server over every operation (416 total)
 - `hostinger-agency-hosting-mcp` — 42 operations for agency-hosting
 - `hostinger-agent-readiness-mcp` — 3 operations for agent-readiness
 - `hostinger-billing-mcp` — 9 operations for billing
@@ -77,9 +77,9 @@ This package installs the following MCP server commands:
 - `hostinger-domains-mcp` — 42 operations for domains
 - `hostinger-ecommerce-mcp` — 29 operations for ecommerce
 - `hostinger-horizons-mcp` — 6 operations for horizons
-- `hostinger-hosting-mcp` — 67 operations for hosting
+- `hostinger-hosting-mcp` — 66 operations for hosting
 - `hostinger-mail-mcp` — 38 operations for mail
-- `hostinger-reach-mcp` — 62 operations for reach
+- `hostinger-reach-mcp` — 69 operations for reach
 - `hostinger-vps-mcp` — 67 operations for vps
 - `hostinger-wordpress-mcp` — 40 operations for wordpress
 
@@ -1816,7 +1816,7 @@ interface in the provided website URL.
 
 #### hosting_deploy
 
-Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, pass appType and nodeVersion from the project's engines, plus outputDirectory and buildScript if the app has a build step). Git needs GitHub or GitLab connected once in hPanel.
+Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.
 
 - **Method**: `custom`
 - **Path**: `custom`
@@ -2248,21 +2248,6 @@ to it.
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/headless/agent-reports`
 
-#### hosting_nodejs_build-settings-from-repository
-
-Determine the build settings for a Node.js application from the package.json file of a branch
-in a Git repository. Use before starting a Git-source build to find out the auto-detected
-settings instead of guessing them.
-
-The repository is read through a Git installation: take `installation_uuid` from
-`List Git installations` and `owner` and `repository` from `List Git installation repositories`.
-
-Returns 422 when the installation is not found, the repository or branch is not found, or
-the branch has no package.json.
-
-- **Method**: `GET`
-- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/from-repository`
-
 #### hosting_nodejs_list-environment-variables
 
 Lists the Node.js environment variables currently set for the website. Values are always
@@ -3050,7 +3035,8 @@ Get a single campaign with its sender, subject, template reference, targeting an
 progress.
 
 This describes how the campaign was set up and how far it has got. For opens, clicks and
-unsubscribes use the campaign statistics endpoint.
+unsubscribes use the campaign statistics endpoint. The email content is not included: pass
+`template_uuid` to the get email template endpoint to read its HTML.
 
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/profiles/{profileUuid}/campaigns/{campaignUuid}`
@@ -3705,13 +3691,41 @@ a connected domain cannot be changed here. Returns the settings after the change
 - **Method**: `PATCH`
 - **Path**: `/api/reach/v1/profiles/{profileUuid}/settings`
 
+#### reach_integrations_disconnect-ecommerce-store
+
+Disconnect an eCommerce store from the profile.
+
+Reach stops receiving the store's customers and orders, and its products and coupons are
+removed from Reach; contacts and past orders stay. Take `store_id` from the list eCommerce
+stores endpoint; for a store that is `connected_to_other_profile`, call this with that
+profile. Also succeeds when the store is not connected to this profile, so success is not
+proof that anything was disconnected. Confirm the store and the plan with the customer
+before calling.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/ecommerce/stores/{storeId}`
+
+#### reach_integrations_list-ecommerce-stores
+
+Get all of the customer's Hostinger eCommerce stores, each with its `store_id` and
+`connection_status` for the profile in the path.
+
+A store is connected to at most one profile. `connected_to_other_profile` does not name that
+profile - call this for each profile to find it. The list is empty, not an error, when the
+eCommerce service cannot be reached. Pass `store_id` to the disconnect eCommerce store
+endpoint. Connecting an AI Website Builder site connects the store selling on it.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/ecommerce/stores`
+
 #### reach_templates_list-email
 
 Get a list of the email templates in a profile, most recently updated first.
 
 Templates are the reusable email bodies a campaign is built from. The list is not paginated
-and only the metadata is returned - the template content itself is not exposed. Use the
-`uuid` of a template as the `template_uuid` when creating a campaign.
+and only the metadata is returned, without the HTML content. Use the `uuid` of a template
+as the `template_uuid` when creating a campaign. To read one template's HTML use the get
+email template endpoint, and only when the content itself is needed.
 
 - **Method**: `GET`
 - **Path**: `/api/reach/v1/profiles/{profileUuid}/templates`
@@ -3727,6 +3741,71 @@ reference it as the `template_uuid` of a campaign.
 - **Method**: `POST`
 - **Path**: `/api/reach/v1/profiles/{profileUuid}/templates`
 
+#### reach_templates_email
+
+Get one email template of the profile with its full HTML in `template_content`.
+
+A campaign's email content is its template: to read what a campaign sends, get the campaign
+and pass its `template_uuid` here. The HTML can be large, so fetch it only when the content
+itself is needed, never to browse or pick templates - the list email templates endpoint does
+that without content. Personalization tags such as `{{name}}` come back unrendered.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/templates/{templateUuid}`
+
+#### reach_integrations_list-connected-websites
+
+Get the websites connected to the profile, each with its `domain` and `platform_type`.
+
+A domain is connected to at most one profile, so to find which plan a site is on, call this
+for each profile. Only connected sites are listed, not every website the customer owns, and
+eCommerce stores are not included - use the list eCommerce stores endpoint for those. Pass
+`domain` to the disconnect WordPress site or disconnect AI Website Builder site endpoint.
+
+- **Method**: `GET`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/websites`
+
+#### reach_integrations_connect-ai-website-builder-site
+
+Connect an AI Website Builder site the customer built manually to the profile, so its
+subscribers flow into Reach.
+
+Fails with not found when the customer owns no AI Website Builder site with that domain.
+Fails with `DOMAIN_ALREADY_EXISTS` when the domain is connected to any profile - to move a
+site to another plan, disconnect it from the old profile first - and with
+`WEBSITE_CONNECTION_ALREADY_EXISTS` when this profile already has an AI Website Builder site.
+The eCommerce store selling on the site, if it is not connected anywhere, is connected too.
+WordPress sites and sites made with the agentic AI Website Builder cannot be connected here.
+
+- **Method**: `POST`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/websites/website-builder`
+
+#### reach_integrations_disconnect-ai-website-builder-site
+
+Disconnect an AI Website Builder site from the profile; the site stops sending subscribers
+to Reach.
+
+Take `domain` from the list connected websites endpoint. Works for a site that was already
+deleted in the builder. Fails with not found when the domain is not connected to this
+profile. Contacts and any connected eCommerce store stay. The site stays disconnected until
+it is connected again, so confirm the site and the plan with the customer before calling.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/websites/website-builder`
+
+#### reach_integrations_disconnect-wordpress-site
+
+Disconnect a WordPress site from the profile.
+
+The Reach plugin on the site stops sending subscribers and store data, and the site's
+products and coupons are removed from Reach; contacts and past orders stay. Take `domain`
+from the list connected websites endpoint. Fails with not found when the domain is not
+connected to this profile. This cannot be undone through the API - the customer reconnects
+from the WordPress plugin - so confirm the site and the plan with the customer before calling.
+
+- **Method**: `DELETE`
+- **Path**: `/api/reach/v1/profiles/{profileUuid}/websites/wordpress`
+
 ### `hostinger-vps-mcp`
 
 #### vps_data-centers_list

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "3.11.0",
+  "version": "3.12.0",
   "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
   "mcpServers": {
     "hostinger": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "3.11.0",
+  "version": "3.12.0",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/hostinger/api-mcp-server",
     "source": "github"
   },
-  "version": "3.11.0",
+  "version": "3.12.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "3.11.0",
+      "version": "3.12.0",
       "transport": {
         "type": "stdio"
       },

package/skills/deploy-to-hosting/SKILL.md

@@ -86,7 +86,7 @@ Local files on the hosted server, deployed from an upload (step 2):
 
 On both the local and the hosted server, `hosting_deploy` with `git: { repository: "owner/name", branch }` does all of it: it finds the Git installation that can reach the repository and deploys it as the `type` you give. Always pass `type: "static"` or `"nodejs"` unless the site already runs a Node.js app (or you pass Node.js settings such as `appType`): a new site is not detected as Node.js, and a Node.js repository deployed as static would publish its source. Then:
 - **PHP and static sites:** saves the auto-deployment settings, which deploys the branch immediately and again on every push;
-- **Node.js sites:** starts a build of the branch with the stored build settings; later pushes build the same way. A Git deploy has nothing to detect from, so when none are stored pass `appType` and `nodeVersion` (from `engines` in `package.json`), plus `outputDirectory` and `buildScript` if the app has a build step; they are stored for those pushes.
+- **Node.js sites:** starts a build of the branch with the stored build settings; later pushes build the same way. When none are stored, they are detected from the branch's `package.json` and stored for those pushes; pass `appType`, `nodeVersion`, `outputDirectory`, `buildScript` or `entryFile` to override them (a compiled app still needs `entryFile`).
 
 With no active installation it stops and says so: the user connects GitHub or GitLab once in hPanel under Websites → Manage → Advanced → Git; there is no API for that step. Confirm with `hosting_get-deployment`, which returns the stored `gitAutoDeployment`.
 

package/src/core/runtime.js

@@ -66,7 +66,7 @@ const GetSkillRequestSchema = z.object({
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 2.3.0
+ * Generated from OpenAPI spec version 2.4.0
  */
 class MCPServer {
   constructor({ name, version, tools, instructions, skills = [] }) {
@@ -543,15 +543,29 @@ class MCPServer {
     return this.executeApiCall(tool, params);
   }
 
-  // The website for a domain, matched exactly (the list endpoint filters by substring).
+  // The website for a domain, matched exactly. The list endpoint filters by substring and pages its
+  // results, so a short domain can match many sites: read pages until the exact one turns up or a page
+  // comes back short, up to a limit.
   async findWebsite(domain) {
-    const response = await this.callOperation('hosting_websites_list', { domain });
-    const sites = response && Array.isArray(response.data) ? response.data : [];
-    const site = sites.find((website) => website.domain && website.domain.toLowerCase() === domain.toLowerCase());
-    if (!site) {
-      throw new Error('No website found for domain: ' + domain);
+    const perPage = 100;
+    const maxPages = 10;
+    for (let page = 1; page <= maxPages; page++) {
+      const response = await this.callOperation('hosting_websites_list', { domain, page, per_page: perPage });
+      const sites = response && Array.isArray(response.data) ? response.data : [];
+      const site = sites.find((website) => website.domain && website.domain.toLowerCase() === domain.toLowerCase());
+      if (site) {
+        // Agency Plan (U4S) websites come back without a username, and every later call would fail with
+        // an unclear API error.
+        if (typeof site.username !== 'string') {
+          throw new Error(site.domain + ' is an Agency Plan website: Git deploys and build status here work only for Shared and Cloud hosting websites. Use the agency-hosting operations for it.');
+        }
+        return site;
+      }
+      if (sites.length < perPage) {
+        break;
+      }
     }
-    return site;
+    throw new Error('No website found for domain: ' + domain);
   }
 
   hosting_deploy_types = ['static', 'nodejs', 'wordpress-site', 'wordpress-plugin', 'wordpress-theme'];
@@ -760,9 +774,11 @@ class MCPServer {
   // directory, and the API stores them as null, so a missing one is sent as null. Detection supplies
   // the build script but only guesses a root-level entry file, so a compiled app (TypeScript) must
   // pass entryFile.
-  // storedSettings tells base apart: settings stored for the site (Git deploy) belong to whatever
-  // framework it ran before, so a different appType starts from a clean build step, while settings
-  // detected from the project itself (archive deploy) are always right to keep.
+  // An explicit null for outputDirectory, buildScript or entryFile clears the stored value, so an app
+  // can drop a build step it no longer has.
+  // storedSettings tells base apart: settings stored for the site or detected from a Git branch (Git
+  // deploy) belong to the framework they were stored or detected for, so a different appType starts
+  // from a clean build step, while settings detected from the archive being deployed are kept.
   hosting_deploy_nodeSettings(base, params, storedSettings) {
     const given = base || {};
     const appType = params.appType ?? given.app_type;
@@ -771,6 +787,7 @@ class MCPServer {
     if (appType === undefined || appType === null) {
       throw new Error("Missing Node.js build setting: appType. Pass it to hosting_deploy, with outputDirectory and buildScript when the app has a build step; read them from the project's package.json.");
     }
+    const cleared = (name) => name in params && params[name] === null;
     const optional = {
       entry_file: params.entryFile ?? stored.entry_file,
       package_manager: params.packageManager ?? stored.package_manager,
@@ -779,9 +796,10 @@ class MCPServer {
       node_version: params.nodeVersion ?? stored.node_version ?? 22,
       app_type: appType,
       root_directory: params.rootDirectory ?? stored.root_directory ?? '.',
-      output_directory: params.outputDirectory ?? stored.output_directory ?? null,
-      build_script: params.buildScript ?? stored.build_script ?? null,
+      output_directory: cleared('outputDirectory') ? null : params.outputDirectory ?? stored.output_directory ?? null,
+      build_script: cleared('buildScript') ? null : params.buildScript ?? stored.build_script ?? null,
       ...Object.fromEntries(Object.entries(optional).filter(([, value]) => value !== undefined && value !== null)),
+      ...(cleared('entryFile') ? { entry_file: null } : {}),
     };
   }
 
@@ -829,6 +847,9 @@ class MCPServer {
     // Read only now that git is known to be an object.
     if (git !== undefined) {
       this.hosting_deploy_gitDirectory(git);
+      if (git.installationUuid !== undefined && (typeof git.installationUuid !== 'string' || git.installationUuid === '')) {
+        throw new Error('git.installationUuid must be a non-empty string when provided');
+      }
     }
   }
 
@@ -1058,23 +1079,59 @@ class MCPServer {
     };
   }
 
-  // The Git installation that can reach owner/name (GitLab owners may contain slashes).
-  async hosting_deploy_findRepository(fullName) {
+  // The Git installation that can reach owner/name (GitLab owners may contain slashes). Every active
+  // installation is checked, not just until the first match: a GitHub and a GitLab mirror can share a
+  // path, the installations come in no set order, and the same request must not deploy one repository
+  // one time and the other the next, overwriting the site. With an installation given, the name is taken as it is: the repository list stops at 500 entries, so a
+  // repository past that cannot be found by searching it.
+  async hosting_deploy_findRepository(fullName, installationUuid) {
     if (!fullName.includes('/')) {
       throw new Error('git.repository must be given as owner/name');
     }
+    if (installationUuid !== undefined) {
+      const slash = fullName.lastIndexOf('/');
+      const owner = fullName.slice(0, slash);
+      const repository = fullName.slice(slash + 1);
+      if (owner === '' || repository === '') {
+        throw new Error('git.repository must be given as owner/name');
+      }
+      return { installationUuid, owner, repository };
+    }
     const installations = await this.callOperation('hosting_git_list-installations', { status: 'active' });
     if (!Array.isArray(installations) || installations.length === 0) {
       throw new Error('No active Git installation. Connect GitHub or GitLab once in hPanel (Websites, Manage, Advanced, Git), then try again.');
     }
+    // The API returns at most this many repositories per installation. A full list without the
+    // repository may still hold it past the cut, so a match elsewhere cannot be trusted to be the only one.
+    const repositoryLimit = 500;
+    const truncated = [];
+    const matches = [];
     for (const installation of installations) {
-      const repositories = await this.callOperation('hosting_git_list-installation-repositories', { uuid: installation.uuid });
-      const repo = (Array.isArray(repositories) ? repositories : []).find((candidate) => String(candidate.full_name).toLowerCase() === fullName.toLowerCase());
+      const response = await this.callOperation('hosting_git_list-installation-repositories', { uuid: installation.uuid });
+      const repositories = Array.isArray(response) ? response : [];
+      const repo = repositories.find((candidate) => String(candidate.full_name).toLowerCase() === fullName.toLowerCase());
       if (repo) {
-        return { installationUuid: installation.uuid, owner: repo.owner, repository: repo.name };
+        matches.push({ installation, installationUuid: installation.uuid, owner: repo.owner, repository: repo.name });
+      } else if (repositories.length >= repositoryLimit) {
+        truncated.push(installation);
+      }
+    }
+    const describe = (installation) => (typeof installation.provider === 'string' ? installation.provider : 'git') + ' account ' + (typeof installation.account_login === 'string' ? installation.account_login : '?') + ' (installation ' + installation.uuid + ')';
+    if (matches.length > 1) {
+      throw new Error('Repository ' + fullName + ' is in ' + matches.length + ' of your Git installations: ' + matches.map((match) => describe(match.installation)).join('; ') + '. Pass git.installationUuid to say which one to deploy.');
+    }
+    if (matches.length === 1) {
+      if (truncated.length > 0) {
+        throw new Error('Repository ' + fullName + ' is in ' + describe(matches[0].installation) + ', but it may also be in ' + truncated.map(describe).join('; ') + ': repository lists stop at the first ' + repositoryLimit + '. Pass git.installationUuid to say which one to deploy.');
       }
+      const { installationUuid, owner, repository } = matches[0];
+      return { installationUuid, owner, repository };
+    }
+    const notFound = 'Repository ' + fullName + ' was not found in your ' + installations.length + ' active Git installation(s). Check the name, or give the Git provider access to it in hPanel (Websites, Manage, Advanced, Git).';
+    if (truncated.length > 0) {
+      throw new Error(notFound + ' An installation lists only its first ' + repositoryLimit + ' repositories: if it has more, pass git.installationUuid (from hosting_git_list-installations) to name the repository directly.');
     }
-    throw new Error('Repository ' + fullName + ' was not found in your ' + installations.length + ' active Git installation(s). Check the name, or give the Git provider access to it in hPanel (Websites, Manage, Advanced, Git).');
+    throw new Error(notFound);
   }
 
   // What a Git deploy is. There are no local files to look at, so guessing is dangerous: a Node.js
@@ -1101,7 +1158,15 @@ class MCPServer {
     if (type === 'nodejs' && directory !== '') {
       throw new Error('git.directory is for static deploys: a Node.js build has no target folder');
     }
-    const repo = await this.hosting_deploy_findRepository(git.repository);
+    // On these sites saving auto-deployment settings clones nothing, so a static deploy would report
+    // success and publish nothing.
+    if (type === 'static' && website.website_type === 'nodejs') {
+      throw new Error('This website runs a Node.js app: deploy it with type nodejs, or leave type out. Saving Git settings on a Node.js website does not deploy anything.');
+    }
+    if (type === 'static' && website.website_type === 'builder') {
+      throw new Error('This is a Website Builder website, which cannot deploy from Git: saving Git settings on it does not deploy anything.');
+    }
+    const repo = await this.hosting_deploy_findRepository(git.repository, git.installationUuid);
 
     if (type === 'static') {
       // Saving the settings deploys the branch now and again on every push.
@@ -1121,9 +1186,31 @@ class MCPServer {
         throw error;
       }
     }
-    const settings = this.hosting_deploy_nodeSettings(stored, params, true);
-    if (this.hosting_deploy_hasNodeOverrides(params)) {
-      // Later pushes build with the stored settings, not with this request: keep what was given.
+    // The API can return all-null settings, which mean nothing is stored.
+    const hasStored = stored !== null && typeof stored === 'object' && stored.app_type !== null && stored.app_type !== undefined;
+    let settings;
+    if (hasStored) {
+      settings = this.hosting_deploy_nodeSettings(stored, params, true);
+    } else {
+      // A first deploy: detect the settings from the branch's package.json. The request's settings beat
+      // them, and a different appType drops the build step detected for the other framework.
+      let detected = null;
+      try {
+        detected = await this.callOperation('hosting_nodejs_build-settings-from-repository', {
+          username, domain, owner: repo.owner, repository: repo.repository, branch: git.branch, installation_uuid: repo.installationUuid,
+        });
+      } catch (error) {
+        if (!(error instanceof ApiExecutionError && error.status === 422)) {
+          throw error;
+        }
+        if (params.appType === undefined || params.appType === null) {
+          throw new Error('No Node.js build settings could be detected from the ' + git.branch + ' branch (' + this.formatToolError(error) + '). Pass appType, with outputDirectory and buildScript when the app has a build step, or deploy with type static if the branch has no Node.js app.');
+        }
+      }
+      settings = this.hosting_deploy_nodeSettings(detected, params, true);
+    }
+    if (!hasStored || this.hosting_deploy_hasNodeOverrides(params)) {
+      // Later pushes build with the stored settings, not with this request: keep what was given or detected.
       await this.callOperation('hosting_nodejs_update-build-settings', { username, domain, ...settings });
     }
     const build = await this.callOperation('hosting_nodejs_start-build', {
@@ -1141,10 +1228,11 @@ class MCPServer {
       // Local checks first, so a bad path fails before any request is made.
       const type = this.hosting_deploy_resolveType(params);
       const website = await this.findWebsite(domain);
-      return this.hosting_deploy_fromPath(website.username, domain, type, params);
+      return this.hosting_deploy_fromPath(website.username, website.domain, type, params);
     }
+    // The lookup ignores case: the API calls and the result use the website's own spelling.
     const website = await this.findWebsite(domain);
-    return this.hosting_deploy_fromGit(website, domain, git, params);
+    return this.hosting_deploy_fromGit(website, website.domain, git, params);
   }
 
   // The failure analysis re-runs on every call and is limited to 5 a minute, so keep one request per
@@ -1190,9 +1278,9 @@ class MCPServer {
   }
 
   async handleHostingGetDeployment(params) {
-    const { domain, buildUuid, fromLine } = params;
+    const { domain: requestedDomain, buildUuid, fromLine } = params;
 
-    if (!domain || typeof domain !== 'string') {
+    if (!requestedDomain || typeof requestedDomain !== 'string') {
       throw new Error('domain is required and must be a string');
     }
     if (buildUuid !== undefined && (typeof buildUuid !== 'string' || buildUuid === '')) {
@@ -1202,7 +1290,8 @@ class MCPServer {
       throw new Error('fromLine must be a non-negative integer when provided');
     }
 
-    const { username } = await this.findWebsite(domain);
+    // The lookup ignores case: from here on use the website's own spelling, so one site has one analysis cache key.
+    const { username, domain } = await this.findWebsite(requestedDomain);
     const target = { username, domain };
 
     const gitSettings = await this.callOperation('hosting_git_auto-deployment-settings', target);