@hostinger/mcp 3.39.0 → 3.39.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (45) hide show
  1. package/CHANGELOG.md +21 -0
  2. package/README.md +14 -8
  3. package/gemini-extension.json +1 -1
  4. package/package.json +1 -1
  5. package/server.json +2 -2
  6. package/skills/headless/VERSION +2 -2
  7. package/src/core/instructions.agency-hosting.js +1 -1
  8. package/src/core/instructions.agency-hosting.ts +1 -1
  9. package/src/core/instructions.js +1 -1
  10. package/src/core/instructions.ts +1 -1
  11. package/src/core/runtime.js +1 -1
  12. package/src/core/runtime.ts +1 -1
  13. package/src/core/tools/all.js +3 -3
  14. package/src/core/tools/all.ts +3 -3
  15. package/src/core/tools/mail.js +3 -3
  16. package/src/core/tools/mail.ts +3 -3
  17. package/src/servers/agency-hosting.js +1 -1
  18. package/src/servers/agency-hosting.ts +1 -1
  19. package/src/servers/agent-readiness.js +1 -1
  20. package/src/servers/agent-readiness.ts +1 -1
  21. package/src/servers/all.js +1 -1
  22. package/src/servers/all.ts +1 -1
  23. package/src/servers/billing.js +1 -1
  24. package/src/servers/billing.ts +1 -1
  25. package/src/servers/dns.js +1 -1
  26. package/src/servers/dns.ts +1 -1
  27. package/src/servers/domains.js +1 -1
  28. package/src/servers/domains.ts +1 -1
  29. package/src/servers/ecommerce.js +1 -1
  30. package/src/servers/ecommerce.ts +1 -1
  31. package/src/servers/gpu.js +1 -1
  32. package/src/servers/gpu.ts +1 -1
  33. package/src/servers/horizons.js +1 -1
  34. package/src/servers/horizons.ts +1 -1
  35. package/src/servers/hosting.js +1 -1
  36. package/src/servers/hosting.ts +1 -1
  37. package/src/servers/mail.js +1 -1
  38. package/src/servers/mail.ts +1 -1
  39. package/src/servers/reach.js +1 -1
  40. package/src/servers/reach.ts +1 -1
  41. package/src/servers/vps.js +1 -1
  42. package/src/servers/vps.ts +1 -1
  43. package/src/servers/wordpress.js +1 -1
  44. package/src/servers/wordpress.ts +1 -1
  45. package/types.d.ts +14 -8
package/CHANGELOG.md CHANGED
@@ -4,6 +4,27 @@ Generated at release time from the diff between the previous and current
4
4
  build. Tool changes are listed individually; everything else is summarised
5
5
  by area.
6
6
 
7
+ ## v3.39.2 — 2026-11-12
8
+
9
+ ### Operations
10
+
11
+ - Changed the description of `mail_api-tokens_create`
12
+ - Changed the description of `mail_api-tokens_revoke`
13
+ - Changed the description of `mail_api-tokens_list`
14
+
15
+ ### Also in this release
16
+
17
+ - Documentation: `README.md`
18
+ - Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
19
+ - Build and packaging: `types.d.ts`
20
+
21
+ ## v3.39.1 — 2026-11-12
22
+
23
+ ### Also in this release
24
+
25
+ - Bundled agent skills: `skills/headless/VERSION`
26
+ - Server instructions: 4 files
27
+
7
28
  ## v3.39.0 — 2026-11-12
8
29
 
9
30
  ### Operations
package/README.md CHANGED
@@ -2809,14 +2809,20 @@ order.
2809
2809
 
2810
2810
  #### mail_api-tokens_create
2811
2811
 
