mybox-mcp
Related Servers
Alternatives to mybox-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP clients to browse, search, download, and upload files in a NAVER MYBOX drive, plus inspect storage quota and create folders, all paced under the documented API rate limits. Read-and-write only: file deletion and trash management are deliberately not exposed.7MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to manage files on Synology NAS via the File Station API, supporting operations like browsing, searching, uploading/downloading, creating, renaming, copying, moving, deleting, compressing, and extracting.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Box files, folders, collaborations, and more via the Box API using tools for search, upload, and metadata operations.5 npmISC
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Google Drive, supporting file operations like list, search, read, create, update, delete, share, and manage permissions.72,911 npm4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to access Yifangyun cloud drive via MCP, supporting queries of enterprise organization, department folders, file details, and download links.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to browse, search, inspect, and download text from Box enterprise cloud storage files and folders, and to retrieve user profile and storage usage details.51 npmMIT
TDQS
Scored across 20 tools
Most tools target a distinct resource+action (list, copy, move, rename, delete, trash, favorite, search). Minor overlap exists between dms_storage and dms_resourceId (both 'property inquiry') and between dms_root and dms_list, but descriptions clarify most boundaries.
Three prefix families coexist (dms_, files_, search_) with mixed structure: some dms_ tools are nouns (dms_storage, dms_root), others are verbs (dms_favorite, dms_unfavorite), plus camelCase suffixes (dms_resourceId, files_trash_clean_resourceId) mixed with snake_case. Still readable but not one predictable pattern.
At 20 tools the surface is on the heavy side for a file manager, but each tool maps to a genuine operation (CRUD, trash lifecycle, search, favorites, storage). A few could be consolidated (search_files/search_folders, dms_root/dms_list) but nothing feels redundant filler.
Strong lifecycle coverage: list/properties, create folder, upload/download, copy/move/rename/delete, full trash management (list/restore/clean/clean-one/routine), search, and favorites. Gaps are secondary features like sharing/permissions, file creation, or versioning rather than core workflows.