Yandex Disk

Yandex Disk

This connector works with one Yandex Disk (Яндекс Диск) through the Yandex Disk REST API (https://cloud-api.yandex.net/v1/disk), signed in with the user's Yandex account: Disk totals, folder listings, a flat list of all files, recent uploads, file details, download links, folders, copy, move, public links, saving a file from a URL, the Trash and background operations.

Paths look like disk:/folder/file.txt; disk:/ is the root, and Trash entries are trash:/.... Use forward slashes and the exact names, including the extension.

Setup (about 5 minutes)

1. Sign in with the Yandex account whose Disk you want to use, open https://oauth.yandex.ru/client/new (or oauth.yandex.com) and create an app.
2. Platform: Web services. Redirect URI: https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself.
3. Data access: add the Yandex Disk REST API permissions cloud_api:disk.read (read all of the Disk), cloud_api:disk.write (write anywhere on the Disk) and cloud_api:disk.info (Disk information). Do not choose cloud_api:disk.app_folder alone: it limits the app to its own folder.
4. Create the app, copy ClientID into YANDEX_DISK_CLIENT_ID and Client secret into YANDEX_DISK_CLIENT_SECRET, and install.
5. On the connector page click Authorize with Provider, pick the Yandex account and allow access. Run yandex_disk_get_disk_info to check.

Scopes: the authorization request names no scope, so Yandex grants exactly the permissions ticked in the app (step 3). For a read-only setup, register the app with cloud_api:disk.read and cloud_api:disk.info only and switch off the write tools.

Tokens: Yandex sends the token as Authorization: OAuth <token> (the word OAuth, not Bearer); the connector does this for you. Yandex tokens last about a year and come with a refresh token, which AnythingMCP uses to renew them. Revoking the app at https://id.yandex.ru/security (or changing its permissions) means authorizing again.

Writes: confirm first. Creating folders, copying, moving, publishing, unpublishing, uploading from a URL and restoring change the Disk. Say what will happen and wait for the user's yes. yandex_disk_publish makes a file readable by anyone with the link. yandex_disk_delete is installed switched off; when enabled it moves to the Trash by default (permanently false) and only deletes for good with permanently true.

Background operations: copy, move, restore and delete of large folders, and every upload from a URL, run in the background. Yandex then answers 202 with href ending in /operations/<id>; poll yandex_disk_get_operation_status with that id until status is success or failed.

No search: the Yandex Disk REST API has no full-text or file-name search. List a folder with yandex_disk_list_folder, or page through yandex_disk_list_files (all files, filter by media_type) and compare names.

File contents: this connector does not read or upload file bytes. yandex_disk_get_download_link returns a temporary URL the user can open; yandex_disk_upload_from_url saves a file that is already on the internet.

Common errors (error, an English description and a Russian message in the body)

• 401 UnauthorizedError: the sign-in is missing, revoked or expired; authorize again.
• 403: the app lacks the permission (e.g. no cloud_api:disk.write for a write), the Disk is over its quota, or it is in read-only mode.
• 404: the path does not exist; check the spelling, the extension and the disk:/ prefix.
• 409: the target already exists (use overwrite only with the user's consent), or the parent folder of the target is missing.
• 423: the resource is locked by another operation, or uploads are paused; retry later.
• 507: not enough free space on the Disk.
• 429: too many requests; wait and retry once.

Out of scope here: uploading or reading file bytes, custom properties, emptying the Trash, sharing folders with specific people, and Yandex 360 admin settings.