Clusterport

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

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

VerifiedSTDIODesktop only

Overview

Clusterport's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Clusterport in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

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

CLI

bash
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

bash
npx -y @reneturcios/clusterport mcp
json
{  "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

bash
npm installnpm run buildnpm testnpm 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.

Source: README.md at commit 6ad44f8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts