Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Core kubectl operations: get, describe, logs, apply, scale, patch, rollout and explain.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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 mcpPaste 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.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Local-only Python MCP server for the Files.com API.
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 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.
npx @reneturcios/clusterport kubectl-get pods -n default
docker run -i ghcr.io/cloudcorprecords/clusterport
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.
npx -y @reneturcios/clusterport mcp
{
"mcpServers": { "clusterport": { "command": "npx", "args": ["-y", "@reneturcios/clusterport", "mcp"] } } }
| Tool | Input | What it does |
|---|---|---|
kubectl_get | resource_type (required), name, namespace, output_format | kubectl get -o json by default; JSON parsed. |
kubectl_describe | resource_type, name (required), namespace | kubectl describe. |
kubectl_logs | name (required), namespace, container | kubectl logs. |
kubectl_apply | manifest (required), namespace, dry_run | kubectl apply -f -, manifest over stdin. |
kubectl_create | resource_type, name (required), namespace, image | Generated spec created via kubectl create -f - over stdin. |
kubectl_delete | resource_type, name (required), namespace | kubectl delete. |
kubectl_scale | resource_type, name, replicas (required), namespace | kubectl scale --replicas=n. |
kubectl_patch | resource_type, name, patch (required), namespace | kubectl patch -p. |
kubectl_rollout | resource_type, name, action (required), namespace | kubectl rollout / . |
kubectl_context | operation (required: current, list, use), name | kubectl config current/get/use-context. |
explain_resource | resource (required), api_version | kubectl explain. |
list_api_resources | kind (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.
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.
MIT — see LICENSE.