Config Drift Detector
Compare live configurations across environments and flag drift
Example Prompt
Check for configuration drift between our staging and production Redis environments
About
Detects configuration drift by reading configuration values from Redis across different environments (development, staging, production), comparing them to the canonical configuration stored in your repository, and flagging any discrepancies. A detailed drift report highlights which keys differ, their expected vs. actual values, and the risk level of each deviation.
Workflow Steps
Read live configuration values from Redis for each environment
🔑 Get KeyRead the canonical configuration file from the repository as the source of truth
📃 Read Repo FileReason through differences between live and canonical configs to assess drift severity
🧠 Structured ReasoningWrite a drift report detailing all discrepancies with risk levels and remediation steps
✏️ Write FileTools Used
Write File
Write or overwrite a file at a specified path with the given content
Read Repo File
Read the contents of a file from a GitHub repository at a specific branch or commit
Get Key
Retrieve the value of a key from a Redis datastore
Structured Reasoning
Break down a complex problem into sequential reasoning steps with explicit chain-of-thought
Required MCP Servers
Filesystem
Read, search, and manage files on the local filesystem
GitHub
Access GitHub repos, issues, PRs, and code search via the official MCP server
Redis
Read, write, and manage keys in Redis for caching and real-time data
Sequential Thinking
Dynamic problem-solving through structured thought sequences with branching and revision