run_kubectl_command
Run a kubectl command against the cluster pointed to by the current kubeconfig
LABSCO SUMMARY
kubectl, with the answer read back to you.
There is no shaped tool surface here — it runs the commands you would have run, which means the reach is whatever your kubeconfig grants, writes included. Piping support is what separates it from a one-command wrapper: the diagnostic commands people actually type usually have a pipe in them.
What it is
A server that runs kubectl on your behalf and interprets what comes back. It accepts a kubeconfig path, so you choose which cluster and context the commands land on, and it supports command-line piping rather than only single flat commands.
What you get
- kubectl commands executed against your cluster, with the result interpreted rather than dumped raw
- Flexible command-line piping, so multi-stage commands work as they do in your shell
- A custom kubeconfig path, to pick the cluster and context the calls run against
- A startup check that kubectl is actually installed, and error messages that say what went wrong
Requirements
kubectl installed and on the path, and a kubeconfig for the cluster you want to reach. Node dependencies installed and the project built; the client points at build/index.js. No account or key beyond your existing cluster credentials. The package is k8s-interactive 0.1.0.
Setup effort
Build from source
USE CASES
01
Working out why pods are unhealthy in a namespace you rarely touch
Run the listing and describe commands and get the output interpreted, instead of scrolling through raw kubectl text looking for the line that matters.
02
Switching between clusters without leaving the conversation
Point the server at a specific kubeconfig path so commands run against the cluster and context you mean, not whatever your shell had selected last.
03
Running a multi-stage command you would normally pipe
Chain the command as you would in a terminal — piping is supported, so filtering and reshaping output happens in one call.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
- Node.js and npm (to build the clone)
- kubectl installed, and a kubeconfig for your cluster
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/TaichiHo/k8s-interactive-mcp
cd k8s-interactive-mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"k8s-interactive": {
"command": "<YOUR_PATH_TO_K8S_INTERACTIVE_MCP>/build/index.js"
}
}
}
