Yandex 360 MCP: Disk, Telemost and Messenger
mcp-yandex360
A 28-tool MCP server covering Yandex 360 Disk, Telemost and Messenger in one process
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- The tools delete files on Disk, delete messages, and change Messenger chat membership
Install
Manual install
python3 -m venv .venv && ./.venv/bin/pip install -r requirements.txtDependency install from the README.
This is third-party code. Review the repository files before installing.
What it does
The server bundles three Yandex 360 services that, per the author, had no dedicated public MCP servers before. Disk gets file read and write, folders, search, publishing and unpublishing links, and deletion. Telemost gets create, get, update and delete a meeting, plus org settings. Messenger gets sending text and files, creating a chat, updating membership, fetching updates and deleting a message. A separate yandex_api_request tool calls any documented API method that does not have a dedicated tool yet.
Who it is for. For Yandex 360 users who want Disk, video meetings and the corporate messenger from a single MCP server.
Good fit when
- You want to read and upload files to Yandex Disk from an agent
- You want to quickly create a Telemost meeting link
- You want to send a message or file to a Messenger chat
Not a fit when
- You need Yandex 360 Mail or Calendar: they are not covered here
- You are not ready to hand the server tokens for all three services
Example request
Upload a file to Yandex Disk, create a Telemost meeting for tomorrow, and send the link to a chatLimitations
The project is unofficial, maintained by one author, with no stars. It needs separate OAuth tokens for Disk, Telemost and Messenger with the matching scopes. Mail and Calendar are not part of this server.
How to disable. Remove the server from your MCP client config, for example claude mcp remove yandex360, and revoke the issued tokens.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_DISK_TOKEN required, secret | OAuth token with cloud_api:disk.read, .write and .info scopes |
| YANDEX_TELEMOST_TOKEN required, secret | OAuth token with telemost-api scopes |
| YANDEX_MESSENGER_BOT_TOKEN required, secret | Yandex Messenger bot token |
Security check
- The tools delete files on Disk, delete messages, and change Messenger chat membership
README in short
The English README notes that public MCP servers already exist for Yandex Tracker, Cloud and Search, but not for Disk, Telemost and Messenger, and lists all 28 tools across the three services, venv installation, and Claude Code registration with three tokens and a table of required scopes.
FAQ
What if a specific Disk tool does not exist yet?
There is an escape-hatch tool, yandex_api_request, that calls any documented Yandex 360 API method directly, for example reactions or polls.
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