MCP Duplicate File Manager Server
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 |
|---|---|
| list_filesA | List files in a specified directory with optional filtering. Args: directory: Directory path to list files from (default: current directory) pattern: File pattern to match (e.g., ".py", ".txt") (default: "*") include_hidden: Whether to include hidden files (default: False) Returns: List of dictionaries containing file information (name, size, type, path) Example: list_files(directory=".", pattern="*.py") list_files(directory="/home/user/documents", include_hidden=True) |
| find_duplicatesA | Find duplicate files in a directory based on content hash. Args: directory: Directory path to search for duplicates (default: current directory) recursive: Whether to search recursively in subdirectories (default: True) Returns: Dictionary with hash as key and list of duplicate file paths as values Example: find_duplicates(directory="./documents") find_duplicates(directory="/home/user", recursive=False) |
| delete_duplicatesA | Delete duplicate files in a directory, keeping only one copy of each file. Uses intelligent copy detection to prioritize deleting files with copy indicators (like "copy", "(1)", "(2)", etc.) over original files. Args: directory: Directory path to search for duplicates (default: current directory) recursive: Whether to search recursively in subdirectories (default: True) dry_run: If True, only show what would be deleted without actually deleting (default: True) Returns: Dictionary with information about deleted files and preserved originals Example: delete_duplicates(directory="./documents", dry_run=True) # Preview only delete_duplicates(directory="./documents", dry_run=False) # Actually delete |
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
Each tool has a distinct purpose: list_files for directory exploration, find_duplicates for identifying duplicates, and delete_duplicates for removing them. There is no overlap or ambiguity between the tool functions.
All tools follow the verb_noun pattern with consistent snake_case and plural nouns (list_files, find_duplicates, delete_duplicates). The naming is uniform and intuitive.
With 3 tools, the server is tightly scoped to the core duplicate file management workflow. Each tool is essential and none are redundant, making the count appropriate.
The tool set covers the full lifecycle: listing files to explore, finding duplicates, and then deleting them with a dry-run option for safety. No critical operations are missing for the stated purpose.