@hostinger/mcp 3.37.1 → 3.38.0
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.
- package/CHANGELOG.md +26 -0
- package/README.md +1 -1
- package/gemini-extension.json +1 -1
- package/package.json +1 -1
- package/server.json +2 -2
- package/skills/deploy-to-hosting/SKILL.md +1 -1
- package/skills/headless/VERSION +3 -3
- package/src/core/catalog.js +9 -1
- package/src/core/catalog.ts +11 -2
- package/src/core/instructions.agency-hosting.js +1 -1
- package/src/core/instructions.agency-hosting.ts +1 -1
- package/src/core/instructions.js +1 -1
- package/src/core/instructions.ts +1 -1
- package/src/core/runtime.js +2 -1483
- package/src/core/runtime.ts +4 -1483
- package/src/core/skills.js +3 -3
- package/src/core/skills.ts +3 -3
- package/src/core/tools/agency-hosting.ts +2 -0
- package/src/core/tools/agent-readiness.ts +2 -0
- package/src/core/tools/all.js +72 -330
- package/src/core/tools/all.ts +74 -330
- package/src/core/tools/billing.ts +2 -0
- package/src/core/tools/dns.ts +2 -0
- package/src/core/tools/domains.ts +2 -0
- package/src/core/tools/ecommerce.ts +2 -0
- package/src/core/tools/gpu.ts +2 -0
- package/src/core/tools/horizons.ts +2 -0
- package/src/core/tools/hosting.js +63 -327
- package/src/core/tools/hosting.ts +65 -327
- package/src/core/tools/mail.ts +2 -0
- package/src/core/tools/reach.ts +2 -0
- package/src/core/tools/vps.ts +2 -0
- package/src/core/tools/wordpress.ts +2 -0
- package/src/servers/agency-hosting.js +1 -1
- package/src/servers/agency-hosting.ts +1 -1
- package/src/servers/agent-readiness.js +1 -1
- package/src/servers/agent-readiness.ts +1 -1
- package/src/servers/all.js +1 -1
- package/src/servers/all.ts +1 -1
- package/src/servers/billing.js +1 -1
- package/src/servers/billing.ts +1 -1
- package/src/servers/dns.js +1 -1
- package/src/servers/dns.ts +1 -1
- package/src/servers/domains.js +1 -1
- package/src/servers/domains.ts +1 -1
- package/src/servers/ecommerce.js +1 -1
- package/src/servers/ecommerce.ts +1 -1
- package/src/servers/gpu.js +1 -1
- package/src/servers/gpu.ts +1 -1
- package/src/servers/horizons.js +1 -1
- package/src/servers/horizons.ts +1 -1
- package/src/servers/hosting.js +1 -1
- package/src/servers/hosting.ts +1 -1
- package/src/servers/mail.js +1 -1
- package/src/servers/mail.ts +1 -1
- package/src/servers/reach.js +1 -1
- package/src/servers/reach.ts +1 -1
- package/src/servers/vps.js +1 -1
- package/src/servers/vps.ts +1 -1
- package/src/servers/wordpress.js +1 -1
- package/src/servers/wordpress.ts +1 -1
- package/types.d.ts +0 -155
package/src/servers/ecommerce.js
CHANGED
package/src/servers/ecommerce.ts
CHANGED
package/src/servers/gpu.js
CHANGED
package/src/servers/gpu.ts
CHANGED
package/src/servers/horizons.js
CHANGED
package/src/servers/horizons.ts
CHANGED
package/src/servers/hosting.js
CHANGED
|
@@ -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.
|
|
7
|
+
startServer({ name: 'hostinger-hosting-mcp', version: '3.38.0', tools, instructions });
|
package/src/servers/hosting.ts
CHANGED
|
@@ -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.
|
|
7
|
+
startServer({ name: 'hostinger-hosting-mcp', version: '3.38.0', tools, instructions });
|
package/src/servers/mail.js
CHANGED
package/src/servers/mail.ts
CHANGED
package/src/servers/reach.js
CHANGED
package/src/servers/reach.ts
CHANGED
package/src/servers/vps.js
CHANGED
package/src/servers/vps.ts
CHANGED
package/src/servers/wordpress.js
CHANGED
package/src/servers/wordpress.ts
CHANGED
package/types.d.ts
CHANGED
|
@@ -312,161 +312,6 @@ export interface APITools {
|
|
|
312
312
|
response: any; // Response structure will depend on the API
|
|
313
313
|
};
|
|
314
314
|
|
|
315
|
-
/**
|
|
316
|
-
* Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end. The username will be automatically resolved from the domain.
|
|
317
|
-
*/
|
|
318
|
-
"hosting_import-wordpress-website": {
|
|
319
|
-
params: {
|
|
320
|
-
/**
|
|
321
|
-
* Domain name associated with the hosting account (e.g., example.com)
|
|
322
|
-
*/
|
|
323
|
-
domain: string;
|
|
324
|
-
/**
|
|
325
|
-
* Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)
|
|
326
|
-
*/
|
|
327
|
-
archivePath: string;
|
|
328
|
-
/**
|
|
329
|
-
* Absolute or relative path to a database dump file (.sql)
|
|
330
|
-
*/
|
|
331
|
-
databaseDump: string;
|
|
332
|
-
};
|
|
333
|
-
response: any; // Response structure will depend on the API
|
|
334
|
-
};
|
|
335
|
-
|
|
336
|
-
/**
|
|
337
|
-
* Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end.
|
|
338
|
-
*/
|
|
339
|
-
"hosting_deploy-wordpress-plugin": {
|
|
340
|
-
params: {
|
|
341
|
-
/**
|
|
342
|
-
* Domain name associated with the hosting account (e.g., example.com)
|
|
343
|
-
*/
|
|
344
|
-
domain: string;
|
|
345
|
-
/**
|
|
346
|
-
* WordPress plugin slug (e.g., omnisend)
|
|
347
|
-
*/
|
|
348
|
-
slug: string;
|
|
349
|
-
/**
|
|
350
|
-
* Absolute or relative path to the plugin directory containing all plugin files. node_modules, .git, symlinks and secret files (.env, keys, credentials) are not uploaded.
|
|
351
|
-
*/
|
|
352
|
-
pluginPath: string;
|
|
353
|
-
};
|
|
354
|
-
response: any; // Response structure will depend on the API
|
|
355
|
-
};
|
|
356
|
-
|
|
357
|
-
/**
|
|
358
|
-
* Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end.
|
|
359
|
-
*/
|
|
360
|
-
"hosting_deploy-wordpress-theme": {
|
|
361
|
-
params: {
|
|
362
|
-
/**
|
|
363
|
-
* Domain name associated with the hosting account (e.g., example.com)
|
|
364
|
-
*/
|
|
365
|
-
domain: string;
|
|
366
|
-
/**
|
|
367
|
-
* WordPress theme slug (e.g., twentytwentyfive)
|
|
368
|
-
*/
|
|
369
|
-
slug: string;
|
|
370
|
-
/**
|
|
371
|
-
* Absolute or relative path to the theme directory containing all theme files. node_modules, .git, symlinks and secret files (.env, keys, credentials) are not uploaded.
|
|
372
|
-
*/
|
|
373
|
-
themePath: string;
|
|
374
|
-
/**
|
|
375
|
-
* Whether to activate the theme after deployment (default: false)
|
|
376
|
-
*/
|
|
377
|
-
activate?: boolean;
|
|
378
|
-
};
|
|
379
|
-
response: any; // Response structure will depend on the API
|
|
380
|
-
};
|
|
381
|
-
|
|
382
|
-
/**
|
|
383
|
-
* Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. After deployment, use the hosting_list-js-deployments tool to check deployment status and track build progress.
|
|
384
|
-
*/
|
|
385
|
-
"hosting_deploy-js-application": {
|
|
386
|
-
params: {
|
|
387
|
-
/**
|
|
388
|
-
* Domain name associated with the hosting account (e.g., example.com)
|
|
389
|
-
*/
|
|
390
|
-
domain: string;
|
|
391
|
-
/**
|
|
392
|
-
* Absolute or relative path to the application archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive from it before proceeding. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory.
|
|
393
|
-
*/
|
|
394
|
-
archivePath: string;
|
|
395
|
-
/**
|
|
396
|
-
* Whether to remove the archive file after successful deployment (default: false)
|
|
397
|
-
*/
|
|
398
|
-
removeArchive?: boolean;
|
|
399
|
-
};
|
|
400
|
-
response: any; // Response structure will depend on the API
|
|
401
|
-
};
|
|
402
|
-
|
|
403
|
-
/**
|
|
404
|
-
* Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deploy-js-application instead. The tool uploads the archive to the website's file browser over TUS and triggers deployment; the archive is extracted and deployed directly without any build steps. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. The username will be automatically resolved from the domain.
|
|
405
|
-
*/
|
|
406
|
-
"hosting_deploy-static-website": {
|
|
407
|
-
params: {
|
|
408
|
-
/**
|
|
409
|
-
* Domain name associated with the hosting account (e.g., example.com)
|
|
410
|
-
*/
|
|
411
|
-
domain: string;
|
|
412
|
-
/**
|
|
413
|
-
* Absolute or relative path to the static website archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mystaticwebsite_20250115_143022.zip)
|
|
414
|
-
*/
|
|
415
|
-
archivePath: string;
|
|
416
|
-
/**
|
|
417
|
-
* Whether to remove the archive file after successful deployment (default: false)
|
|
418
|
-
*/
|
|
419
|
-
removeArchive?: boolean;
|
|
420
|
-
};
|
|
421
|
-
response: any; // Response structure will depend on the API
|
|
422
|
-
};
|
|
423
|
-
|
|
424
|
-
/**
|
|
425
|
-
* List javascript application deployments for checking their status. Use this tool when customer asks for the status of the deployment. This tool retrieves a paginated list of Node.js application deployments for a domain with optional filtering by deployment states.
|
|
426
|
-
*/
|
|
427
|
-
"hosting_list-js-deployments": {
|
|
428
|
-
params: {
|
|
429
|
-
/**
|
|
430
|
-
* Domain name associated with the hosting account (e.g., example.com)
|
|
431
|
-
*/
|
|
432
|
-
domain: string;
|
|
433
|
-
/**
|
|
434
|
-
* Page number for pagination (optional)
|
|
435
|
-
*/
|
|
436
|
-
page?: number;
|
|
437
|
-
/**
|
|
438
|
-
* Number of items per page (optional)
|
|
439
|
-
*/
|
|
440
|
-
perPage?: number;
|
|
441
|
-
/**
|
|
442
|
-
* Filter by deployment states (optional). Valid values: pending, completed, running, failed
|
|
443
|
-
*/
|
|
444
|
-
states?: array;
|
|
445
|
-
};
|
|
446
|
-
response: any; // Response structure will depend on the API
|
|
447
|
-
};
|
|
448
|
-
|
|
449
|
-
/**
|
|
450
|
-
* Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure.
|
|
451
|
-
*/
|
|
452
|
-
"hosting_show-js-deployment-logs": {
|
|
453
|
-
params: {
|
|
454
|
-
/**
|
|
455
|
-
* Domain name associated with the hosting account (e.g., example.com)
|
|
456
|
-
*/
|
|
457
|
-
domain: string;
|
|
458
|
-
/**
|
|
459
|
-
* Line from which to retrieve logs (optional, default 0)
|
|
460
|
-
*/
|
|
461
|
-
fromLine?: number;
|
|
462
|
-
/**
|
|
463
|
-
* UUID of the JavaScript deployment build
|
|
464
|
-
*/
|
|
465
|
-
buildUuid: string;
|
|
466
|
-
};
|
|
467
|
-
response: any; // Response structure will depend on the API
|
|
468
|
-
};
|
|
469
|
-
|
|
470
315
|
/**
|
|
471
316
|
* Tell Hostinger that something happened on this website, so Hostinger services such as hPanel can react to it. `event.name` picks the event and decides which `event.params` it takes. The call changes nothing on the website.
|
|
472
317
|
*/
|