Troubleshoot Kubernetes agentically: natural-language cluster diagnosis via ask_kubently
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-kubently-kubently": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Troubleshoot Kubernetes agentically: natural-language cluster diagnosis via ask_kubently
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / health
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
MCP Server for kubernetes management commands
MCP server for Hostinger API
IAM Policy Autopilot is an open source static code analysis tool that helps you quickly create baseline AWS IAM policies that you can refine as your application evolves. This tool is available as a command-line utility and MCP server for use within AI coding assistants for quickly building IAM policies.
MCP Security Weekly
Get CVE alerts and security updates for io.github.kubently/kubently and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Kubently - Troubleshooting Kubernetes Agentically
Kubently (Kubernetes + Agentically) enables AI agents to troubleshoot Kubernetes clusters through natural language conversations. By implementing the A2A (Agent-to-Agent) protocol, Kubently allows multiple agents to collaborate in diagnosing and resolving cluster issues autonomously.
Point kubectl at any cluster (kind, minikube, or real) and run:
npm install -g @kubently/cli
kubently install
That's it. The CLI installs Kubently via Helm, wires up secrets and the executor, port-forwards the API, and drops you into a debug chat:
kubently> why is my nginx pod crashlooping?
You'll need an LLM API key (Anthropic, OpenAI, or Google) — the installer
prompts for it, or reads ANTHROPIC_API_KEY / OPENAI_API_KEY /
GOOGLE_API_KEY from your environment. Use --provider to pick the LLM,
--chart ./deployment/helm/kubently to install from a local checkout, and
kubently install --help for everything else.
Already ran kubently install? Add Kubently to Claude Code:
claude mcp add kubently -- kubently mcp
Or connect directly over HTTP (no bridge process):
claude mcp add --transport http kubently http://localhost:8080/mcp/ \
--header "X-API-Key: <your-api-key>"
Then ask Claude things like "use kubently to figure out why payments pods are crashlooping". Any MCP client works — see docs/MCP.md for Cursor and generic configuration.
Set api.env.SLACK_WEBHOOK_URL to a Slack incoming-webhook URL and point
Alertmanager at Kubently:
receivers:
- name: kubently
webhook_configs:
- url: https://<your-kubently-host>/webhooks/alertmanager
http_config:
http_headers: # Alertmanager >= 0.28
X-API-Key:
secrets: ["<your-api-key>"]
Each firing alert is diagnosed by the agent and the result is posted to Slack — the bot often explains the root cause before you've opened your laptop.
📖 See QUICK_START.md for full quick-start guide
📚 See GETTING_STARTED.md for production deployment
# Deploy to a local kind cluster (builds i
... [View full README on GitHub](https://github.com/kubently/kubently#readme)