Back to Browse

Clusterport MCP Server

Developer ToolsUse Caution3.4MCP RegistryLocal
Free

Server data from the Official MCP Registry

Core kubectl operations: get, describe, logs, apply, scale, patch, rollout and explain.

About

Core kubectl operations: get, describe, logs, apply, scale, patch, rollout and explain.

Security Report

3.4
Use Caution3.4High Risk

clusterport is a kubectl wrapper that spawns kubectl with argument arrays and passes manifests over stdin, which avoids shell injection and matches its Kubernetes purpose. The main concern is argument injection: resource names and types are passed to kubectl without a '--' separator or a leading-dash check, so a value such as '--all' as the name of kubectl_delete can turn a single-resource delete into a broad one, and an LLM caller can be steered into doing so. The server also has no auth layer of its own and relies entirely on the host's kubeconfig, and its destructive tools have no confirmation step. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 12 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

process_spawn

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

database

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "clusterport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/clusterport@0.1.0"
      ]
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub README.

clusterport

clusterport is a small MCP server and CLI for core Kubernetes work. It is a clean-room rebuild of a core subset — twelve tools — from the documented surface of the community Flux159 mcp-server-kubernetes: get, describe and fetch logs; apply and create; delete, scale and patch; rollout actions and context switching; plus kubectl explain and API-resource listing.

Everything runs through the host's real kubectl. Each call is built as an argument array and spawned directly — never a shell string — so resource names, namespaces and patches cannot be reinterpreted as shell syntax. Manifests are never written to temp files or shell redirects: kubectl_apply sends its manifest over stdin (kubectl apply -f -), and kubectl_create generates a minimal manifest spec from its parameters and creates it from stdin the same way (kubectl create -f -). The executor is injectable, which is how the test suite verifies the exact argument arrays and stdin payloads with a fake.

Deliberately omitted: port-forward long-lived sessions, exec-into-pod, the helm tools, install/uninstall addon operations, non-resource URL operations, watch/streaming, and node operations such as cordon, taint or drain.

The host needs a working kubectl and cluster credentials. When kubectl is absent, calls fail honestly with the underlying spawn error (ENOENT) instead of a fabricated result. The published container image bundles no kubectl binary: it expects a host executor and says so in its Dockerfile.

Install

npx @reneturcios/clusterport kubectl-get pods -n default
docker run -i ghcr.io/cloudcorprecords/clusterport

CLI

clusterport kubectl-get <resource_type> [name] [-n namespace] [-o format]
clusterport kubectl-describe <resource_type> <name> [-n namespace]
clusterport kubectl-logs <name> [-n namespace] [-c container]
clusterport kubectl-apply "<manifest yaml>" [-n namespace] [--dry-run]
clusterport kubectl-create <resource_type> <name> [--image img] [-n namespace]
clusterport kubectl-delete <resource_type> <name> [-n namespace]
clusterport kubectl-scale <resource_type> <name> <replicas> [-n namespace]
clusterport kubectl-patch <resource_type> <name> '<json patch>' [-n namespace]
clusterport kubectl-rollout <resource_type> <name> <action> [-n namespace]
clusterport kubectl-context <current|list|use> [name]
clusterport explain-resource <resource> [--api-version v]
clusterport list-api-resources [kind]
clusterport --version

Exit codes: 0 success, 1 kubectl error, 2 usage error.

MCP server

npx -y @reneturcios/clusterport mcp
{
  "mcpServers": {
    "clusterport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/clusterport", "mcp"]
    }
  }
}

Tools

ToolInputWhat it does
kubectl_getresource_type (required), name, namespace, output_formatkubectl get -o json by default; JSON parsed.
kubectl_describeresource_type, name (required), namespacekubectl describe.
kubectl_logsname (required), namespace, containerkubectl logs.
kubectl_applymanifest (required), namespace, dry_runkubectl apply -f -, manifest over stdin.
kubectl_createresource_type, name (required), namespace, imageGenerated spec created via kubectl create -f - over stdin.
kubectl_deleteresource_type, name (required), namespacekubectl delete.
kubectl_scaleresource_type, name, replicas (required), namespacekubectl scale --replicas=n.
kubectl_patchresource_type, name, patch (required), namespacekubectl patch -p.
kubectl_rolloutresource_type, name, action (required), namespacekubectl rollout <action> <type>/<name>.
kubectl_contextoperation (required: current, list, use), namekubectl config current/get/use-context.
explain_resourceresource (required), api_versionkubectl explain.
list_api_resourceskind (optional)kubectl api-resources, parsed, kind-filtered.

Executor failures — a missing kubectl binary, an unreachable cluster, a nonexistent resource — are reported as tool errors carrying the underlying message.

Development

npm install
npm run build
npm test
npm run dev

Tests run entirely on a fake executor: exact argument arrays, stdin manifest passing for apply/create, output parsing, and error propagation. No live cluster is touched.

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!