litmus

LitmusChaos MCP Server is a Go-based MCP server that provides a comprehensive control plane for managing LitmusChaos resources through AI-assisted interactions. It exposes a rich set of tools to manage chaos experiments, infrastructures, environments, resilience probes, chaos hubs, and analytics. With this MCP server, you can list, describe, run, stop, and monitor experiments; manage infrastructures and environments; create resilience probes; browse ChaosHubs and faults; and fetch statistics and run details. The server is designed to integrate with AI assistants or vault-like assistants (e.g., Claude) to enable natural-language driven chaos engineering workflows. Typical usage flows include listing available experiments, triggering on-demand experiments, monitoring live runs, and querying for historical results and resiliency scores. Tools are grouped by areas like Experiment Management, Execution Monitoring, Infrastructure Management, Environment Organization, Resilience Validation, and Discovery & Analytics, enabling precise natural-language queries such as “Show me all production experiments with status running” or “Create an HTTP resilience probe for the payment API.”

Prerequisites:

• Go 1.21 or higher (for building from source)
• Docker (optional, for containerized deployment)
• Access to a LitmusChaos 3.x Chaos Center and valid credentials

From Source

1. Clone the repository git clone https://github.com/yourusername/litmuschaos-mcp-server.git cd litmuschaos-mcp-server

2. Build the binary make build

3. Install locally make install

Using Go Install

1. Install the latest release go install github.com/yourusername/litmuschaos-mcp-server@latest

Using Docker

1. Build the Docker image (if a Dockerfile is provided in repo) make docker-build

2. Run with required environment variables docker run --rm -it
   -e CHAOS_CENTER_ENDPOINT=http://your-chaos-center:8080
   -e LITMUS_PROJECT_ID=your-project-id
   -e LITMUS_ACCESS_TOKEN=your-token
   litmuschaos-mcp-server:latest

Tips and common issues:

• Ensure CHAOS_CENTER_ENDPOINT, LITMUS_PROJECT_ID, and LITMUS_ACCESS_TOKEN are correctly set; missing or invalid credentials will prevent API access.
• When using Docker, prefer mounting environment-specific values and consider using a secret manager for tokens.
• If you encounter connectivity issues, verify Chaos Center is reachable from the MCP server host and that firewalls allow access.
• For development workflows, the repository supports hot-reload development setup with Makefile targets (dev, build, test, etc.).
• The MCP server supports multiple environments and can filter operations by environment or namespace depending on setup; use DEFAULT_INFRA_ID and DEFAULT_ENVIRONMENT_ID to simplify common commands.
• When using Claude or other assistants, ensure the MCP server endpoint in your client configuration points to the MCP server (e.g., http://localhost:8080) and that the environment variables align with your deployment.