yadisk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YANDEX_DISK_TOKEN | Yes | OAuth token for Yandex Disk API access. Required for all operations. | |
| YADISK_MCP_READ_ONLY | No | Set to 'true' to enable read-only mode, disabling write operations. Alternative to --read-only flag. | |
| YADISK_MCP_UPLOAD_ALLOWED_DIRS | No | Comma-separated list of allowed directories for file uploads. Restricts local file access. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| disk_infoA | Get Yandex Disk quota and usage information. |
| list_filesA | List files and folders at the given Yandex Disk path. Args: path: Path on Yandex Disk (e.g. "/" or "/Documents"). limit: Max items to return (1–100). offset: Offset for pagination. sort: Sort field: name, created, modified, size. Prefix with "-" for descending. |
| list_recent_filesA | List recently uploaded files across the entire disk. Args: limit: Max number of files to return (1–100). |
| search_filesA | Search for files on Yandex Disk by name. Args: query: Search query string. limit: Max results (1–100). media_type: Optional media type filter: audio, backup, book, compressed, data, development, disk_image, document, encoded, executable, flash, font, image, msi, text, unknown, video, web. |
| get_metadataB | Get metadata for a file or folder. Args: path: Path on Yandex Disk (e.g. "/Documents/file.txt"). |
| create_folderA | Create a folder (including intermediate directories). Args: path: Path of the folder to create (e.g. "/Documents/NewFolder"). |
| deleteA | Delete a file or folder. Args: path: Path to delete (e.g. "/Documents/old_file.txt"). permanently: If True, skip trash and delete permanently. Default False. |
| copyA | Copy a file or folder to a new location. Args: src: Source path (e.g. "/Documents/file.txt"). dst: Destination path (e.g. "/Archive/file.txt"). overwrite: Overwrite destination if it exists. |
| moveB | Move a file or folder to a new location. Args: src: Source path (e.g. "/Documents/file.txt"). dst: Destination path (e.g. "/Archive/file.txt"). overwrite: Overwrite destination if it exists. |
| renameA | Rename a file or folder (moves it within the same directory). Args: path: Full path of the item (e.g. "/Documents/old_name.txt"). new_name: New name without path (e.g. "new_name.txt"). |
| get_download_urlA | Get a temporary direct download URL for a file. Args: path: Path on Yandex Disk (e.g. "/Documents/report.pdf"). |
| upload_local_fileA | Upload a local file to Yandex Disk (blocking). Use for files under ~100 MB. For large files use upload_local_file_background to avoid timeout. Args: local_path: Absolute path to the file on the local filesystem. disk_path: Destination path on Yandex Disk (e.g. "/Videos/video.mp4"). overwrite: Overwrite if file already exists on Yandex Disk. |
| upload_local_file_backgroundA | Start uploading a large local file to Yandex Disk in the background. Returns immediately with a job_id. Use get_upload_status(job_id) to check progress. Suitable for files of any size — no timeout issues. Args: local_path: Absolute path to the file on the local filesystem. disk_path: Destination path on Yandex Disk (e.g. "/Videos/big_video.mp4"). overwrite: Overwrite if file already exists on Yandex Disk. |
| get_upload_statusB | Check the status of a background upload started with upload_local_file_background. Args: job_id: The job ID returned by upload_local_file_background. |
| list_upload_jobsA | List all background upload jobs and their statuses. |
| upload_from_urlA | Upload a file to Yandex Disk by downloading it from a remote URL. Args: url: Source URL to download the file from (must be http or https). path: Destination path on Yandex Disk (e.g. "/Downloads/file.zip"). overwrite: Overwrite if file already exists. |
| publishA | Publish a file or folder and return its public URL. Args: path: Path on Yandex Disk to publish (e.g. "/Documents/presentation.pdf"). |
| unpublishA | Revoke public access to a file or folder. Args: path: Path on Yandex Disk (e.g. "/Documents/presentation.pdf"). |
| get_public_resourceA | Get information about a public resource by its public key or URL. Args: public_key: Public key or public URL of the resource. path: Sub-path within a public folder (use "/" for root). limit: Max items to list if the resource is a folder. |
| list_trashA | List files in the Trash. Args: limit: Max items to return (1–100). offset: Offset for pagination. |
| restore_from_trashA | Restore a file or folder from Trash. Args: path: Path of the item in Trash (e.g. "/trash/old_file.txt"). destination: Optional new path to restore to. Uses original path if omitted. overwrite: Overwrite if destination already exists. |
| empty_trashA | Permanently delete all files in Trash. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.