2812
- Create an API token for the given mail order. The token grants access
2813
- to the [Hostinger Email API](https://api.mail.hostinger.com/), where
2814
- you can provision and manage the mailboxes it is scoped to.
2812
+ Create an API token for the given mail order. Through the
2813
+ [Hostinger Mail API](https://api.mail.hostinger.com/), the token
2814
+ grants access to the mailboxes it is scoped to (for example, to read,
2815
+ search, send and organise email messages), without signing in with a
2816
+ mailbox password over IMAP, SMTP or webmail.
2817
+
2818
+ A token covers either all mailboxes of the order or only the ones you
2819
+ choose. Set `scope.has_all_mailboxes` to `true` to cover all current
2820
+ and future mailboxes, or to `false` and list specific mailboxes in
2821
+ `scope.mailbox_ids`.
2815
2822
 
2816
2823
  The plaintext token is returned only in this response, never again.
2817
- A maximum of 10 tokens can exist per order. Use
2818
- `scope.has_all_mailboxes` to cover all current and future mailboxes,
2819
- or list specific mailboxes in `scope.mailbox_ids`.
2824
+ Store it securely, because anyone who has it gets the same access. A
2825
+ maximum of 10 tokens can exist per order.
2820
2826
 
2821
2827
  - **Method**: `POST`
2822
2828
  - **Path**: `/api/mail/v1/orders/{orderId}/api-tokens`
@@ -2824,7 +2830,7 @@ or list specific mailboxes in `scope.mailbox_ids`.
2824
2830
  #### mail_api-tokens_revoke
2825
2831
 
2826
2832
  Revoke an API token. The token immediately loses access to the
2827
- [Hostinger Email API](https://api.mail.hostinger.com/). This action
2833
+ [Hostinger Mail API](https://api.mail.hostinger.com/). This action
2828
2834
  cannot be undone.
2829
2835
 
2830
2836
  - **Method**: `DELETE`
@@ -2833,7 +2839,7 @@ cannot be undone.
2833
2839
  #### mail_api-tokens_list
2834
2840
 
2835
2841
  Retrieve a paginated list of
2836
- [Hostinger Email API](https://api.mail.hostinger.com/) tokens across
2842
+ [Hostinger Mail API](https://api.mail.hostinger.com/) tokens across
2837
2843
  all your mail orders, optionally filtered by order. Plaintext tokens
2838
2844
  are never included; they are returned only when a token is created.
2839
2845
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hostinger-api-mcp",
3
- "version": "3.39.0",
3
+ "version": "3.39.2",
4
4
  "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
5
5
  "mcpServers": {
6
6
  "hostinger": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hostinger/mcp",
3
- "version": "3.39.0",
3
+ "version": "3.39.2",
4
4
  "mcpName": "io.github.hostinger/hostinger-api-mcp",
5
5
  "description": "MCP server for Hostinger API",
6
6
  "repository": {
package/server.json CHANGED
@@ -17,12 +17,12 @@
17
17
  "url": "https://github.com/hostinger/api-mcp-server",
18
18
  "source": "github"
19
19
  },
20
- "version": "3.39.0",
20
+ "version": "3.39.2",
21
21
  "packages": [
22
22
  {
23
23
  "registryType": "npm",
24
24
  "identifier": "@hostinger/mcp",
25
- "version": "3.39.0",
25
+ "version": "3.39.2",
26
26
  "transport": {
27
27
  "type": "stdio"
28
28
  },
@@ -1,3 +1,3 @@
1
- version=3.39.0
2
- commit=49930122d23b
1
+ version=3.39.2
2
+ commit=7bb99b69e47b
3
3
  built=2026-11-12
@@ -1,2 +1,2 @@
1
1
  // Auto-generated server instructions
2
- export default "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ export default "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nEmail\n- mail_* operations set up email (orders, mailboxes, aliases, forwarders); they cannot read or send messages.\n- To read, search, send or organise email in a mailbox, create a token with mail_api-tokens_create and use it with the Hostinger Mail API (https://api.mail.hostinger.com/) instead of asking for the mailbox password.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
@@ -1,3 +1,3 @@
1
1
  // Auto-generated server instructions
2
- const instructions: string = "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ const instructions: string = "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nEmail\n- mail_* operations set up email (orders, mailboxes, aliases, forwarders); they cannot read or send messages.\n- To read, search, send or organise email in a mailbox, create a token with mail_api-tokens_create and use it with the Hostinger Mail API (https://api.mail.hostinger.com/) instead of asking for the mailbox password.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
3
3
  export default instructions;
@@ -1,2 +1,2 @@
1
1
  // Auto-generated server instructions
2
- export default "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nDeploying a website (this server only)\n- 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.\n- 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.\n- 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.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ export default "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nEmail\n- mail_* operations set up email (orders, mailboxes, aliases, forwarders); they cannot read or send messages.\n- To read, search, send or organise email in a mailbox, create a token with mail_api-tokens_create and use it with the Hostinger Mail API (https://api.mail.hostinger.com/) instead of asking for the mailbox password.\n\nDeploying a website (this server only)\n- 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.\n- 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.\n- 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.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
@@ -1,3 +1,3 @@
1
1
  // Auto-generated server instructions
2
- const instructions: string = "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nDeploying a website (this server only)\n- 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.\n- 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.\n- 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.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
2
+ const instructions: string = "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.\n\nDatabases (web hosting, hosting_* operations)\n- 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.\n- 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.\n- Agency Plan (agency-hosting_* operations) database users are created for localhost; the PHP app connects there.\n\nAsynchronous operations\n- A success response often means \"queued\", not \"done\". Poll the matching read operation with backoff (seconds, then minutes). Never re-send the write.\n- 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.\n- A Node.js deploy or 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.\n- wordpress_installations_install and WordPress plugin/theme/core jobs -> poll wordpress_installations_list.\n- agency-hosting_website-setups_create -> poll agency-hosting_website-setups_status with setup_uuid; other Agency Plan jobs -> agency-hosting_websites_list-processes.\n- Website deletion, database repair and domain contact changes finish in the background.\n\nCredentials\n- Never write database passwords or API tokens into source code, client-side JavaScript or committed .env files.\n- 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.\n- PHP apps read them from a config file on the server, outside the repository.\n- Generate strong passwords and do not echo them back once stored.\n\nDeploying from a shell\n- 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.\n\nEmail\n- mail_* operations set up email (orders, mailboxes, aliases, forwarders); they cannot read or send messages.\n- To read, search, send or organise email in a mailbox, create a token with mail_api-tokens_create and use it with the Hostinger Mail API (https://api.mail.hostinger.com/) instead of asking for the mailbox password.\n\nDeploying a website (this server only)\n- 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.\n- 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.\n- 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.\n- Every deploy overwrites the site's contents: confirm the domain with the user before the first deploy to a site that already has content.\n\nProduct updates\n- 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.\n\nFor end-to-end site builds install the headless skill: npx skills add hostinger/api-mcp-server";
3
3
  export default instructions;
@@ -62,7 +62,7 @@ const GetSkillRequestSchema = z.object({
62
62
 
63
63
  /**
64
64
  * MCP Server for Hostinger API
65
- * Generated from OpenAPI spec version 2.14.0
65
+ * Generated from OpenAPI spec version 2.14.1
66
66
  */
67
67
  class MCPServer {
68
68
  constructor({ name, version, tools, instructions, skills = [] }) {
@@ -96,7 +96,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
96
96
 
97
97
  /**
98
98
  * MCP Server for Hostinger API
99
- * Generated from OpenAPI spec version 2.14.0
99
+ * Generated from OpenAPI spec version 2.14.1
100
100
  */
101
101
  class MCPServer {
102
102
  private readonly name: string;
@@ -10525,7 +10525,7 @@ export default [
10525
10525
  "readOnlyHint": false,
10526
10526
  "destructiveHint": false
10527
10527
  },
10528
- "description": "Create an API token for the given mail order. The token grants access\nto the [Hostinger Email API](https://api.mail.hostinger.com/), where\nyou can provision and manage the mailboxes it is scoped to.\n\nThe plaintext token is returned only in this response, never again.\nA maximum of 10 tokens can exist per order. Use\n`scope.has_all_mailboxes` to cover all current and future mailboxes,\nor list specific mailboxes in `scope.mailbox_ids`.",
10528
+ "description": "Create an API token for the given mail order. Through the\n[Hostinger Mail API](https://api.mail.hostinger.com/), the token\ngrants access to the mailboxes it is scoped to (for example, to read,\nsearch, send and organise email messages), without signing in with a\nmailbox password over IMAP, SMTP or webmail.\n\nA token covers either all mailboxes of the order or only the ones you\nchoose. Set `scope.has_all_mailboxes` to `true` to cover all current\nand future mailboxes, or to `false` and list specific mailboxes in\n`scope.mailbox_ids`.\n\nThe plaintext token is returned only in this response, never again.\nStore it securely, because anyone who has it gets the same access. A\nmaximum of 10 tokens can exist per order.",
10529
10529
  "method": "POST",
10530
10530
  "path": "/api/mail/v1/orders/{orderId}/api-tokens",
10531
10531
  "inputSchema": {
@@ -10583,7 +10583,7 @@ export default [
10583
10583
  "destructiveHint": true,
10584
10584
  "idempotentHint": true
10585
10585
  },
10586
- "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Email API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
10586
+ "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Mail API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
10587
10587
  "method": "DELETE",
10588
10588
  "path": "/api/mail/v1/api-tokens/{tokenId}",
10589
10589
  "inputSchema": {
@@ -10613,7 +10613,7 @@ export default [
10613
10613
  "readOnlyHint": true,
10614
10614
  "destructiveHint": false
10615
10615
  },
10616
- "description": "Retrieve a paginated list of\n[Hostinger Email API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
10616
+ "description": "Retrieve a paginated list of\n[Hostinger Mail API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
10617
10617
  "method": "GET",
10618
10618
  "path": "/api/mail/v1/api-tokens",
10619
10619
  "inputSchema": {
@@ -10544,7 +10544,7 @@ const tools: OpenApiTool[] = [
10544
10544
  "readOnlyHint": false,
10545
10545
  "destructiveHint": false
10546
10546
  },
10547
- "description": "Create an API token for the given mail order. The token grants access\nto the [Hostinger Email API](https://api.mail.hostinger.com/), where\nyou can provision and manage the mailboxes it is scoped to.\n\nThe plaintext token is returned only in this response, never again.\nA maximum of 10 tokens can exist per order. Use\n`scope.has_all_mailboxes` to cover all current and future mailboxes,\nor list specific mailboxes in `scope.mailbox_ids`.",
10547
+ "description": "Create an API token for the given mail order. Through the\n[Hostinger Mail API](https://api.mail.hostinger.com/), the token\ngrants access to the mailboxes it is scoped to (for example, to read,\nsearch, send and organise email messages), without signing in with a\nmailbox password over IMAP, SMTP or webmail.\n\nA token covers either all mailboxes of the order or only the ones you\nchoose. Set `scope.has_all_mailboxes` to `true` to cover all current\nand future mailboxes, or to `false` and list specific mailboxes in\n`scope.mailbox_ids`.\n\nThe plaintext token is returned only in this response, never again.\nStore it securely, because anyone who has it gets the same access. A\nmaximum of 10 tokens can exist per order.",
10548
10548
  "method": "POST",
10549
10549
  "path": "/api/mail/v1/orders/{orderId}/api-tokens",
10550
10550
  "inputSchema": {
@@ -10602,7 +10602,7 @@ const tools: OpenApiTool[] = [
10602
10602
  "destructiveHint": true,
10603
10603
  "idempotentHint": true
10604
10604
  },
10605
- "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Email API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
10605
+ "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Mail API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
10606
10606
  "method": "DELETE",
10607
10607
  "path": "/api/mail/v1/api-tokens/{tokenId}",
10608
10608
  "inputSchema": {
@@ -10632,7 +10632,7 @@ const tools: OpenApiTool[] = [
10632
10632
  "readOnlyHint": true,
10633
10633
  "destructiveHint": false
10634
10634
  },
10635
- "description": "Retrieve a paginated list of\n[Hostinger Email API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
10635
+ "description": "Retrieve a paginated list of\n[Hostinger Mail API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
10636
10636
  "method": "GET",
10637
10637
  "path": "/api/mail/v1/api-tokens",
10638
10638
  "inputSchema": {
@@ -163,7 +163,7 @@ export default [
163
163
  "readOnlyHint": false,
164
164
  "destructiveHint": false
165
165
  },
166
- "description": "Create an API token for the given mail order. The token grants access\nto the [Hostinger Email API](https://api.mail.hostinger.com/), where\nyou can provision and manage the mailboxes it is scoped to.\n\nThe plaintext token is returned only in this response, never again.\nA maximum of 10 tokens can exist per order. Use\n`scope.has_all_mailboxes` to cover all current and future mailboxes,\nor list specific mailboxes in `scope.mailbox_ids`.",
166
+ "description": "Create an API token for the given mail order. Through the\n[Hostinger Mail API](https://api.mail.hostinger.com/), the token\ngrants access to the mailboxes it is scoped to (for example, to read,\nsearch, send and organise email messages), without signing in with a\nmailbox password over IMAP, SMTP or webmail.\n\nA token covers either all mailboxes of the order or only the ones you\nchoose. Set `scope.has_all_mailboxes` to `true` to cover all current\nand future mailboxes, or to `false` and list specific mailboxes in\n`scope.mailbox_ids`.\n\nThe plaintext token is returned only in this response, never again.\nStore it securely, because anyone who has it gets the same access. A\nmaximum of 10 tokens can exist per order.",
167
167
  "method": "POST",
168
168
  "path": "/api/mail/v1/orders/{orderId}/api-tokens",
169
169
  "inputSchema": {
@@ -221,7 +221,7 @@ export default [
221
221
  "destructiveHint": true,
222
222
  "idempotentHint": true
223
223
  },
224
- "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Email API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
224
+ "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Mail API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
225
225
  "method": "DELETE",
226
226
  "path": "/api/mail/v1/api-tokens/{tokenId}",
227
227
  "inputSchema": {
@@ -251,7 +251,7 @@ export default [
251
251
  "readOnlyHint": true,
252
252
  "destructiveHint": false
253
253
  },
254
- "description": "Retrieve a paginated list of\n[Hostinger Email API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
254
+ "description": "Retrieve a paginated list of\n[Hostinger Mail API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
255
255
  "method": "GET",
256
256
  "path": "/api/mail/v1/api-tokens",
257
257
  "inputSchema": {
@@ -182,7 +182,7 @@ const tools: OpenApiTool[] = [
182
182
  "readOnlyHint": false,
183
183
  "destructiveHint": false
184
184
  },
185
- "description": "Create an API token for the given mail order. The token grants access\nto the [Hostinger Email API](https://api.mail.hostinger.com/), where\nyou can provision and manage the mailboxes it is scoped to.\n\nThe plaintext token is returned only in this response, never again.\nA maximum of 10 tokens can exist per order. Use\n`scope.has_all_mailboxes` to cover all current and future mailboxes,\nor list specific mailboxes in `scope.mailbox_ids`.",
185
+ "description": "Create an API token for the given mail order. Through the\n[Hostinger Mail API](https://api.mail.hostinger.com/), the token\ngrants access to the mailboxes it is scoped to (for example, to read,\nsearch, send and organise email messages), without signing in with a\nmailbox password over IMAP, SMTP or webmail.\n\nA token covers either all mailboxes of the order or only the ones you\nchoose. Set `scope.has_all_mailboxes` to `true` to cover all current\nand future mailboxes, or to `false` and list specific mailboxes in\n`scope.mailbox_ids`.\n\nThe plaintext token is returned only in this response, never again.\nStore it securely, because anyone who has it gets the same access. A\nmaximum of 10 tokens can exist per order.",
186
186
  "method": "POST",
187
187
  "path": "/api/mail/v1/orders/{orderId}/api-tokens",
188
188
  "inputSchema": {
@@ -240,7 +240,7 @@ const tools: OpenApiTool[] = [
240
240
  "destructiveHint": true,
241
241
  "idempotentHint": true
242
242
  },
243
- "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Email API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
243
+ "description": "Revoke an API token. The token immediately loses access to the\n[Hostinger Mail API](https://api.mail.hostinger.com/). This action\ncannot be undone.",
244
244
  "method": "DELETE",
245
245
  "path": "/api/mail/v1/api-tokens/{tokenId}",
246
246
  "inputSchema": {
@@ -270,7 +270,7 @@ const tools: OpenApiTool[] = [
270
270
  "readOnlyHint": true,
271
271
  "destructiveHint": false
272
272
  },
273
- "description": "Retrieve a paginated list of\n[Hostinger Email API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
273
+ "description": "Retrieve a paginated list of\n[Hostinger Mail API](https://api.mail.hostinger.com/) tokens across\nall your mail orders, optionally filtered by order. Plaintext tokens\nare never included; they are returned only when a token is created.",
274
274
  "method": "GET",
275
275
  "path": "/api/mail/v1/api-tokens",
276
276
  "inputSchema": {
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agency-hosting.js';
5
5
  import instructions from '../core/instructions.agency-hosting.js';
6
6
 
7
- startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.39.0', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.39.2', tools, instructions });
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agency-hosting.js';
5
5
  import instructions from '../core/instructions.agency-hosting.js';
6
6
 
7
- startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.39.0', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.39.2', tools, instructions });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agent-readiness.js';
5
5
 
6
- startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agent-readiness.js';
5
5
 
6
- startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.39.2', tools });
@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
5
5
  import instructions from '../core/instructions.js';
6
6
  import skills from '../core/skills.js';
7
7
 
8
- startServer({ name: 'hostinger-api-mcp', version: '3.39.0', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '3.39.2', tools, instructions, skills });
@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
5
5
  import instructions from '../core/instructions.js';
6
6
  import skills from '../core/skills.js';
7
7
 
8
- startServer({ name: 'hostinger-api-mcp', version: '3.39.0', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '3.39.2', tools, instructions, skills });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/billing.js';
5
5
 
6
- startServer({ name: 'hostinger-billing-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/billing.js';
5
5
 
6
- startServer({ name: 'hostinger-billing-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/dns.js';
5
5
 
6
- startServer({ name: 'hostinger-dns-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/dns.js';
5
5
 
6
- startServer({ name: 'hostinger-dns-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/domains.js';
5
5
 
6
- startServer({ name: 'hostinger-domains-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/domains.js';
5
5
 
6
- startServer({ name: 'hostinger-domains-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/ecommerce.js';
5
5
 
6
- startServer({ name: 'hostinger-ecommerce-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/ecommerce.js';
5
5
 
6
- startServer({ name: 'hostinger-ecommerce-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/gpu.js';
5
5
 
6
- startServer({ name: 'hostinger-gpu-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-gpu-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/gpu.js';
5
5
 
6
- startServer({ name: 'hostinger-gpu-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-gpu-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/horizons.js';
5
5
 
6
- startServer({ name: 'hostinger-horizons-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/horizons.js';
5
5
 
6
- startServer({ name: 'hostinger-horizons-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '3.39.2', tools });
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/hosting.js';
5
5
  import instructions from '../core/instructions.js';
6
6
 
7
- startServer({ name: 'hostinger-hosting-mcp', version: '3.39.0', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '3.39.2', tools, instructions });
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/hosting.js';
5
5
  import instructions from '../core/instructions.js';
6
6
 
7
- startServer({ name: 'hostinger-hosting-mcp', version: '3.39.0', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '3.39.2', tools, instructions });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/mail.js';
5
5
 
6
- startServer({ name: 'hostinger-mail-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/mail.js';
5
5
 
6
- startServer({ name: 'hostinger-mail-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/reach.js';
5
5
 
6
- startServer({ name: 'hostinger-reach-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/reach.js';
5
5
 
6
- startServer({ name: 'hostinger-reach-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/vps.js';
5
5
 
6
- startServer({ name: 'hostinger-vps-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/vps.js';
5
5
 
6
- startServer({ name: 'hostinger-vps-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/wordpress.js';
5
5
 
6
- startServer({ name: 'hostinger-wordpress-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '3.39.2', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/wordpress.js';
5
5
 
6
- startServer({ name: 'hostinger-wordpress-mcp', version: '3.39.0', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '3.39.2', tools });
package/types.d.ts CHANGED
@@ -6155,14 +6155,20 @@ order.
6155
6155
  };
6156
6156
 
6157
6157
  /**
6158
- * Create an API token for the given mail order. The token grants access
6159
- to the [Hostinger Email API](https://api.mail.hostinger.com/), where
6160
- you can provision and manage the mailboxes it is scoped to.
6158
+ * Create an API token for the given mail order. Through the
6159
+ [Hostinger Mail API](https://api.mail.hostinger.com/), the token
6160
+ grants access to the mailboxes it is scoped to (for example, to read,
6161
+ search, send and organise email messages), without signing in with a
6162
+ mailbox password over IMAP, SMTP or webmail.
6163
+
6164
+ A token covers either all mailboxes of the order or only the ones you
6165
+ choose. Set `scope.has_all_mailboxes` to `true` to cover all current
6166
+ and future mailboxes, or to `false` and list specific mailboxes in
6167
+ `scope.mailbox_ids`.
6161
6168
 
6162
6169
  The plaintext token is returned only in this response, never again.
6163
- A maximum of 10 tokens can exist per order. Use
6164
- `scope.has_all_mailboxes` to cover all current and future mailboxes,
6165
- or list specific mailboxes in `scope.mailbox_ids`.
6170
+ Store it securely, because anyone who has it gets the same access. A
6171
+ maximum of 10 tokens can exist per order.
6166
6172
  */
6167
6173
  "mail_api-tokens_create": {
6168
6174
  params: {
@@ -6184,7 +6190,7 @@ or list specific mailboxes in `scope.mailbox_ids`.
6184
6190
 
6185
6191
  /**
6186
6192
  * Revoke an API token. The token immediately loses access to the
6187
- [Hostinger Email API](https://api.mail.hostinger.com/). This action
6193
+ [Hostinger Mail API](https://api.mail.hostinger.com/). This action
6188
6194
  cannot be undone.
6189
6195
  */
6190
6196
  "mail_api-tokens_revoke": {
@@ -6199,7 +6205,7 @@ cannot be undone.
6199
6205
 
6200
6206
  /**
6201
6207
  * Retrieve a paginated list of
6202
- [Hostinger Email API](https://api.mail.hostinger.com/) tokens across
6208
+ [Hostinger Mail API](https://api.mail.hostinger.com/) tokens across
6203
6209
  all your mail orders, optionally filtered by order. Plaintext tokens
6204
6210
  are never included; they are returned only when a token is created.
6205
6211
  */