yadisk-mcp
Related Servers
Alternatives to yadisk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for performing filesystem operations, enabling file management and manipulation through natural language.MIT
- AlicenseAqualityDmaintenanceMCP server for Yandex Metrika API, enabling reporting, counter management, goals, filters, and other operations via natural language.122MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for Yandex 360 that provides 28 tools for Disk, Telemost, and Messenger, plus an escape hatch for undocumented endpoints.MIT
- AlicenseBqualityAmaintenanceMCP server for managing Yandex Cloud infrastructure including Compute VMs, Object Storage, Serverless Functions, and Operations.87 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Yandex Mail that enables reading, searching, sending, and managing emails via IMAP and SMTP.8-
- AlicenseNot gradedqualityAmaintenanceMCP server for Google Drive that enables listing, searching, uploading, downloading, and managing files and folders, as well as handling comments and permissions.66 npm5MIT
TDQS
Scored across 22 tools
Each tool targets a distinct operation or resource: listing files vs recent vs search, upload local vs background vs URL, trash management vs deletion. The only near-overlap (upload_local_file vs upload_local_file_background) is explicitly distinguished by blocking behavior and file size, so no ambiguity remains.
The majority of tools follow a verb_noun pattern (list_files, search_files, get_metadata, create_folder, upload_local_file). However, a few tools deviate: bare verbs (delete, copy, move, rename, publish, unpublish) and a noun phrase (disk_info). All names are lowercase snake_case, keeping the set readable and mostly predictable.
With 22 tools, the server is on the heavier side, but the breadth of Yandex Disk functionality—file operations, uploads (local, background, URL), trash lifecycle, sharing, and disk info—justifies the count. The tools are neither redundant nor trivial, so the size feels appropriate rather than bloated.
The toolset covers the core file lifecycle (create, list, get, copy, move, rename, delete, trash), uploads from multiple sources, download URLs, publishing/unpublishing, and public resource access. Minor gaps exist, such as no direct file content download (only a URL) and no metadata update, but these are workable given the provided capabilities.