Kubernetes MCP Server vs Hostinger API MCP
A side-by-side look at the Kubernetes MCP Server and Hostinger API MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kubernetes MCP Server for cloud platforms work as a local process; choose Hostinger API MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kubernetes MCP Server when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
configuration_contexts_list, targets_list, configuration_view.
Choose Hostinger API MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HOSTINGER_API_TOKEN, DEBUG, OAUTH_ISSUER, API_TOKEN. - You want tools like
search, execute, multi-execute.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 68/100 · Great | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | HOSTINGER_API_TOKENDEBUGOAUTH_ISSUERAPI_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,173 | 163 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 76 | 3 |
| Full listing | View Kubernetes MCP Server | View Hostinger API MCP |
Tools & capabilities
Kubernetes MCP Server tools 76
configuration_contexts_listList all available context names and associated server urls from the kubeconfig filetargets_listList all available targetsconfiguration_viewGet the current Kubernetes configuration content as a kubeconfig YAMLevents_listList Kubernetes events (warnings, errors, state changes) for debugging and troubleshooting in the current cluster from all namespacesnamespaces_listList all the Kubernetes namespaces in the current clusterprojects_listList all the OpenShift projects in the current clusternodes_logGet logs from a Kubernetes node (kubelet, kube-proxy, or other system logs). This accesses node logs through the Kubernetes API proxy to the kubeletnodes_stats_summaryGet detailed resource usage statistics from a Kubernetes node via the kubelet's Summary API. Provides comprehensive metrics including CPU, memory, filesystem, and network usage at the node, pod, and container levels. On systems with cgroup v2 and kernel 4.20+, also includes PSI (Pressure Stall Info…nodes_topList the resource consumption (CPU and memory) as recorded by the Kubernetes Metrics Server for the specified Kubernetes Nodes or all nodes in the clusterpods_listList all the Kubernetes pods in the current cluster from all namespacespods_list_in_namespaceList all the Kubernetes pods in the specified namespace in the current clusterpods_getGet a Kubernetes Pod in the current or provided namespace with the provided name- +64 more on the listing page
Hostinger API MCP tools 3
searchfind operations by keyword; returns each match with its `inputSchema`.executerun one operation: `{ "operation": "<name>", "params": { ... } }`.multi-executerun up to 20 operations in order, stopping at the first failure. A params value that is exactly `"$steps.<i>.<path>"` is replaced by that value from an earlier step's result.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kubernetes MCP Server
{
"mcpServers": {
"kubernetes-mcp-server": {
"command": "npx",
"args": [
"-y",
"kubernetes-mcp-server@latest"
]
}
}
}
Hostinger API MCP
{
"mcpServers": {
"hostinger-api-mcp": {
"command": "npx",
"args": [
"-y",
"@hostinger/mcp"
],
"env": {
"HOSTINGER_API_TOKEN": "YOUR_HOSTINGER_API_TOKEN_HERE",
"DEBUG": "YOUR_DEBUG_HERE",
"OAUTH_ISSUER": "YOUR_OAUTH_ISSUER_HERE",
"API_TOKEN": "YOUR_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Kubernetes MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. Hostinger API MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Kubernetes MCP Server for cloud platforms work and Hostinger API MCP for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kubernetes MCP Server is listed as free. Auth: other. Hostinger API MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kubernetes-mcp-server and hostinger-api-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kubernetes MCP Server has a quality signal of 68/100 (Great) with 5 views, 0 installs and 2,173 GitHub stars. Hostinger API MCP has 52/100 (Good) with 1 views, 0 installs and 163 GitHub stars.