mcp_file_manager
Related Servers
Alternatives to mcp_file_manager
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSecure file exchange MCP server enabling AI agents to upload, share, fetch, and revoke files with SHA-256 verification, malware scanning, expiry, access restrictions, and human approval workflows.11 npmMIT

YAFL MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely transfer files between machines via encrypted, expiring share links, with tools for upload, download, status checks, and link management.MIT- AlicenseNot gradedqualityCmaintenanceEnables local file exchange between users and CLI agents via a web UI and MCP server, allowing agents to read/uploads and deliver artifacts without copy-paste.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LibreChat agents to manage per-user private files, persistent documentation, RAG indexing and semantic search, and publish files via secure opaque public links.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to autonomously manage files on the Filecoin decentralized network through folder management, file uploads, and AI-powered semantic search. Provides seamless integration with Filecoin storage through simple MCP tool calls.2MIT
- FlicenseNot gradedqualityDmaintenanceA hybrid REST + MCP file server for managing files with large file streaming support, enabling AI agents and web frontends to perform file operations via MCP tools and REST APIs.-
TDQS
Scored across 9 tools
Each tool targets a distinct operation: upload, download, metadata lookup, listing, deletion, expiry extension, upload link creation, cleanup, and stats. There is no overlap that would cause an agent to confuse one tool with another.
All tool names follow a strict verb_noun pattern in snake_case (e.g., download_file, list_files, extend_expiry). The naming is perfectly uniform and predictable.
With 9 tools, the set is well-scoped for a file management server. Each tool serves a clear purpose without redundancy, and the count falls comfortably in the optimal 3-15 range.
The tool surface covers the full lifecycle of temporary file storage: create (upload_file, create_upload_link), read (download_file, get_file_info), list (list_files), update (extend_expiry), delete (delete_file, sweep_expired), and additional management (get_storage_stats). There are no obvious gaps.