Chaos Mesh MCP Server
Related Servers
Alternatives to Chaos Mesh MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform chaos engineering and resilience testing on Kubernetes clusters through Chaos Mesh. Supports creating and managing 24 types of chaos experiments including network failures, stress tests, pod disruptions, and I/O faults through natural language conversations.2MIT
- FlicenseAqualityCmaintenanceEnables diagnosing Kubernetes clusters without creating or changing cluster objects, with tools to inspect health, workloads, events, storage, RBAC, custom resources, logs, and configuration.18-
- AlicenseAqualityDmaintenanceYour proactive chaos engineering companion that analyzes infrastructure code and designs targeted resilience experiments before problems occur.13MIT No Attribution
- FlicenseNot gradedqualityDmaintenanceEnables real-time Kubernetes cluster observability and debugging through standardized MCP interface. Provides access to pods, services, nodes, events, and includes built-in tools for cluster health analysis and issue identification.-
- FlicenseNot gradedqualityDmaintenanceEnables exploration of Kubernetes metrics, logs, traces, and service graph data via simple tools.1-
- AlicenseNot gradedqualityBmaintenanceEnables natural language Kubernetes operations, including smart resource queries, pod root-cause analysis, cross-environment diffs, and manifest generation.MIT
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose. The two delay tools are explicitly disambiguated in their descriptions, and other tools cover different fault types or informational queries without overlap.
Most tools follow a verb_noun pattern (e.g., delete_chaos, list_chaos, pod_kill), but there are minor inconsistencies like 'httpchaos_delay' (combined prefix) and 'network_external_delay' (three-part name) which mildly deviate from the norm.
With 12 tools, the server covers core chaos engineering operations (query, inject, delete) for multiple fault types, without being overwhelming or too sparse.
The set includes common fault types (pod kill, network delay/loss, HTTP delay) and external delay, but lacks stress chaos injection tools despite listing them, and does not support update operations, leaving notable gaps.