fileman
Related Servers
Alternatives to fileman
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to scan a messy folder, preview a dry-run plan that renames and sorts files into folders using a fully offline local model, then apply or undo it and surface duplicate files. Nothing is ever deleted — duplicates and old installers go to _tidy_trash/.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to intelligently organize files by scanning folders, detecting duplicates, suggesting meaningful names, and moving files into logical folders.MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to organize and manage Windows file systems with intelligent file analysis, automated grouping, renaming with date prefixes, and safe operations through dry-run mode and sandbox restrictions.1MIT
- FlicenseNot gradedqualityDmaintenanceLets AI assistants analyze and organize local directories by file type, with dry-run support and safe sorting.-
- AlicenseNot gradedqualityCmaintenanceA local-first, open-source harness for organizing your files with an AI agent.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to scan and search local photo libraries, maintain persistent selections across turns, preview grouping and export plans, and create albums or copy/compress photos while keeping originals in place.MIT
TDQS
Scored across 16 tools
Each tool targets a distinct action (list, get, create, preview, apply, scan, etc.) across different domains (jobs, manifest, review rules, inbox). Overlap is minimal, with only 'analyze.create' and 'inbox.analyze' slightly related but clearly differentiated by source.
All tools follow a consistent `domain.action` or `domain.subdomain.action` pattern using lower_snake_case. Verbs like list, get, create, preview, apply, scan are used uniformly, making the naming predictable.
With 16 tools, the set is well-scoped for a file management system covering jobs, manifests, review rules, inbox processing, settings, and reports. No tool feels redundant or missing in terms of count.
The tool surface covers core workflows (analyze, review, manifest patching, inbox scanning) but lacks execution tools for applying changes (only preview exists), job cancellation, or manifest creation. Some lifecycle gaps exist.