hostinger-api-mcp 1.5.1 → 1.5.3

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/types.d.ts CHANGED
@@ -159,6 +159,258 @@ export interface APITools {
159
159
  response: any; // Response structure will depend on the API
160
160
  };
161
161
 
162
+ /**
163
+ * Lists the datacenters available for provisioning a new website on the given Agency Plan
164
+ hosting order.
165
+
166
+ Each datacenter includes a `pinger_url` you can ping from the client to measure round-trip
167
+ latency; comparing the results across datacenters lets you pick the nearest one (lowest
168
+ ping) before choosing its `code` as the `datacenter_code` when creating a website setup.
169
+ */
170
+ "agency-hosting_listAvailableDatacentersForAnAgencyPlanOrderV1": {
171
+ params: {
172
+ /**
173
+ * Agency Plan order ID
174
+ */
175
+ order_id: number;
176
+ };
177
+ response: any; // Response structure will depend on the API
178
+ };
179
+
180
+ /**
181
+ * Changes the primary domain for an Agency Plan website.
182
+
183
+ Provide the current domain in the path and the new domain in the request body.
184
+ Set domain to null to revert to the temporary domain.
185
+ */
186
+ "agency-hosting_changeAgencyPlanWebsiteDomainV1": {
187
+ params: {
188
+ /**
189
+ * Agency Plan website UID
190
+ */
191
+ website_uid: string;
192
+ /**
193
+ * Current domain name to change from
194
+ */
195
+ from_domain: string;
196
+ /**
197
+ * New domain to assign to the website. Set to null to revert to the temporary domain.
198
+ */
199
+ domain: string;
200
+ };
201
+ response: any; // Response structure will depend on the API
202
+ };
203
+
204
+ /**
205
+ * Links a domain to the specified Agency Plan website so it can serve traffic for that domain.
206
+ */
207
+ "agency-hosting_linkDomainToAgencyPlanWebsiteV1": {
208
+ params: {
209
+ /**
210
+ * Agency Plan website UID
211
+ */
212
+ website_uid: string;
213
+ /**
214
+ * Fully qualified domain name to link to the website
215
+ */
216
+ domain: string;
217
+ };
218
+ response: any; // Response structure will depend on the API
219
+ };
220
+
221
+ /**
222
+ * Returns a paginated list of domains associated with Agency Plan websites accessible to the authenticated client.
223
+
224
+ Use the website_uuids filter to narrow results to specific websites.
225
+ */
226
+ "agency-hosting_listAgencyPlanDomainsV1": {
227
+ params: {
228
+ /**
229
+ * Page number
230
+ */
231
+ page?: number;
232
+ /**
233
+ * Number of items per page
234
+ */
235
+ per_page?: number;
236
+ /**
237
+ * Filter by website UIDs
238
+ */
239
+ website_uuids?: array;
240
+ };
241
+ response: any; // Response structure will depend on the API
242
+ };
243
+
244
+ /**
245
+ * Unlinks a domain from the specified Agency Plan website.
246
+
247
+ The website stops serving traffic on this domain immediately.
248
+
249
+ Website files and database are preserved, and any other linked domains remain accessible.
250
+
251
+ If this is the only domain on the website, unlinking leaves the website without an accessible domain.
252
+ */
253
+ "agency-hosting_unlinkDomainFromAgencyPlanWebsiteV1": {
254
+ params: {
255
+ /**
256
+ * Agency Plan website UID
257
+ */
258
+ website_uid: string;
259
+ /**
260
+ * Domain name
261
+ */
262
+ domain: string;
263
+ };
264
+ response: any; // Response structure will depend on the API
265
+ };
266
+
267
+ /**
268
+ * Provisions a new website on one of your Agency Plan hosting orders.
269
+
270
+ Choose the datacenter, stack (`flavor`), and PHP version for the site. Optionally attach
271
+ your own `domain` — omit it, set it to `null`, or leave it unavailable and a free
272
+ `*.hostingersite.com` subdomain is generated instead — and/or install WordPress by
273
+ supplying the `wordpress` details (admin account, site title, and language).
274
+
275
+ Common setups:
276
+ - **Plain PHP site**: `flavor` set to `php-fpm`, with `settings.php.version`; omit
277
+ `wordpress` and `type`.
278
+ - **WordPress site**: `flavor` set to the desired WordPress version (e.g. `wp-7.0`), plus
279
+ the `wordpress` block (admin account, title, language).
280
+ - **Static/Node.js frontend app**: `flavor` set to `php-fpm` and `type` set to
281
+ `node-static`.
282
+
283
+ Provisioning runs in the background, so the response returns immediately with a setup UUID
284
+ that identifies the job. The new website becomes reachable once provisioning finishes.
285
+ */
286
+ "agency-hosting_provisionANewAgencyPlanWebsiteV1": {
287
+ params: {
288
+ /**
289
+ * Agency Plan order ID
290
+ */
291
+ order_id: number;
292
+ /**
293
+ * Datacenter code where the website should be provisioned. Available codes depend on live capacity and are not a fixed set.
294
+ */
295
+ datacenter_code: string;
296
+ /**
297
+ * Setup flavor: a specific WordPress version in the format `wp-<major>.<minor>` or `wp-<major>.<minor>.<patch>` (e.g. `wp-6.8.2`), or `php-fpm` for a plain PHP stack. Generic versions like `wp-latest` are not allowed.
298
+ */
299
+ flavor: string;
300
+ /**
301
+ * Website settings
302
+ */
303
+ settings: object;
304
+ /**
305
+ * Primary domain to attach to the website. Omit or set to null to get a free auto-generated *.hostingersite.com subdomain instead.
306
+ */
307
+ domain?: string;
308
+ /**
309
+ * Website type
310
+ */
311
+ type?: string;
312
+ /**
313
+ * WordPress installation options
314
+ */
315
+ wordpress?: object;
316
+ /**
317
+ * Clone the new website from an existing website
318
+ */
319
+ clone?: object;
320
+ /**
321
+ * Derive the domain from an existing vhost
322
+ */
323
+ derive_domain?: object;
324
+ };
325
+ response: any; // Response structure will depend on the API
326
+ };
327
+
328
+ /**
329
+ * Returns the current status of an Agency Plan website setup started via the setups
330
+ endpoint.
331
+
332
+ Poll this endpoint using the `setup_uuid` returned from the provisioning request until
333
+ `status` becomes `completed`, at which point `website_uid` identifies the new website.
334
+ */
335
+ "agency-hosting_getAgencyPlanWebsiteSetupStatusV1": {
336
+ params: {
337
+ /**
338
+ * Agency Plan order ID
339
+ */
340
+ order_id: number;
341
+ /**
342
+ * Website setup UUID
343
+ */
344
+ setup_uuid: string;
345
+ };
346
+ response: any; // Response structure will depend on the API
347
+ };
348
+
349
+ /**
350
+ * Builds and deploys a Node.js application for an Agency Plan website from an already-uploaded archive.
351
+
352
+ Upload the archive to file browser first, then provide its relative path from document root in this request.
353
+ Website contents are overwritten by the build result, which is deployed to public_html.
354
+ */
355
+ "agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1": {
356
+ params: {
357
+ /**
358
+ * Agency Plan website UID
359
+ */
360
+ website_uid: string;
361
+ /**
362
+ * Directory, relative to the website document root, where the uploaded site archive currently lives. Most commonly this is simply `public_html`.
363
+ */
364
+ archive_path: string;
365
+ };
366
+ response: any; // Response structure will depend on the API
367
+ };
368
+
369
+ /**
370
+ * Retrieves detailed information about a specific Agency Plan website, including configuration,
371
+ status, metadata, hosting plan details, and resource quotas.
372
+ */
373
+ "agency-hosting_getAgencyPlanWebsiteDetailsV1": {
374
+ params: {
375
+ /**
376
+ * Agency Plan website UID
377
+ */
378
+ website_uid: string;
379
+ };
380
+ response: any; // Response structure will depend on the API
381
+ };
382
+
383
+ /**
384
+ * Deletes an Agency Plan website and schedules cleanup of its resources.
385
+
386
+ This action is irreversible. Website files, databases, and linked domains are removed.
387
+ */
388
+ "agency-hosting_deleteAgencyPlanWebsiteV1": {
389
+ params: {
390
+ /**
391
+ * Agency Plan website UID
392
+ */
393
+ website_uid: string;
394
+ };
395
+ response: any; // Response structure will depend on the API
396
+ };
397
+
398
+ /**
399
+ * Lists active and recently completed asynchronous processes for an Agency Plan website.
400
+
401
+ Each process has a unique ID (for tracking), a type, and a status (running, completed, failed).
402
+ Poll this endpoint after initiating async operations (SSL setup, backups, cloning) to track progress.
403
+ */
404
+ "agency-hosting_listRunningAgencyPlanWebsiteProcessesV1": {
405
+ params: {
406
+ /**
407
+ * Agency Plan website UID
408
+ */
409
+ website_uid: string;
410
+ };
411
+ response: any; // Response structure will depend on the API
412
+ };
413
+
162
414
  /**
163
415
  * Retrieve catalog items available for order.
164
416
 
@@ -1808,7 +2060,7 @@ Only applicable to server-side applications (Express, Next.js, NestJS, etc.). St
1808
2060
  front-end apps (React, Vue, Vite) have no persistent server process, so restarting them
1809
2061
  has no effect. Returns success even when the website has no server process to restart.
1810
2062
  */
1811
- "hosting_restartNode.jsApplicationV1": {
2063
+ "hosting_restartNode_jsApplicationV1": {
1812
2064
  params: {
1813
2065
  /**
1814
2066
  * username parameter