Yandex.Disk MCP Server
A small Python MCP server for Yandex Disk: browse, upload, download and create files, but never modify existing ones
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Uploads and creates files on the user's Yandex Disk
- The OAuth token grants access to disk contents per the application's rights
Install
Manual install
git clone https://github.com/yermidi-bot/yandex-disk-mcp.git
cd yandex-disk-mcp
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txtInstall from source with a virtual environment.
This is third-party code. Review the repository files before installing.
What it does
The Python server gives an agent six Yandex Disk tools: list files and folders, get file info, upload a local file to the disk, download a file from the disk, create a new file with text content, and create a folder. The author deliberately left out editing existing files, so an agent cannot accidentally change or overwrite them.
Who it is for. For people who want simple, safe agent access to Yandex Disk without risking already-saved files.
Good fit when
- You want an agent to save new files and results to Yandex Disk
- You need a quick way to list files and see file info from a conversation with an agent
- You want to rule out the risk of accidentally editing or overwriting existing files
Not a fit when
- You need to edit or overwrite existing files: the server deliberately does not support this
- You need folder operations beyond creation: renaming, moving and deleting are not implemented
Example request
Save this report as report.txt into the reports folder on Yandex DiskLimitations
There is no PyPI package; install is from source via requirements.txt and a virtual environment. A Yandex OAuth token with Yandex Disk access is required. Maximum file size and rate limits depend on the Yandex Disk plan and API docs, which the README does not spell out.
How to disable. Stop the server process and revoke the Yandex OAuth token at oauth.yandex.ru.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_OAUTH_TOKEN required, secret | OAuth token for an application with Yandex Disk access |
Security check
- Uploads and creates files on the user's Yandex Disk
- The OAuth token grants access to disk contents per the application's rights
README in short
The Russian README lists six server capabilities and explicitly notes the ban on editing existing files as protection against accidental changes. It gives setup steps via a virtual environment and requirements.txt, instructions for getting a Yandex OAuth token two ways, and JSON parameter examples for each tool. It separately notes file-size and API rate limits. MIT license.
FAQ
Can the agent modify a file that already exists on the disk?
No, editing existing files is deliberately not implemented, as a guard against accidental changes.
How do I get an OAuth token?
Create an application at oauth.yandex.ru with Yandex Disk access and get an access_token through browser authorization or by exchanging a code for a token.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI