idrive-mcp-server
Related Servers
Alternatives to idrive-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables MCP-compatible AI assistants to interact with a user's Google Drive, including listing, searching, reading, creating, updating, and deleting files, with authentication via Google OAuth.-
- 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.5 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to browse, read, write, move, copy, and delete files on WD MyCloud Home devices, supporting local SMB and remote REST API connections with automatic token refresh.12Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables MCP-enabled assistants to search, inspect, and restore archived files from an encrypted restic repository via find, show, and get operations.2-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to analyze, audit, deduplicate, and organize Google Drive content through MCP, including storage checks, exact and semantic duplicate management, empty folder cleanup, archiving, and sync health monitoring.1MIT
- AlicenseAqualityAmaintenanceEnables AI apps to work with Google Drive in plain language, including searching, organizing, uploading, downloading, exporting, sharing, and commenting on files, with reversible trash and configurable access scopes.21506 npmMIT
TDQS
Scored across 15 tools
Most tools target clearly distinct resources and actions, but list_files and browse_folder overlap in core purpose: both list backed-up files at a path, differentiated only by endpoint richness and path format. The rest of the set is cleanly separated into read, download, and mutation roles.
All tools use lowercase snake_case verb_noun names: get_, list_, browse_, download_, create_, delete_, restore_. The pattern is consistent throughout, with no camelCase mixing or vague verbs.
15 tools sits at the upper edge of the well-scoped range but is reasonable for a backup/restore server spanning account diagnostics, device/file browsing, downloads, and mutations. A few tools like get_dashboard and get_server_version are peripheral, but they do not make the set feel bloated.
The set covers the main restore-oriented workflow: discover devices, browse files, fetch metadata/versions/thumbnails, download content, and perform trash-safe mutations. Obvious gaps are the lack of trash enumeration and file search, but these are minor relative to the core backup-restore surface.