CloudSee Drive MCP Server
Related Servers
Alternatives to CloudSee Drive MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables browsing S3 buckets and objects, and generating secure presigned URLs for downloads and uploads, through natural language commands in MCP clients like Claude Desktop.36 npm3MIT
- AlicenseAqualityDmaintenanceEnables Google Drive file operations (search, read, create, download, etc.) through natural language, compatible with Claude.ai's Drive connector.182MIT
- AlicenseNot gradedqualityAmaintenanceProvides MCP tools for AWS S3 and S3-compatible storage, enabling file upload, download, listing, deletion, and temporary remote file staging via natural language.BSD 3-Clause
- FlicenseNot gradedqualityBmaintenanceProvides basic filesystem operations such as listing directories, reading/writing files, retrieving file info, and searching for files, enabling natural language file management.-
- AlicenseAqualityCmaintenanceEnables advanced file system operations such as file read/write, directory management, search, archiving, and file watching through natural language.1616 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of Google Drive files, Docs, Sheets, and Slides through natural language using MCP, with support for file operations, search, and shared drives.6 npmMIT
TDQS
Scored across 19 tools
Most tools are clearly distinct in purpose, but the listing tools (browse_folder, search_files, list_files, recent_files) overlap in functionality. Each has detailed descriptions explaining the differences, so an agent can differentiate them, but they could still cause misselection if descriptions are not read carefully.
All tool names use snake_case and predominantly follow a verb_noun pattern (list_buckets, download_file, move_file). A few like recent_files and get_version deviate slightly, but the overall convention is consistent and predictable.
With 19 tools, the server covers a wide range of drive operations (browse, search, upload, download, manage metadata, share, archive restore). While on the higher end, each tool serves a distinct function that justifies its inclusion for a comprehensive drive API.
The tool set covers the full lifecycle of file management: create, read, update, delete, plus metadata, tags, sharing, and archiving. Minor gaps exist, such as no share revocation or bulk operations, but these are not critical for core workflows.