Documents & filesYandex Disk

Install the Yandex Disk CLI and MCP server

Install the Yandex Disk CLI with npm, get a Yandex token and sign in with a profile.

Set up ydisk once on each computer where you or an agent use it. After these steps your Disk is connected under a profile name you choose, and the first search works. Signing in means pasting a Yandex OAuth token: a key that Yandex gives you for your own account, which lets the tool use your Disk. Getting it takes about five minutes, once.

On this page:

  1. Install the tool
  2. Get a Yandex token
  3. Sign in
  4. Check that it works
  5. A computer with no keyring
  6. Update
  7. Remove

Install the tool

You need Node.js 22.16 or a later 22.x, or 24 or later. Node 23 is not supported. Check your version with node --version, and get Node.js from nodejs.org if it is missing or older.

npm install -g @wirecat/yandex-disk-cli
ydisk --version
ydisk doctor

doctor needs no network and opens no keyring. It shows the version, where the settings and the local store live, the profiles that exist, and whether other users of the computer can read the settings. To try the tool without installing it, run npx @wirecat/yandex-disk-cli --help.

Get a Yandex token

Yandex gives a token to an app that you register for yourself. The app is only a name and a list of access rights in your Yandex account. Nothing is published. These steps follow Yandex's own guides: register an app for API access and the Disk API quick start. Yandex's pages are in Russian, so the labels below are given in Russian too.

  1. Open oauth.yandex.ru/client/new and sign in to Yandex with the account whose Disk you want to use. If Yandex shows a choice of app type, choose For API access or debugging («Для доступа к API или отладки»).
  2. Enter any name for the app («Название вашего сервиса»), such as My laptop, and your email («Контактная почта»).
  3. Under data access («Доступ к данным»), add the Yandex Disk rights the tool needs:
    • cloud_api:disk.read, read the whole Disk («Чтение всего Диска»).
    • cloud_api:disk.info, read information about the Disk («Доступ к информации о Диске»). The tool uses it to check whose token it is.
    • cloud_api:disk.write, write anywhere on the Disk («Запись в любом месте на Диске»), for uploads, moves, deletes and public links. Leave it out for a token that can only read. Every change then fails.
  4. Create the app («Создать приложение»). Its page shows a ClientID, a string of letters and digits. Copy it.
  5. Open this address in the browser, with your ClientID added at the very end, after client_id=: https://oauth.yandex.ru/authorize?response_type=token&client_id=
  6. Yandex asks whether to allow the app access to your Disk. Allow it, and Yandex shows the token on its page. Copy it.

Yandex may ask to confirm your identity before it lets you create apps. Without the confirmation it shows a warning and limits how many apps you can create, which does not stop you here. See Yandex's page on it.

Keep the token like a password. Anyone who has it can use your Disk with the rights you chose.

Sign in

Choose a profile name for this account, such as personal, and sign in under it. The tool asks for the token with hidden input. Paste it and press Enter.

ydisk personal session start

The tool checks the token with Yandex first, and keeps it only if Yandex accepts it. It is kept in the system keyring (Keychain on macOS, Credential Manager on Windows, Secret Service on Linux). The token is never a command argument and never appears in the output or a log.

session start also reads the token from stdin, so a script can pipe it in from a password manager. A second account gets its own profile: ydisk work session start.

Check that it works

ydisk personal session status --check
ydisk personal folders browse

session status --check asks Yandex whose token it is and shows the account. folders browse lists the folders at the top of your Disk. Both answer from Yandex, so a working answer means the sign-in is done.

Yandex keeps a token valid for months and extends it while it is used (Yandex ID). When Yandex stops accepting it, the commands fail with exit code 4: get a new token the same way and run session start again.

ydisk personal session end removes the token from this computer.

A computer with no keyring

On a server or a container without a keyring, the tool keeps the token in a private file only you can read, and says so. To skip the keyring on purpose:

ydisk personal session start --credential-storage file

Update

ydisk upgrade

ydisk upgrade --check only says whether a newer version exists. After an update, run ydisk skill install again so your agent's instructions match the new version.

Remove

ydisk personal session end forgets the profile's token on this computer. Then remove the tool:

npm uninstall -g @wirecat/yandex-disk-cli

The settings and the local store stay in the folders ydisk doctor showed, for the other WireCat tools that share the store. Delete them by hand if you no longer need them.

Next: choose folders and sync them.