About Snappcloud Bot
Snappcloud Bot is an MCP server published by snapp-incubator in the Blockchain category: chatOps SRE assistant for Kubernetes/OpenShift. Answers questions and investigates Alertmanager alerts over MCP servers — strictly inside each user's own RBAC, read-only, with no cluster credentials of its own.
The repository has 1 stars and 0 forks, with the last commit 3 days ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
From source
git clone https://github.com/snapp-incubator/snappcloud-botThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
✦
Ask AI about Snappcloud Bot
Powered by Claude · Grounded in docs
I know everything about Snappcloud Bot. Ask me about installation, configuration, usage, or troubleshooting.
Security checks
6 checks have not been run yet.
Releases
v1.13.0v1.13.0 · 14 Oct 2026Unattended answers are reviewed against their own evidence A scheduled report or alert investigation gets one more pass before it is posted: the same model, the same transcript, asked to correct the draft against the tool results it…
v1.12.0v1.12.0 · 14 Oct 2026Configuration only — the image is identical to v1.11.0. The version exists so one number names one deployment. The bot can be asked to launch an application "How do I deploy / launch / expose an application?" now has a playbook, written…
v1.11.0v1.11.0 · 3 Oct 2026The model was never sent the metrics tools Every daily report that explained at length that teh-1 has no Prometheus tool was telling the truth about what it held. The bot was not. The endpoint carries **128 tool definitions**. Past that…
v1.10.0v1.10.0 · 3 Oct 2026v1.10.0 Code identical to v1.9.0. This release pairs with the tool-guidance change that ships beside it, so the image and the values move as one version. An alert's metric is searched for, not recalled Two Cilium alerts were investigated…
v1.9.0v1.9.0 · 28 Sep 2026v1.9.0 A report is demanded, never a transcript of the deliberation A scheduled report arrived as: "Stop. I have spent my tool budget on tool exploration… I need to be honest about this… I'll write what I have, mark what I could not…