janitor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| janitor_system_healthA | RAM/swap/tmpfs health: used/free RAM and swap, /tmp tmpfs utilization, CPU load and the top-5 processes by resident memory. alert=true past 85% RAM or 80% /tmp. |
| janitor_scan_orphansA | Scan this user's processes for suspected orphaned development workers (PPID=1, dead parent, zombie): headless browsers, agent runners, detached compilers and python sub-workers. |
| janitor_sweep_processesA | Terminate processes safely. Provide explicit pids and/or target_type='orphans'|'browsers'|'compilers'. dry_run=true (default) only reports; force=true allows SIGKILL after a 3s SIGTERM grace. systemd, compositors, sshd, shells and OrquestraAI are always refused. |
| janitor_clean_cachesA | Clean transient caches. targets: sockets (dead ~/.orquestra/*.sock), staging (.codex marketplace staging), testing_scratch (/var/tmp/testing). older_than_hours=6 gates every removal; dry_run=true (default) only reports. |
| janitor_oom_inspectA | Inspect oom_score and oom_score_adj for active agent runners to show kernel sacrifice priority under memory pressure, with recommendations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a fairly distinct role: health monitoring, orphan scanning, process termination, cache cleaning, and OOM inspection. The only mild overlap is between janitor_scan_orphans (read) and janitor_sweep_processes with target_type='orphans' (write), but the descriptions make the scan-vs-act split clear.
All five tools use a uniform janitor_ prefix followed by a snake_case verb_noun pattern (system_health, scan_orphans, sweep_processes, clean_caches, oom_inspect). The convention is consistent throughout with no style deviations.
Five tools is well-scoped for a system janitor: monitor, scan, terminate, clean, and inspect. Each tool earns its place with no redundant or filler operations.
The surface covers the core janitor lifecycle: observe health, find orphans, kill processes, clean caches, and assess OOM priority. Minor gaps exist, such as no general disk-usage reporting beyond tmpfs/swap or a way to list configured cache targets, but core workflows are covered.