Is Rootcause safe to use?

Rootcause has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install Rootcause?

Rootcause supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can Rootcause do?

Rootcause provides 57 tools: rootcause.incident_bundle, rootcause.rca_generate, rootcause.change_timeline, rootcause.postmortem_export, rootcause.capabilities and 52 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with Rootcause?

Rootcause is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is Rootcause actively maintained?

Rootcause is actively maintained — last commit was 6 days ago. It has 41 GitHub stars.

Rootcause

Name: Rootcause
Author: yindia

agent-browser · by yindia

RootCause is a local-first MCP server that turns natural-language requests into evidence-backed incident analysis, Kubernetes diagnostics, and safer operations.

41 57 tools GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 6d ago

Works with most clients

Transport: stdio, sse, http

57 tools · ~1.7k tok

Grade C · 0.8% of 200K ctx

Edit this pageView history

DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "rootcause": {
      "env": {
        "KUBECONFIG": "/Users/you/.kube/config"
      },
      "args": [
        "--config",
        "/Users/you/.config/rootcause/config.toml"
      ],
      "command": "rootcause"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/rootcause)](https://mcppedia.org/s/rootcause)

Read me

What Rootcause does

RootCause is a local-first MCP server that turns natural-language requests into evidence-backed incident analysis, Kubernetes diagnostics, and safer operations.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'agent-browser' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

80/100across 5 weighted dimensions

How we score →

0255075100

−20

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked agent-browser against OSV.dev.

Inventory

Tools (57)

Click any tool to inspect its schema.

~1.7k tokens total

Inventory

Prompts (3)

gcp_workload_diagnose

Diagnose issues with GCP workloads

k8s-helm

Kubernetes and Helm operations guidance

k8s-incident

Kubernetes incident response and diagnostics

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Rootcause safe to use?: Rootcause has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install Rootcause?: Rootcause supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can Rootcause do?: Rootcause provides 57 tools: rootcause.incident_bundle, rootcause.rca_generate, rootcause.change_timeline, rootcause.postmortem_export, rootcause.capabilities and 52 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with Rootcause?: Rootcause is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is Rootcause actively maintained?: Rootcause is actively maintained — last commit was 6 days ago. It has 41 GitHub stars.

Similar servers

Others in devops

View all →

Mcp Gitlab96

MCP server for using the GitLab API

1.6k 12

Mcp Gitlab Server92

Enhanced MCP server for GitLab: group projects listing and activity tracking

51 2

Alibabacloud Devops Mcp Server92

Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.

116 7

Komodo MCP Server91

MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI

7 11

MCP Security Weekly

Get CVE alerts and security updates for Rootcause and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "rootcause": {
      "env": {
        "KUBECONFIG": "/Users/you/.kube/config"
      },
      "args": [
        "--config",
        "/Users/you/.config/rootcause/config.toml"
      ],
      "command": "rootcause"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/rootcause)](https://mcppedia.org/s/rootcause)

Read me

What Rootcause does

RootCause is a local-first MCP server that turns natural-language requests into evidence-backed incident analysis, Kubernetes diagnostics, and safer operations.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'agent-browser' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

RootCause 🧭

AI-native SRE for Kubernetes incidents.

RootCause is a local-first MCP server that turns natural-language requests into evidence-backed incident analysis, Kubernetes diagnostics, and safer operations.

Built in Go as a single binary, RootCause is optimized for low-friction local workflows using your existing kubeconfig identity.

Why RootCause 💡

RootCause is built for SRE/operator workflows where speed matters, but unsafe automation is unacceptable.

🚀 Stop context-switching: investigate incidents, rollout risk, Helm/Terraform/AWS signals, and remediation from one MCP server.
🧠 AI-powered diagnostics: evidence-first analysis with RCA, timelines, and action-oriented next checks.
💸 Built-in cost optimization: combine resource usage, workload best-practice checks, Terraform plan analysis, and cloud context for optimization decisions.
🔒 Enterprise-ready guardrails: role/namespace policy enforcement, redaction, read-only mode, destructive tool controls, and mutation preflight.
⚡ Zero learning curve: ask natural-language operational questions and use provided prompt templates for common SRE flows.
🌐 Universal compatibility: works with MCP-compatible clients across Claude, Cursor, Copilot, Codex, and more.
🏭 Production-grade workflow: single Go binary, kubeconfig-native auth, deterministic structured outputs, and broad test coverage.

Why teams choose it

Need	RootCause answer
"What changed and why did this break?"	`rootcause.incident_bundle`, `rootcause.change_timeline`, `rootcause.rca_generate`
"Is it safe to restart or roll out now?"	`k8s.restart_safety_check`, `k8s.best_practice`, `k8s.safe_mutation_preflight`
"Is my platform ecosystem healthy?"	`k8s._detect` + `k8s.diagnose_` for ArgoCD/Flux/cert-manager/Kyverno/Gatekeeper/Cilium
"Can I standardize SRE responses?"	Prompt templates + structured output from shared render/evidence pipeline

What Can You Do?

Ask your AI assistant in natural language:

"Why did this deployment fail after rollout?"
"Is this workload safe to restart right now?"
"Why are ArgoCD apps out of sync?"
"Is Flux healthy in this cluster?"
"Why are certs failing to renew?"
"Before patch/apply, is this mutation safe?"

RootCause keeps its depth-first model: evidence-first diagnosis, root-cause analysis, and remediation flow instead of raw tool sprawl.

Power users can map these prompts to concrete tools in this README (Complete Feature Set, Toolchains, and Tools sections).

Use Cases

Incident response

Build end-to-end incident evidence with rootcause.incident_bundle
Generate probable causes with rootcause.rca_generate
Export timeline and postmortem artifacts for follow-up

Safe operations before mutation

Evaluate rollout/restart risk with k8s.restart_safety_check and k8s.best_practice
Run k8s.safe_mutation_preflight before apply/patch/delete/scale operations

Ecosystem-specific health checks

ArgoCD: detect installation and diagnose sync/health drift
Flux: detect controllers and diagnose reconciliation failures
cert-manager / Kyverno / Gatekeeper / Cilium: detect footprint and diagnose control-plane or policy issues

Feature Highlights

Area	RootCause Capability
Incident analysis	`rootcause.incident_bundle`, `rootcause.rca_g

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

80/100across 5 weighted dimensions

How we score →

0255075100

−20

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked agent-browser against OSV.dev.

Inventory

Tools (57)

Click any tool to inspect its schema.

~1.7k tokens total

Inventory

Prompts (3)

gcp_workload_diagnose

Diagnose issues with GCP workloads

k8s-helm

Kubernetes and Helm operations guidance

k8s-incident

Kubernetes incident response and diagnostics

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Rootcause safe to use?: Rootcause has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install Rootcause?: Rootcause supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can Rootcause do?: Rootcause provides 57 tools: rootcause.incident_bundle, rootcause.rca_generate, rootcause.change_timeline, rootcause.postmortem_export, rootcause.capabilities and 52 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with Rootcause?: Rootcause is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is Rootcause actively maintained?: Rootcause is actively maintained — last commit was 6 days ago. It has 41 GitHub stars.