Install
$ agentstack add mcp-coding-dev-tools-configdrift ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
ConfigDrift
[](https://github.com/Coding-Dev-Tools/configdrift/stargazers)
Keep configurations consistent across all environments, automatically. ConfigDrift compares configs, flags drift, and reports compliance violations before they cause incidents.
> ⭐ Star this repo if you manage multi-environment configs — it helps other devs find ConfigDrift!
[](https://github.com/Coding-Dev-Tools/configdrift/releases)
[](https://github.com/Coding-Dev-Tools/configdrift/blob/main/LICENSE) [](https://www.opensourcealternative.to/project/configdrift) |[](https://www.libhunt.com/r/Coding-Dev-Tools/configdrift) |[](https://pypi.org/project/configdrift/)
Real-world scenarios:
- Multi-environment compliance: Ensure staging and prod configs are identical before every deploy
- Secrets audit: Detect env vars that exist in one environment but are missing in another
- CI/CD gating: Block PRs that introduce config drift across environments
- Incident prevention: Catch a changed database endpoint before it causes a production outage
Installation
pip install git+https://github.com/Coding-Dev-Tools/configdrift.git
Editable install for development:
pip install -e ".[dev]"
Then run: configdrift --help
Quick Start
Compare two config files:
configdrift check dev.yaml prod.yaml
Scan entire directories as environments:
configdrift scan ./config/dev ./config/staging ./config/prod
Use a config file to define environments:
configdrift init
configdrift scan --config .configdrift.yaml
Usage
check — Compare config files
configdrift check [--output table|json|silent] [--baseline dev] [--target prod]
Output formats:
table(default): Rich colored table outputjson: Machine-readable JSON for CI integrationsilent: Exit code only (0 = no breaking drift, 1 = breaking drift found)
scan — Compare environment directories
configdrift scan ./dev ./staging ./prod --baseline dev
Scans all config files in each directory, merges them, and compares against a baseline environment.
init — Generate a config file
configdrift init .
Creates .configdrift.yaml in the specified directory.
CI/CD Integration
Use --output silent for CI gating:
configdrift check dev.yaml prod.yaml --output silent || echo "Drift detected!"
GitHub Actions example
- name: Detect config drift
run: |
pip install configdrift
configdrift check ./config/staging/app.yaml ./config/prod/app.yaml --output silent
Troubleshooting
- Exit code 1 with no output: use
--output tableto inspect drift details. - **TOML parsing errors on Python
Part of Revenue Holdings — CLI tools built by autonomous AI.
License
MIT
Test
npm test # runs: node --test tests/
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Coding-Dev-Tools
- Source: Coding-Dev-Tools/configdrift
- License: MIT
- Homepage: https://coding-dev-tools.github.io/devforge/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.