hostinger-api-mcp 1.6.2 → 1.7.1
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/README.md +27 -3
- package/gemini-extension.json +1 -1
- package/package.json +1 -1
- package/server.json +2 -2
- package/src/core/runtime.js +532 -1
- package/src/core/runtime.ts +540 -1
- package/src/core/tools/agency-hosting.js +68 -0
- package/src/core/tools/agency-hosting.ts +68 -0
- package/src/core/tools/all.js +92 -0
- package/src/core/tools/all.ts +92 -0
- package/src/core/tools/domains.js +24 -0
- package/src/core/tools/domains.ts +24 -0
- package/src/servers/agency-hosting.js +1 -1
- package/src/servers/agency-hosting.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/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/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 +58 -0
|
@@ -14,6 +14,74 @@ export interface OpenApiTool extends Tool {
|
|
|
14
14
|
}
|
|
15
15
|
|
|
16
16
|
const tools: OpenApiTool[] = [
|
|
17
|
+
{
|
|
18
|
+
"name": "agencyHosting_deployNodeStaticWebsite",
|
|
19
|
+
"topic": "agency-hosting",
|
|
20
|
+
"description": "Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.",
|
|
21
|
+
"method": "",
|
|
22
|
+
"path": "",
|
|
23
|
+
"inputSchema": {
|
|
24
|
+
"type": "object",
|
|
25
|
+
"properties": {
|
|
26
|
+
"domain": {
|
|
27
|
+
"type": "string",
|
|
28
|
+
"description": "Domain name of the Agency Plan website (e.g., example.com)"
|
|
29
|
+
},
|
|
30
|
+
"archivePath": {
|
|
31
|
+
"type": "string",
|
|
32
|
+
"description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
|
|
33
|
+
},
|
|
34
|
+
"removeArchive": {
|
|
35
|
+
"type": "boolean",
|
|
36
|
+
"description": "Whether to remove the local archive file after successful deployment (default: true)"
|
|
37
|
+
}
|
|
38
|
+
},
|
|
39
|
+
"required": [
|
|
40
|
+
"domain",
|
|
41
|
+
"archivePath"
|
|
42
|
+
]
|
|
43
|
+
},
|
|
44
|
+
"security": [],
|
|
45
|
+
"custom": true,
|
|
46
|
+
"templateFile": "deploy-node-static.template.js",
|
|
47
|
+
"templateFileTS": "deploy-node-static.template.ts",
|
|
48
|
+
"handlerMethod": "handleNodeStaticDeploy",
|
|
49
|
+
"group": "agency-hosting"
|
|
50
|
+
},
|
|
51
|
+
{
|
|
52
|
+
"name": "agencyHosting_deployPhpApplication",
|
|
53
|
+
"topic": "agency-hosting",
|
|
54
|
+
"description": "Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.",
|
|
55
|
+
"method": "",
|
|
56
|
+
"path": "",
|
|
57
|
+
"inputSchema": {
|
|
58
|
+
"type": "object",
|
|
59
|
+
"properties": {
|
|
60
|
+
"domain": {
|
|
61
|
+
"type": "string",
|
|
62
|
+
"description": "Domain name of the Agency Plan website (e.g., example.com)"
|
|
63
|
+
},
|
|
64
|
+
"archivePath": {
|
|
65
|
+
"type": "string",
|
|
66
|
+
"description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
|
|
67
|
+
},
|
|
68
|
+
"removeArchive": {
|
|
69
|
+
"type": "boolean",
|
|
70
|
+
"description": "Whether to remove the local archive file after successful deployment (default: true)"
|
|
71
|
+
}
|
|
72
|
+
},
|
|
73
|
+
"required": [
|
|
74
|
+
"domain",
|
|
75
|
+
"archivePath"
|
|
76
|
+
]
|
|
77
|
+
},
|
|
78
|
+
"security": [],
|
|
79
|
+
"custom": true,
|
|
80
|
+
"templateFile": "deploy-php-app.template.js",
|
|
81
|
+
"templateFileTS": "deploy-php-app.template.ts",
|
|
82
|
+
"handlerMethod": "handlePhpAppDeploy",
|
|
83
|
+
"group": "agency-hosting"
|
|
84
|
+
},
|
|
17
85
|
{
|
|
18
86
|
"name": "agency-hosting_listAvailableDatacentersForAnAgencyPlanOrderV1",
|
|
19
87
|
"description": "Lists the datacenters available for provisioning a new website on the given Agency Plan\nhosting order.\n\nEach datacenter includes a `pinger_url` you can ping from the client to measure round-trip\nlatency; comparing the results across datacenters lets you pick the nearest one (lowest\nping) before choosing its `code` as the `datacenter_code` when creating a website setup.",
|
package/src/core/tools/all.js
CHANGED
|
@@ -1,5 +1,73 @@
|
|
|
1
1
|
// Auto-generated tool list for group: all
|
|
2
2
|
export default [
|
|
3
|
+
{
|
|
4
|
+
"name": "agencyHosting_deployNodeStaticWebsite",
|
|
5
|
+
"topic": "agency-hosting",
|
|
6
|
+
"description": "Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.",
|
|
7
|
+
"method": "",
|
|
8
|
+
"path": "",
|
|
9
|
+
"inputSchema": {
|
|
10
|
+
"type": "object",
|
|
11
|
+
"properties": {
|
|
12
|
+
"domain": {
|
|
13
|
+
"type": "string",
|
|
14
|
+
"description": "Domain name of the Agency Plan website (e.g., example.com)"
|
|
15
|
+
},
|
|
16
|
+
"archivePath": {
|
|
17
|
+
"type": "string",
|
|
18
|
+
"description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
|
|
19
|
+
},
|
|
20
|
+
"removeArchive": {
|
|
21
|
+
"type": "boolean",
|
|
22
|
+
"description": "Whether to remove the local archive file after successful deployment (default: true)"
|
|
23
|
+
}
|
|
24
|
+
},
|
|
25
|
+
"required": [
|
|
26
|
+
"domain",
|
|
27
|
+
"archivePath"
|
|
28
|
+
]
|
|
29
|
+
},
|
|
30
|
+
"security": [],
|
|
31
|
+
"custom": true,
|
|
32
|
+
"templateFile": "deploy-node-static.template.js",
|
|
33
|
+
"templateFileTS": "deploy-node-static.template.ts",
|
|
34
|
+
"handlerMethod": "handleNodeStaticDeploy",
|
|
35
|
+
"group": "agency-hosting"
|
|
36
|
+
},
|
|
37
|
+
{
|
|
38
|
+
"name": "agencyHosting_deployPhpApplication",
|
|
39
|
+
"topic": "agency-hosting",
|
|
40
|
+
"description": "Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.",
|
|
41
|
+
"method": "",
|
|
42
|
+
"path": "",
|
|
43
|
+
"inputSchema": {
|
|
44
|
+
"type": "object",
|
|
45
|
+
"properties": {
|
|
46
|
+
"domain": {
|
|
47
|
+
"type": "string",
|
|
48
|
+
"description": "Domain name of the Agency Plan website (e.g., example.com)"
|
|
49
|
+
},
|
|
50
|
+
"archivePath": {
|
|
51
|
+
"type": "string",
|
|
52
|
+
"description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
|
|
53
|
+
},
|
|
54
|
+
"removeArchive": {
|
|
55
|
+
"type": "boolean",
|
|
56
|
+
"description": "Whether to remove the local archive file after successful deployment (default: true)"
|
|
57
|
+
}
|
|
58
|
+
},
|
|
59
|
+
"required": [
|
|
60
|
+
"domain",
|
|
61
|
+
"archivePath"
|
|
62
|
+
]
|
|
63
|
+
},
|
|
64
|
+
"security": [],
|
|
65
|
+
"custom": true,
|
|
66
|
+
"templateFile": "deploy-php-app.template.js",
|
|
67
|
+
"templateFileTS": "deploy-php-app.template.ts",
|
|
68
|
+
"handlerMethod": "handlePhpAppDeploy",
|
|
69
|
+
"group": "agency-hosting"
|
|
70
|
+
},
|
|
3
71
|
{
|
|
4
72
|
"name": "hosting_importWordpressWebsite",
|
|
5
73
|
"topic": "hosting",
|
|
@@ -1562,6 +1630,30 @@ export default [
|
|
|
1562
1630
|
],
|
|
1563
1631
|
"group": "domains"
|
|
1564
1632
|
},
|
|
1633
|
+
{
|
|
1634
|
+
"name": "domains_getDomainRenewalInformationV1",
|
|
1635
|
+
"description": "Retrieve renewal information for a specified domain, including its status and current\nexpiration date.\n\nUse this endpoint to build renewal automation and expiry monitoring for a single domain.",
|
|
1636
|
+
"method": "GET",
|
|
1637
|
+
"path": "/api/domains/v1/portfolio/{domain}/renewal",
|
|
1638
|
+
"inputSchema": {
|
|
1639
|
+
"type": "object",
|
|
1640
|
+
"properties": {
|
|
1641
|
+
"domain": {
|
|
1642
|
+
"type": "string",
|
|
1643
|
+
"description": "Domain name"
|
|
1644
|
+
}
|
|
1645
|
+
},
|
|
1646
|
+
"required": [
|
|
1647
|
+
"domain"
|
|
1648
|
+
]
|
|
1649
|
+
},
|
|
1650
|
+
"security": [
|
|
1651
|
+
{
|
|
1652
|
+
"apiToken": []
|
|
1653
|
+
}
|
|
1654
|
+
],
|
|
1655
|
+
"group": "domains"
|
|
1656
|
+
},
|
|
1565
1657
|
{
|
|
1566
1658
|
"name": "domains_updateDomainNameserversV1",
|
|
1567
1659
|
"description": "Set nameservers for a specified domain.\n\nBe aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable.\n\nUse this endpoint to configure custom DNS hosting for domains.",
|
package/src/core/tools/all.ts
CHANGED
|
@@ -14,6 +14,74 @@ export interface OpenApiTool extends Tool {
|
|
|
14
14
|
}
|
|
15
15
|
|
|
16
16
|
const tools: OpenApiTool[] = [
|
|
17
|
+
{
|
|
18
|
+
"name": "agencyHosting_deployNodeStaticWebsite",
|
|
19
|
+
"topic": "agency-hosting",
|
|
20
|
+
"description": "Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.",
|
|
21
|
+
"method": "",
|
|
22
|
+
"path": "",
|
|
23
|
+
"inputSchema": {
|
|
24
|
+
"type": "object",
|
|
25
|
+
"properties": {
|
|
26
|
+
"domain": {
|
|
27
|
+
"type": "string",
|
|
28
|
+
"description": "Domain name of the Agency Plan website (e.g., example.com)"
|
|
29
|
+
},
|
|
30
|
+
"archivePath": {
|
|
31
|
+
"type": "string",
|
|
32
|
+
"description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
|
|
33
|
+
},
|
|
34
|
+
"removeArchive": {
|
|
35
|
+
"type": "boolean",
|
|
36
|
+
"description": "Whether to remove the local archive file after successful deployment (default: true)"
|
|
37
|
+
}
|
|
38
|
+
},
|
|
39
|
+
"required": [
|
|
40
|
+
"domain",
|
|
41
|
+
"archivePath"
|
|
42
|
+
]
|
|
43
|
+
},
|
|
44
|
+
"security": [],
|
|
45
|
+
"custom": true,
|
|
46
|
+
"templateFile": "deploy-node-static.template.js",
|
|
47
|
+
"templateFileTS": "deploy-node-static.template.ts",
|
|
48
|
+
"handlerMethod": "handleNodeStaticDeploy",
|
|
49
|
+
"group": "agency-hosting"
|
|
50
|
+
},
|
|
51
|
+
{
|
|
52
|
+
"name": "agencyHosting_deployPhpApplication",
|
|
53
|
+
"topic": "agency-hosting",
|
|
54
|
+
"description": "Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.",
|
|
55
|
+
"method": "",
|
|
56
|
+
"path": "",
|
|
57
|
+
"inputSchema": {
|
|
58
|
+
"type": "object",
|
|
59
|
+
"properties": {
|
|
60
|
+
"domain": {
|
|
61
|
+
"type": "string",
|
|
62
|
+
"description": "Domain name of the Agency Plan website (e.g., example.com)"
|
|
63
|
+
},
|
|
64
|
+
"archivePath": {
|
|
65
|
+
"type": "string",
|
|
66
|
+
"description": "Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)"
|
|
67
|
+
},
|
|
68
|
+
"removeArchive": {
|
|
69
|
+
"type": "boolean",
|
|
70
|
+
"description": "Whether to remove the local archive file after successful deployment (default: true)"
|
|
71
|
+
}
|
|
72
|
+
},
|
|
73
|
+
"required": [
|
|
74
|
+
"domain",
|
|
75
|
+
"archivePath"
|
|
76
|
+
]
|
|
77
|
+
},
|
|
78
|
+
"security": [],
|
|
79
|
+
"custom": true,
|
|
80
|
+
"templateFile": "deploy-php-app.template.js",
|
|
81
|
+
"templateFileTS": "deploy-php-app.template.ts",
|
|
82
|
+
"handlerMethod": "handlePhpAppDeploy",
|
|
83
|
+
"group": "agency-hosting"
|
|
84
|
+
},
|
|
17
85
|
{
|
|
18
86
|
"name": "hosting_importWordpressWebsite",
|
|
19
87
|
"topic": "hosting",
|
|
@@ -1576,6 +1644,30 @@ const tools: OpenApiTool[] = [
|
|
|
1576
1644
|
],
|
|
1577
1645
|
"group": "domains"
|
|
1578
1646
|
},
|
|
1647
|
+
{
|
|
1648
|
+
"name": "domains_getDomainRenewalInformationV1",
|
|
1649
|
+
"description": "Retrieve renewal information for a specified domain, including its status and current\nexpiration date.\n\nUse this endpoint to build renewal automation and expiry monitoring for a single domain.",
|
|
1650
|
+
"method": "GET",
|
|
1651
|
+
"path": "/api/domains/v1/portfolio/{domain}/renewal",
|
|
1652
|
+
"inputSchema": {
|
|
1653
|
+
"type": "object",
|
|
1654
|
+
"properties": {
|
|
1655
|
+
"domain": {
|
|
1656
|
+
"type": "string",
|
|
1657
|
+
"description": "Domain name"
|
|
1658
|
+
}
|
|
1659
|
+
},
|
|
1660
|
+
"required": [
|
|
1661
|
+
"domain"
|
|
1662
|
+
]
|
|
1663
|
+
},
|
|
1664
|
+
"security": [
|
|
1665
|
+
{
|
|
1666
|
+
"apiToken": []
|
|
1667
|
+
}
|
|
1668
|
+
],
|
|
1669
|
+
"group": "domains"
|
|
1670
|
+
},
|
|
1579
1671
|
{
|
|
1580
1672
|
"name": "domains_updateDomainNameserversV1",
|
|
1581
1673
|
"description": "Set nameservers for a specified domain.\n\nBe aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable.\n\nUse this endpoint to configure custom DNS hosting for domains.",
|
|
@@ -345,6 +345,30 @@ export default [
|
|
|
345
345
|
],
|
|
346
346
|
"group": "domains"
|
|
347
347
|
},
|
|
348
|
+
{
|
|
349
|
+
"name": "domains_getDomainRenewalInformationV1",
|
|
350
|
+
"description": "Retrieve renewal information for a specified domain, including its status and current\nexpiration date.\n\nUse this endpoint to build renewal automation and expiry monitoring for a single domain.",
|
|
351
|
+
"method": "GET",
|
|
352
|
+
"path": "/api/domains/v1/portfolio/{domain}/renewal",
|
|
353
|
+
"inputSchema": {
|
|
354
|
+
"type": "object",
|
|
355
|
+
"properties": {
|
|
356
|
+
"domain": {
|
|
357
|
+
"type": "string",
|
|
358
|
+
"description": "Domain name"
|
|
359
|
+
}
|
|
360
|
+
},
|
|
361
|
+
"required": [
|
|
362
|
+
"domain"
|
|
363
|
+
]
|
|
364
|
+
},
|
|
365
|
+
"security": [
|
|
366
|
+
{
|
|
367
|
+
"apiToken": []
|
|
368
|
+
}
|
|
369
|
+
],
|
|
370
|
+
"group": "domains"
|
|
371
|
+
},
|
|
348
372
|
{
|
|
349
373
|
"name": "domains_updateDomainNameserversV1",
|
|
350
374
|
"description": "Set nameservers for a specified domain.\n\nBe aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable.\n\nUse this endpoint to configure custom DNS hosting for domains.",
|
|
@@ -359,6 +359,30 @@ const tools: OpenApiTool[] = [
|
|
|
359
359
|
],
|
|
360
360
|
"group": "domains"
|
|
361
361
|
},
|
|
362
|
+
{
|
|
363
|
+
"name": "domains_getDomainRenewalInformationV1",
|
|
364
|
+
"description": "Retrieve renewal information for a specified domain, including its status and current\nexpiration date.\n\nUse this endpoint to build renewal automation and expiry monitoring for a single domain.",
|
|
365
|
+
"method": "GET",
|
|
366
|
+
"path": "/api/domains/v1/portfolio/{domain}/renewal",
|
|
367
|
+
"inputSchema": {
|
|
368
|
+
"type": "object",
|
|
369
|
+
"properties": {
|
|
370
|
+
"domain": {
|
|
371
|
+
"type": "string",
|
|
372
|
+
"description": "Domain name"
|
|
373
|
+
}
|
|
374
|
+
},
|
|
375
|
+
"required": [
|
|
376
|
+
"domain"
|
|
377
|
+
]
|
|
378
|
+
},
|
|
379
|
+
"security": [
|
|
380
|
+
{
|
|
381
|
+
"apiToken": []
|
|
382
|
+
}
|
|
383
|
+
],
|
|
384
|
+
"group": "domains"
|
|
385
|
+
},
|
|
362
386
|
{
|
|
363
387
|
"name": "domains_updateDomainNameserversV1",
|
|
364
388
|
"description": "Set nameservers for a specified domain.\n\nBe aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable.\n\nUse this endpoint to configure custom DNS hosting for domains.",
|
package/src/servers/all.js
CHANGED
package/src/servers/all.ts
CHANGED
package/src/servers/billing.js
CHANGED
package/src/servers/billing.ts
CHANGED
package/src/servers/dns.js
CHANGED
package/src/servers/dns.ts
CHANGED
package/src/servers/domains.js
CHANGED
package/src/servers/domains.ts
CHANGED
package/src/servers/ecommerce.js
CHANGED
package/src/servers/ecommerce.ts
CHANGED
package/src/servers/horizons.js
CHANGED
package/src/servers/horizons.ts
CHANGED
package/src/servers/hosting.js
CHANGED
package/src/servers/hosting.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
|
@@ -4,6 +4,48 @@
|
|
|
4
4
|
*/
|
|
5
5
|
|
|
6
6
|
export interface APITools {
|
|
7
|
+
/**
|
|
8
|
+
* Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.
|
|
9
|
+
*/
|
|
10
|
+
"agencyHosting_deployNodeStaticWebsite": {
|
|
11
|
+
params: {
|
|
12
|
+
/**
|
|
13
|
+
* Domain name of the Agency Plan website (e.g., example.com)
|
|
14
|
+
*/
|
|
15
|
+
domain: string;
|
|
16
|
+
/**
|
|
17
|
+
* Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)
|
|
18
|
+
*/
|
|
19
|
+
archivePath: string;
|
|
20
|
+
/**
|
|
21
|
+
* Whether to remove the local archive file after successful deployment (default: true)
|
|
22
|
+
*/
|
|
23
|
+
removeArchive?: boolean;
|
|
24
|
+
};
|
|
25
|
+
response: any; // Response structure will depend on the API
|
|
26
|
+
};
|
|
27
|
+
|
|
28
|
+
/**
|
|
29
|
+
* Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.
|
|
30
|
+
*/
|
|
31
|
+
"agencyHosting_deployPhpApplication": {
|
|
32
|
+
params: {
|
|
33
|
+
/**
|
|
34
|
+
* Domain name of the Agency Plan website (e.g., example.com)
|
|
35
|
+
*/
|
|
36
|
+
domain: string;
|
|
37
|
+
/**
|
|
38
|
+
* Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it before proceeding using EXACTLY this naming pattern: directoryname_YYYYMMDD_HHMMSS.zip (e.g., mywebsite_20250115_143022.zip)
|
|
39
|
+
*/
|
|
40
|
+
archivePath: string;
|
|
41
|
+
/**
|
|
42
|
+
* Whether to remove the local archive file after successful deployment (default: true)
|
|
43
|
+
*/
|
|
44
|
+
removeArchive?: boolean;
|
|
45
|
+
};
|
|
46
|
+
response: any; // Response structure will depend on the API
|
|
47
|
+
};
|
|
48
|
+
|
|
7
49
|
/**
|
|
8
50
|
* 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. The username will be automatically resolved from the domain.
|
|
9
51
|
*/
|
|
@@ -945,6 +987,22 @@ Use this endpoint to make domain owner's information publicly visible.
|
|
|
945
987
|
response: any; // Response structure will depend on the API
|
|
946
988
|
};
|
|
947
989
|
|
|
990
|
+
/**
|
|
991
|
+
* Retrieve renewal information for a specified domain, including its status and current
|
|
992
|
+
expiration date.
|
|
993
|
+
|
|
994
|
+
Use this endpoint to build renewal automation and expiry monitoring for a single domain.
|
|
995
|
+
*/
|
|
996
|
+
"domains_getDomainRenewalInformationV1": {
|
|
997
|
+
params: {
|
|
998
|
+
/**
|
|
999
|
+
* Domain name
|
|
1000
|
+
*/
|
|
1001
|
+
domain: string;
|
|
1002
|
+
};
|
|
1003
|
+
response: any; // Response structure will depend on the API
|
|
1004
|
+
};
|
|
1005
|
+
|
|
948
1006
|
/**
|
|
949
1007
|
* Set nameservers for a specified domain.
|
|
950
1008
|
|