Gitignore Drift Monitor
Register this MCP server when you want automated visibility into how many untracked or uncommitted files are piling up and which drift class dominates.
Overview
Gitignore Drift Monitor is an Operate-phase MCP server that counts uncommitted files in your repo and raises YELLOW or RED alerts based on drift severity.
What is this MCP server?
- Counts uncommitted files across the active repo workspace
- Surfaces the dominant drift class for quick triage
- YELLOW alert when count exceeds 100 files
- RED alert when count exceeds 250 files
- MIT-licensed DailyAI Agents federation watcher (spec 1.0)
- YELLOW threshold: more than 100 uncommitted files
- RED threshold: more than 250 uncommitted files
- Server version 0.1.0, MIT license
What problem does it solve?
Agent-heavy repos silently accumulate hundreds of untracked files until you cannot tell signal from noise or your .gitignore is wrong.
Who is it for?
Indie builders running daily AI coding agents on one repo who want automatic drift thresholds without building custom git scripts.
Skip if: Teams that already enforce pre-commit hooks and pristine CI workspaces with no local agent artifact churn.
What do I get? / Deliverables
You get a continuous drift class and file-count signal so you fix .gitignore or clean the tree before commits and releases.
- Live uncommitted file count for the watched repo
- Dominant drift class label for triage
- YELLOW or RED status when thresholds are exceeded
Recommended MCP Servers
Journey fit
Canonical shelf is Operate because the server is a always-on watcher over working-tree hygiene, not a one-off build or ship task. Monitoring fits counting uncommitted files and surfacing YELLOW/RED drift classes before they become merge or deploy surprises.
How it compares
MCP repo watcher with tiered alerts, not a git skill that edits .gitignore for you.
Common Questions / FAQ
Who is gitignore-drift-monitor for?
Solo and indie developers using MCP-enabled agents who need early warning when uncommitted or ignored-file drift grows past manageable size.
When should I use gitignore-drift-monitor?
Use it during Operate and active Build cycles whenever agents generate local files and you want YELLOW above 100 files and RED above 250.
How do I add gitignore-drift-monitor to my agent?
Register the io.github.dailyaiagents-cpu/gitignore-drift-monitor MCP server from the DailyAI OS package in your client’s MCP config and point it at the repo you want watched.