Chaos Engineering has always been about one thing: building resilient systems. But let’s be honest, while the idea sounds great, getting started with chaos experiments has never been easy.
YAMLs, CLI commands, complex setups, and a fear of “what if I break something?” often stop developers and SREs before they even begin. Even with tools like LitmusChaos, which simplify a lot of this, there’s still a learning curve, especially for those new to resilience testing.
That’s exactly what the LitmusChaos MCP Server aims to change.
The Challenge with Chaos Engineering
Chaos Engineering helps you intentionally inject failures into your systems to test how they respond.
But here’s the catch for many teams: it feels too technical, too complex, or too risky.
- You need to understand multiple CRDs and YAML definitions.
- You have to set up and manage chaos infrastructures.
- You have to know how to interpret experimental results.
And if you’re a developer or DevOps engineer already juggling deployments, observability, and CI/CD, adding “run chaos experiments” to that list can feel overwhelming.
Where LitmusChaos Fits In
LitmusChaos was built to solve exactly that. To make Chaos Engineering simpler, more organized, and more collaborative.
With ChaosCenter, you get a single pane of glass to:
- Run and manage chaos experiments.
- Track resilience scores.
- Monitor chaos infrastructures (agents).
- Visualize experiment runs and results.
It has helped teams integrate chaos into their CI/CD pipelines and production workflows.
But… even with all these features, there’s still one big barrier left: You still need to know how to use it.
Now imagine if you could talk to your system and say:
“Run a pod-delete experiment on the payment service in production.”
And it just does it.
That’s exactly what LitmusChaos MCP Server enables. It turns Chaos Engineering into a conversational experience.
No YAMLs. No CLI. No UI clicks.
Just natural language.
LitmusChaos MCP Server
The LitmusChaos MCP Server is a Go-based Model Context Protocol (MCP) server that connects your AI assistant (like Claude) directly to your ChaosCenter.
It provides a complete interface to:
- Manage experiments
- Control infrastructures
- Organize environments
- Run and monitor resilience probes
All through natural language interactions.
In simple words, the MCP Server acts as a bridge between your AI assistant and your Chaos Engineering setup, letting anyone perform chaos operations just by asking.
What You Can Do With It?
Here are some examples of what the MCP Server can handle through natural language:
1. Experiment Management
“List all chaos experiments.”
“Run the pod-delete experiment on the frontend pods.”
“Stop the network latency experiment.”
You can trigger, stop, or describe chaos experiments instantly.
2. Infrastructure Operations
“List all active chaos infrastructures.”
“Show me the status of the production infra.”
You get a complete overview of all connected Litmus agents.
3. Environment Organization
“Create a new environment called staging.”
“Show me all experiments in the PROD environment.”
Organize chaos operations by environments for better structure.
4. Resilience Probes
“Create an HTTP probe that checks the payment API every 5 seconds.”
“List all existing probes in my project.”
You can validate steady-state conditions or system health with simple requests.
5. Analytics & Monitoring
“Show me all failed experiments last week.”
“What’s the resiliency score of my production environment?”
It makes chaos data easy to access and interpret.
Getting Started with MCP Server
You can get up and running in just a few minutes.
Quick setup
# Clone and build
git clone https://github.com/litmuschaos/litmus-mcp-server.git
cd litmus-mcp-server
make build
Now, just add it to your Claude or any other MCP Host, and you’re ready to talk to your ChaosCenter through natural language.
Follow this guide to learn more about setting up the Litmus MCP server.
Why It Matters
The MCP Server is more than just a new integration; it’s a mindset shift for chaos engineering.
- For Developers: No more YAML confusion. Learn chaos the easy way.
- For SREs: Run, monitor, and analyze chaos experiments faster.
- For DevOps Teams: Automate resilience testing with AI-driven workflows.
- For Organizations: Empower every engineer, not just chaos experts, to build resilient systems.
It lowers the barrier of entry so that anyone, regardless of chaos experience, can perform meaningful resilience testing.
The Future of Accessible Chaos Engineering
The LitmusChaos MCP Server marks a big step forward, where Chaos Engineering meets AI-driven accessibility.
It makes resilience testing approachable, interactive, and intuitive.
The future of chaos isn’t about running YAML files; it’s about asking the right questions, getting answers, and improving system resilience effortlessly.
So go ahead, try it out, connect your assistant, and let’s make Chaos Engineering something everyone can do.
Top comments (0)