DevGuard-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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_workspaceA | Scan a developer workspace for reclaimable artifacts, build files, virtualenvs, caches, and secret files. Args: path: Root directory to scan (defaults to current directory). max_depth: Max directory traversal depth (default: 6). artifact_types: Optional list of specific types to filter: ['node_modules', 'python_venv', 'python_cache', 'build_artifact', 'temp_logs', 'env_secret']. min_size_mb: Minimum item size in Megabytes to report (default: 0.0). Returns: Structured scan report with discovered items, sizes, categories, and secret warnings. |
| audit_workspace_secretsA | Audit workspace for security risks: untracked .env files, exposed API keys, and workspace hygiene. Args: path: Root directory to audit. Returns: Security audit report including health score (0-100), detected exposed .env files, embedded secret leaks, and hygiene recommendations. |
| preview_cleanupA | Dry-run simulation of workspace cleanup to inspect items and reclaimable space before executing. Args: path: Root workspace path. target_paths: Optional list of explicit paths to clean. artifact_types: Optional list of artifact types to target. older_than_days: Only include artifacts inactive for at least N days. Returns: Preview report with items that would be removed and total reclaimable bytes. |
| clean_workspaceA | Clean reclaimable developer artifacts with safety checks and Recycle Bin quarantine. IMPORTANT: Args: path: Root directory of the workspace. target_paths: Explicit paths to clean. If omitted, cleans all non-secret artifacts matching criteria. artifact_types: Filter specific artifact types to clean. mode: Deletion mode ('trash' for OS Recycle Bin quarantine, 'permanent' for direct deletion). dry_run: If True, simulates cleanup without removing files. Default is True. Returns: Clean report with status of removed items, freed space, and any errors. |
| get_workspace_healthA | Get high-level health overview and disk space metrics for a developer workspace. Args: path: Workspace root directory. Returns: Summary metrics (total reclaimable space, artifact count, secret alerts, category breakdown). |
| get_audit_historyA | Retrieve historical workspace audit scans and cleanup activity logs. Args: path: Optional workspace root directory to filter history. limit: Maximum number of records to return (default: 10). Returns: Historical scan records and cleanup logs with totals and metrics. |
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 6 tools
Most tools have clearly distinct purposes: audit focuses on security risks, scan on reclaimable artifacts, preview/clean are paired, history and health are distinct. The only potential overlap is between audit_workspace_secrets and scan_workspace, as both may detect secrets, but their descriptions emphasize different objectives (security audit vs artifact discovery).
All tool names follow a consistent verb_noun pattern in snake_case (audit, preview, get, clean, scan), with only minor variation like audit_workspace_secrets adding an extra noun. The style is uniform and predictable, making it easy to infer behavior from names.
Six tools is well-scoped for a workspace hygiene server, covering scanning, auditing, previewing, cleaning, health metrics, and history. Each tool serves a distinct function without redundancy, and the count feels neither sparse nor bloated.
The surface covers the core lifecycle: scan (discover), audit (security), preview (simulate), clean (execute), plus health and history. Minor gaps exist such as no explicit tool for managing exclusion lists or restoring from recycle bin, but these are not critical for the primary workflow.