hostinger-api-mcp 0.1.12 → 0.1.15

package/.github/workflows/build-release.yaml

@@ -39,13 +39,14 @@ jobs:
           node-version: '24.x'
           registry-url: 'https://registry.npmjs.org'
 
+      - name: Update NPM
+        run: npm install -g npm@latest
+
       - name: Install dependencies
         run: npm install
 
       - name: Publish package
         run: npm publish --provenance --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
   release-github:
     runs-on: ubuntu-latest

package/README.md

@@ -144,6 +144,86 @@ console.log("Tool result:", result);
 
 This MCP server provides the following tools:
 
+### hosting_importWordpressWebsite
+
+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.
+
+- **Method**: ``
+- **Path**: ``
+
+**Parameters**:
+
+- `domain`: Domain name associated with the hosting account (e.g., example.com) (required)
+- `archivePath`: 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) (required)
+- `databaseDump`: Absolute or relative path to a database dump file (.sql) (required)
+
+### hosting_deployWordpressPlugin
+
+Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment.
+
+- **Method**: ``
+- **Path**: ``
+
+**Parameters**:
+
+- `domain`: Domain name associated with the hosting account (e.g., example.com) (required)
+- `slug`: WordPress plugin slug (e.g., omnisend) (required)
+- `pluginPath`: Absolute or relative path to the plugin directory containing all plugin files (required)
+
+### hosting_deployWordpressTheme
+
+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.
+
+- **Method**: ``
+- **Path**: ``
+
+**Parameters**:
+
+- `domain`: Domain name associated with the hosting account (e.g., example.com) (required)
+- `slug`: WordPress theme slug (e.g., twentytwentyfive) (required)
+- `themePath`: Absolute or relative path to the theme directory containing all theme files (required)
+- `activate`: Whether to activate the theme after deployment (default: false) 
+
+### hosting_deployJsApplication
+
+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. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress.
+
+- **Method**: ``
+- **Path**: ``
+
+**Parameters**:
+
+- `domain`: Domain name associated with the hosting account (e.g., example.com) (required)
+- `archivePath`: 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. (required)
+- `removeArchive`: Whether to remove the archive file after successful deployment (default: false) 
+
+### hosting_listJsDeployments
+
+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.
+
+- **Method**: ``
+- **Path**: ``
+
+**Parameters**:
+
+- `domain`: Domain name associated with the hosting account (e.g., example.com) (required)
+- `page`: Page number for pagination (optional) 
+- `perPage`: Number of items per page (optional) 
+- `states`: Filter by deployment states (optional). Valid values: pending, completed, running, failed 
+
+### hosting_showJsDeploymentLogs
+
+Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure.
+
+- **Method**: ``
+- **Path**: ``
+
+**Parameters**:
+
+- `domain`: Domain name associated with the hosting account (e.g., example.com) (required)
+- `fromLine`: Line from which to retrieve logs (optional, default 0) 
+- `buildUuid`: UUID of the JavaScript deployment build (required)
+
 ### billing_getCatalogItemListV1
 
 Retrieve catalog items available for order.
@@ -402,6 +482,15 @@ Use this endpoint to verify DNS record validity before applying changes.
 - `overwrite`: If `true`, resource records (RRs) matching name and type will be deleted and new RRs will be created, otherwise resource records' ttl's are updated and new records are appended. If no matching RRs are found, they are created. 
 - `zone`: zone parameter (required)
 
+### v2_getDomainVerificationsDIRECT
+
+Retrieve a list of pending and completed domain verifications.
+
+- **Method**: `GET`
+- **Path**: `/api/v2/direct/verifications/active`
+
+
+
 ### domains_checkDomainAvailabilityV1
 
 Check availability of domain names across multiple TLDs.
@@ -727,7 +816,7 @@ Retrieve a paginated list of websites (main and addon types) accessible to the a
 
 This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.
 
-Use the available query parameters to filter results by username, order ID, or enabled status for more targeted results.
+Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
 
 - **Method**: `GET`
 - **Path**: `/api/hosting/v1/websites`
@@ -739,6 +828,7 @@ Use the available query parameters to filter results by username, order ID, or e
 - `username`: Filter by specific username 
 - `order_id`: Order ID 
 - `is_enabled`: Filter by enabled status 
+- `domain`: Filter by domain name (exact match) 
 
 ### hosting_createWebsiteV1
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "0.1.12",
+  "version": "0.1.15",
   "description": "MCP server for Hostinger API",
   "repository": {
     "type": "git",
@@ -26,11 +26,12 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.10.0",
-    "minimist": "^1.2.8",
-    "express": "^4.21.2",
     "axios": "^1.8.0",
+    "cors": "^2.8.5",
     "dotenv": "^16.4.7",
-    "cors": "^2.8.5"
+    "express": "^4.21.2",
+    "minimist": "^1.2.8",
+    "tus-js-client": "^4.1.0"
   },
   "devDependencies": {
     "@types/node": "^24.0.0",