Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Clusterport

by CloudCorpRecordsversion 0.1.0i★ –iRuns on your computer
Registry nameio.github.CloudCorpRecords/clusterport

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add clusterport -- npx -y @reneturcios/clusterport mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32545 servers in this category
  • Published to the registry more recently than 86% of the other 32545 servers in this category
  • Basic checks equal to or better than 100% of the other 32545 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Clusterport safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Python MCP

by Files-com

Local-only Python MCP server for the Files.com API.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 [-n namespace] clusterport kubectl-logs [-n namespace] [-c container] clusterport kubectl-apply " " [-n namespace] [--dry-run] clusterport kubectl-create [--image img] [-n namespace] clusterport kubectl-delete [-n namespace] clusterport kubectl-scale [-n namespace] clusterport kubectl-patch ' ' [-n namespace] clusterport kubectl-rollout [-n namespace] clusterport kubectl-context [name] clusterport explain-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 / .
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.

Ask PopNx