rootcause-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rc_suggest_hfacsB | Suggest HFACS-MES classification codes for a cause description. Returns ranked suggestions with confidence scores. HFACS-MES has 5 levels: External Factors, Organizational Influences, Unsafe Supervision, Preconditions, Unsafe Acts. |
| rc_confirm_classificationA | Confirm an HFACS classification as correct. This helps the system learn from expert decisions and improve future suggestions. Confirmed classifications are stored as learned rules. |
| rc_get_hfacs_frameworkA | Get HFACS-MES framework structure and category definitions. Use this to understand the classification hierarchy and criteria. |
| rc_list_learned_rulesA | List all learned classification rules. Shows rules that have been confirmed by experts. |
| rc_reload_rulesA | Reload classification rules from YAML files. Use this after manually editing config files. |
| rc_get_6m_hfacs_mappingA | Get mapping between 6M Fishbone categories and HFACS codes. Shows how Fishbone categories (Personnel, Equipment, Material, Process, Environment, Monitoring) correspond to HFACS levels. Useful for cross-framework analysis and ensuring comprehensive coverage. Also provides Why Tree depth guidance for each category. |
| rc_start_sessionB | Start a new RCA analysis session. Creates a new session with the specified case type and title. Returns session_id for subsequent operations. |
| rc_get_sessionA | Get details of an RCA session by ID. Returns session status, current stage, and progress. |
| rc_list_sessionsA | List all RCA sessions with optional filters. Returns summary of all sessions. |
| rc_archive_sessionB | Archive a completed RCA session. Archived sessions are preserved but marked as inactive. |
| rc_init_fishboneA | Initialize a Fishbone (Ishikawa) diagram for a session. Creates a 6M structure (Personnel, Equipment, Material, Process, Environment, Monitoring) with the problem statement as the fish head. |
| rc_add_causeB | Add a cause to a Fishbone category. Each cause can have sub-causes, evidence, and HFACS classification. |
| rc_get_fishboneB | Get the complete Fishbone diagram for a session. Returns all categories and causes in structured format. |
| rc_export_fishboneB | Export Fishbone diagram in various formats. Supports Mermaid, JSON, and Markdown formats. |
| rc_ask_whyA | Ask 'Why?' to drill down into root causes using 5-Why analysis. Creates or extends a WhyChain for the session. Each call goes one level deeper (up to 5 levels). This is the CORE tool for systematic root cause reasoning. |
| rc_get_why_treeA | Get the complete Why Tree (5-Why analysis chain) for a session. Shows all Why questions and answers in hierarchical format. |
| rc_mark_root_causeB | Mark a WhyNode as the identified root cause. This indicates the analysis has reached a fundamental cause that requires action. |
| rc_export_why_treeB | Export Why Tree in various formats. Supports Mermaid (flowchart), JSON, and Markdown. |
| rc_add_causal_linkA | Add a directed or bidirectional causal relationship between Why nodes. Use this to capture escalation loops, feedback cycles, or mitigation links that are not visible in a simple linear 5-Why chain. |
| rc_build_teaching_caseA | Transform a completed Why Tree into a teaching-ready lesson plan. Generates learning objectives, common pitfalls, discussion prompts, and reverse-causality questions for medical learners. |
| rc_verify_causationB | Verify causal relationship between cause and effect using the Counterfactual Testing Framework. Tests: 1) Temporality - Did cause precede effect? 2) Necessity - Would effect occur without cause? 3) Mechanism - Is there a plausible causal pathway? 4) Sufficiency - Is cause alone sufficient for effect? |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_incident | Analyze a clinical incident using systematic RCA methodology, then optionally transform it into a teaching-ready causal lesson. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/u9401066/rootcause-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server