hostinger-api-mcp 1.2.1 → 1.4.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/README.md +231 -3
- package/gemini-extension.json +1 -1
- package/package.json +1 -1
- package/server.json +2 -2
- package/src/core/runtime.js +1 -1
- package/src/core/runtime.ts +1 -1
- package/src/core/tools/all.js +738 -82
- package/src/core/tools/all.ts +738 -82
- package/src/core/tools/hosting.js +149 -0
- package/src/core/tools/hosting.ts +149 -0
- package/src/core/tools/wordpress.js +507 -0
- package/src/core/tools/wordpress.ts +507 -0
- 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 +471 -0
package/README.md
CHANGED
|
@@ -49,16 +49,16 @@ pnpm update -g hostinger-api-mcp
|
|
|
49
49
|
|
|
50
50
|
This package installs the following MCP server commands:
|
|
51
51
|
|
|
52
|
-
- `hostinger-api-mcp` — unified server with every tool (
|
|
52
|
+
- `hostinger-api-mcp` — unified server with every tool (202 total)
|
|
53
53
|
- `hostinger-billing-mcp` — 7 tools for billing
|
|
54
54
|
- `hostinger-dns-mcp` — 8 tools for dns
|
|
55
55
|
- `hostinger-domains-mcp` — 18 tools for domains
|
|
56
56
|
- `hostinger-ecommerce-mcp` — 12 tools for ecommerce
|
|
57
57
|
- `hostinger-horizons-mcp` — 2 tools for horizons
|
|
58
|
-
- `hostinger-hosting-mcp` —
|
|
58
|
+
- `hostinger-hosting-mcp` — 46 tools for hosting
|
|
59
59
|
- `hostinger-reach-mcp` — 12 tools for reach
|
|
60
60
|
- `hostinger-vps-mcp` — 62 tools for vps
|
|
61
|
-
- `hostinger-wordpress-mcp` —
|
|
61
|
+
- `hostinger-wordpress-mcp` — 35 tools for wordpress
|
|
62
62
|
|
|
63
63
|
Pick the binary that matches your agent's scope. `hostinger-api-mcp` remains the backwards-compatible default.
|
|
64
64
|
|
|
@@ -743,6 +743,56 @@ Retrieve logs for a specified JavaScript application deployment for debugging pu
|
|
|
743
743
|
- **Method**: `custom`
|
|
744
744
|
- **Path**: `custom`
|
|
745
745
|
|
|
746
|
+
#### hosting_clearWebsiteCacheV1
|
|
747
|
+
|
|
748
|
+
Permanently clears all server-side cache for the website at once. Use it when content was
|
|
749
|
+
updated and needs to be visible immediately, or after making major changes.
|
|
750
|
+
|
|
751
|
+
Also purges the Hostinger CDN cache when CDN is enabled on the website. For a WordPress
|
|
752
|
+
installation living in a subdirectory, pass the directory query parameter to clear its cache.
|
|
753
|
+
|
|
754
|
+
- **Method**: `DELETE`
|
|
755
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/clear`
|
|
756
|
+
|
|
757
|
+
#### hosting_disableCachelessModeV1
|
|
758
|
+
|
|
759
|
+
Turns off development (cacheless) mode and returns the website to normal caching. Use it after
|
|
760
|
+
finishing development work to restore the performance benefits of caching.
|
|
761
|
+
|
|
762
|
+
- **Method**: `PATCH`
|
|
763
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cacheless-mode/disable`
|
|
764
|
+
|
|
765
|
+
#### hosting_disableWebsiteCacheV1
|
|
766
|
+
|
|
767
|
+
Turns off server-side caching for the website until it is enabled again. May impact performance.
|
|
768
|
+
Use it when experiencing cache-related issues; to temporarily bypass caching while developing
|
|
769
|
+
or debugging, prefer enabling cacheless mode instead.
|
|
770
|
+
|
|
771
|
+
Does nothing if caching is already disabled.
|
|
772
|
+
|
|
773
|
+
- **Method**: `PATCH`
|
|
774
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/disable`
|
|
775
|
+
|
|
776
|
+
#### hosting_enableCachelessModeV1
|
|
777
|
+
|
|
778
|
+
Enables development (cacheless) mode where nothing is cached, effectively turning off all
|
|
779
|
+
caching for the website. Use it while actively developing, testing changes, debugging issues,
|
|
780
|
+
or when real-time updates must be visible. Disable cacheless mode afterwards to restore
|
|
781
|
+
normal caching.
|
|
782
|
+
|
|
783
|
+
- **Method**: `PATCH`
|
|
784
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cacheless-mode/enable`
|
|
785
|
+
|
|
786
|
+
#### hosting_enableWebsiteCacheV1
|
|
787
|
+
|
|
788
|
+
Turns on server-side caching for the website for better performance. Use it for faster page
|
|
789
|
+
loads, reduced server load, or improved user experience. Recommended for production websites.
|
|
790
|
+
|
|
791
|
+
Does nothing if caching is already enabled.
|
|
792
|
+
|
|
793
|
+
- **Method**: `PATCH`
|
|
794
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/cache/enable`
|
|
795
|
+
|
|
746
796
|
#### hosting_listAccountCronJobsV1
|
|
747
797
|
|
|
748
798
|
Returns the list of cron jobs configured for the specified account, including their schedule and command.
|
|
@@ -1941,6 +1991,65 @@ Use this endpoint to power off running VPS instances.
|
|
|
1941
1991
|
|
|
1942
1992
|
### `hostinger-wordpress-mcp`
|
|
1943
1993
|
|
|
1994
|
+
#### hosting_showAIOptionStatusV1
|
|
1995
|
+
|
|
1996
|
+
Show the current AI option status for the Hostinger Tools plugin on the
|
|
1997
|
+
specified WordPress installation. Filter by `option` to return a single
|
|
1998
|
+
option, or omit it to return all options.
|
|
1999
|
+
|
|
2000
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2001
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2002
|
+
|
|
2003
|
+
- **Method**: `GET`
|
|
2004
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/hostinger-plugins/ai-option/status`
|
|
2005
|
+
|
|
2006
|
+
#### hosting_setAIOptionStatusV1
|
|
2007
|
+
|
|
2008
|
+
Enable or disable an AI option for the Hostinger Tools plugin on the specified
|
|
2009
|
+
WordPress installation.
|
|
2010
|
+
|
|
2011
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2012
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2013
|
+
|
|
2014
|
+
- **Method**: `PATCH`
|
|
2015
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/hostinger-plugins/ai-option/status`
|
|
2016
|
+
|
|
2017
|
+
#### hosting_checkIfWordPressInstallationsAreValidV1
|
|
2018
|
+
|
|
2019
|
+
Check whether one or more WordPress installations are valid and working
|
|
2020
|
+
correctly. Detects broken installations caused by missing files, broken
|
|
2021
|
+
plugins, themes and similar issues.
|
|
2022
|
+
|
|
2023
|
+
Provide the WordPress installation (software) identifiers in the body. They
|
|
2024
|
+
can be obtained from GET /api/hosting/v1/wordpress/installations (the `id`
|
|
2025
|
+
field).
|
|
2026
|
+
|
|
2027
|
+
- **Method**: `POST`
|
|
2028
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations/check-is-valid`
|
|
2029
|
+
|
|
2030
|
+
#### hosting_deleteWordPressInstallationV1
|
|
2031
|
+
|
|
2032
|
+
Delete the specified WordPress installation, with optional file and database
|
|
2033
|
+
removal. This removes all associated components including plugins, themes,
|
|
2034
|
+
staging websites and any other related data.
|
|
2035
|
+
|
|
2036
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2037
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2038
|
+
|
|
2039
|
+
- **Method**: `DELETE`
|
|
2040
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}`
|
|
2041
|
+
|
|
2042
|
+
#### hosting_detectWordPressInstallationsV1
|
|
2043
|
+
|
|
2044
|
+
Trigger a background scan to detect WordPress installations for the account.
|
|
2045
|
+
|
|
2046
|
+
This operation is asynchronous: a successful response only means the scan has
|
|
2047
|
+
been queued. Poll GET /api/hosting/v1/wordpress/installations to fetch the
|
|
2048
|
+
detected installations once the scan completes.
|
|
2049
|
+
|
|
2050
|
+
- **Method**: `POST`
|
|
2051
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/installations/detect`
|
|
2052
|
+
|
|
1944
2053
|
#### hosting_installWordPressV1
|
|
1945
2054
|
|
|
1946
2055
|
Install WordPress on an existing website.
|
|
@@ -1978,6 +2087,125 @@ Each installation includes a `valid` flag and, when invalid, a
|
|
|
1978
2087
|
- **Method**: `GET`
|
|
1979
2088
|
- **Path**: `/api/hosting/v1/wordpress/installations`
|
|
1980
2089
|
|
|
2090
|
+
#### hosting_listAvailableWordPressCoreUpdatesV1
|
|
2091
|
+
|
|
2092
|
+
List available WordPress core updates for the specified installation.
|
|
2093
|
+
|
|
2094
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2095
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2096
|
+
|
|
2097
|
+
- **Method**: `GET`
|
|
2098
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/updates`
|
|
2099
|
+
|
|
2100
|
+
#### hosting_getInstallationJWTTokenV1
|
|
2101
|
+
|
|
2102
|
+
Return a JWT token used to authenticate requests against the specified
|
|
2103
|
+
WordPress installation, including its MCP (Model Context Protocol) endpoint.
|
|
2104
|
+
|
|
2105
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2106
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2107
|
+
|
|
2108
|
+
- **Method**: `GET`
|
|
2109
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/jwt-token`
|
|
2110
|
+
|
|
2111
|
+
#### hosting_showWordPressCoreVersionV1
|
|
2112
|
+
|
|
2113
|
+
Show the WordPress core version for the specified installation, along with
|
|
2114
|
+
known vulnerabilities affecting it.
|
|
2115
|
+
|
|
2116
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2117
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2118
|
+
|
|
2119
|
+
- **Method**: `GET`
|
|
2120
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/version`
|
|
2121
|
+
|
|
2122
|
+
#### hosting_updateWordPressCoreV1
|
|
2123
|
+
|
|
2124
|
+
Update the WordPress core for the specified installation (minor update or a
|
|
2125
|
+
specific version).
|
|
2126
|
+
|
|
2127
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2128
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2129
|
+
|
|
2130
|
+
This operation is asynchronous: a successful response only means the update
|
|
2131
|
+
job has been queued.
|
|
2132
|
+
|
|
2133
|
+
- **Method**: `POST`
|
|
2134
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/update`
|
|
2135
|
+
|
|
2136
|
+
#### hosting_purgeLiteSpeedCacheV1
|
|
2137
|
+
|
|
2138
|
+
Purge the LiteSpeed Cache for the specified WordPress installation.
|
|
2139
|
+
|
|
2140
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2141
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2142
|
+
|
|
2143
|
+
- **Method**: `POST`
|
|
2144
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/litespeed-cache/purge`
|
|
2145
|
+
|
|
2146
|
+
#### hosting_showLiteSpeedCacheStatusV1
|
|
2147
|
+
|
|
2148
|
+
Show the LiteSpeed Cache status for the specified WordPress installation.
|
|
2149
|
+
|
|
2150
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2151
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2152
|
+
|
|
2153
|
+
- **Method**: `GET`
|
|
2154
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/litespeed-cache/status`
|
|
2155
|
+
|
|
2156
|
+
#### hosting_createLoginLinksV1
|
|
2157
|
+
|
|
2158
|
+
Create temporary auto-login links for the specified WordPress installation.
|
|
2159
|
+
|
|
2160
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2161
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2162
|
+
|
|
2163
|
+
- **Method**: `POST`
|
|
2164
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/login/links`
|
|
2165
|
+
|
|
2166
|
+
#### hosting_showMaintenanceStatusV1
|
|
2167
|
+
|
|
2168
|
+
Show the maintenance mode status for the specified WordPress installation.
|
|
2169
|
+
|
|
2170
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2171
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2172
|
+
|
|
2173
|
+
- **Method**: `GET`
|
|
2174
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/maintenance/status`
|
|
2175
|
+
|
|
2176
|
+
#### hosting_toggleMaintenanceModeV1
|
|
2177
|
+
|
|
2178
|
+
Enable or disable maintenance mode for the specified WordPress installation,
|
|
2179
|
+
based on the `enabled` flag.
|
|
2180
|
+
|
|
2181
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2182
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2183
|
+
|
|
2184
|
+
- **Method**: `PATCH`
|
|
2185
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/maintenance/toggle`
|
|
2186
|
+
|
|
2187
|
+
#### hosting_showMemcachedObjectCacheStatusV1
|
|
2188
|
+
|
|
2189
|
+
Show the Memcached object cache status for the specified WordPress
|
|
2190
|
+
installation.
|
|
2191
|
+
|
|
2192
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2193
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2194
|
+
|
|
2195
|
+
- **Method**: `GET`
|
|
2196
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/memcached/status`
|
|
2197
|
+
|
|
2198
|
+
#### hosting_toggleMemcachedObjectCacheV1
|
|
2199
|
+
|
|
2200
|
+
Activate or deactivate the Memcached object cache for the specified WordPress
|
|
2201
|
+
installation, based on the `enabled` flag.
|
|
2202
|
+
|
|
2203
|
+
Provide the WordPress installation (software) identifier in the path. It can
|
|
2204
|
+
be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
|
|
2205
|
+
|
|
2206
|
+
- **Method**: `PATCH`
|
|
2207
|
+
- **Path**: `/api/hosting/v1/accounts/{username}/wordpress/{software}/memcached/toggle`
|
|
2208
|
+
|
|
1981
2209
|
#### hosting_activateWordPressPluginV1
|
|
1982
2210
|
|
|
1983
2211
|
Activate an installed plugin on a WordPress installation.
|
package/gemini-extension.json
CHANGED
package/package.json
CHANGED
package/server.json
CHANGED
|
@@ -6,12 +6,12 @@
|
|
|
6
6
|
"url": "https://github.com/hostinger/api-mcp-server",
|
|
7
7
|
"source": "github"
|
|
8
8
|
},
|
|
9
|
-
"version": "1.
|
|
9
|
+
"version": "1.4.0",
|
|
10
10
|
"packages": [
|
|
11
11
|
{
|
|
12
12
|
"registryType": "npm",
|
|
13
13
|
"identifier": "hostinger-api-mcp",
|
|
14
|
-
"version": "1.
|
|
14
|
+
"version": "1.4.0",
|
|
15
15
|
"transport": {
|
|
16
16
|
"type": "stdio"
|
|
17
17
|
},
|
package/src/core/runtime.js
CHANGED
package/src/core/runtime.ts
CHANGED