File-Delete-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILE_DELETE_ROOT | No | Workspace root for the MCP server. Defaults to the MCP process current directory. Can alternatively be set with the --root command-line option. Relative paths are resolved against this root, and absolute paths must stay within it. |
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 |
|---|---|
| preview_deleteA | Validate a delete request and issue a one-time ticket. scope="trash" previews moving paths into the workspace .del directory; set recursive=true to allow non-empty directories. scope="purge" previews permanently deleting .del batches selected by batch_ids, older_than_days, or all=true. A blocked request returns risk="block" and no ticket. |
| trash_pathsA | Move previewed paths into the workspace .del directory. The ticket must come from preview_delete with scope="trash" and the same paths and recursive flag. Paths or files changed after preview are refused. |
| purge_delA | Permanently delete .del batches selected by the matching purge preview. The ticket must come from preview_delete with scope="purge". Batches added or changed after preview are refused. |
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 3 tools
preview_delete is clearly a validation/ticket step, while trash_paths and purge_del execute distinct operations on different targets (workspace paths vs .del batches). The dual scope in preview_delete is explicitly described, so the overlap is minimal and predictable.
All names use snake_case with a leading verb, giving a consistent verb_noun pattern. The noun forms vary slightly (delete vs paths vs del), and 'purge_del' abbreviates 'delete' while 'preview_delete' spells it out, which is a minor inconsistency.
Three tools match the narrow, safety-focused deletion domain: one preview/authorization tool and two execution tools. Each tool has a clear role in the workflow, with no redundant surface.
The soft-delete and permanent-purge lifecycle is covered end-to-end with preview/ticket enforcement. A dedicated listing or inspection tool for .del batches (and possibly restore) is absent, which is a minor gap for selective purge by batch_ids, though broad selectors mitigate it.