Summary
Let your AI work in Yandex Disk: browse folders, list all files or recent uploads, read file details, get download links, create folders, copy, move, publish or unpublish files, save a file from a URL and restore from the Trash. Signed in with your Yandex account.
Guided setup
Connect Yandex Disk to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Yandex Disk in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Yandex Disk
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Yandex Disk, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Yandex Disk + Microsoft Copilot
Let your AI work in Yandex Disk: browse folders, list all files or recent uploads, read file details, get download links, create folders, copy, move, publish or unpublish files, save a file from a URL and restore from the Trash. Signed in with your Yandex account.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
YANDEX_DISK_CLIENT_ID, YANDEX_DISK_CLIENT_SECRET
Step 1 — Get credentials
Setting up takes about 5 minutes. You need the Yandex account whose Disk the AI should work with, and an app registered for it at Yandex OAuth.
- Sign in with that Yandex account, open oauth.yandex.ru/client/new (or oauth.yandex.com) and create an app.
- As the platform, choose Web services. As the Redirect URI, enter
https://cloud.anythingmcp.com/api/mcp-oauth/callback. If you host AnythingMCP yourself, enterhttps://your-anythingmcp-host/api/mcp-oauth/callbackinstead. - Under data access, add the Yandex Disk REST API permissions
cloud_api:disk.read(read the whole Disk),cloud_api:disk.write(write anywhere on the Disk) andcloud_api:disk.info(Disk information). Do not pickcloud_api:disk.app_folderalone: it limits the app to its own folder. - Create the app, copy the ClientID into
YANDEX_DISK_CLIENT_IDand the Client secret intoYANDEX_DISK_CLIENT_SECRET, and install the connector. - On the connector page, click Authorize with Provider, pick the Yandex account and allow access.
- Start with
yandex_disk_get_disk_info: it shows whose Disk the connector is signed in to, how much space is used and how big the Trash is.
Permissions and read-only setup: Yandex grants exactly the permissions you ticked in the app in step 3. For a read-only setup, register the app with cloud_api:disk.read and cloud_api:disk.info only, and switch off yandex_disk_create_folder, yandex_disk_copy, yandex_disk_move, yandex_disk_publish, yandex_disk_unpublish, yandex_disk_upload_from_url and yandex_disk_restore_from_trash.
Sign-in: a Yandex token lasts about a year and comes with a refresh token, which AnythingMCP uses to renew it. Both are stored encrypted. If you revoke the app at id.yandex.ru/security or change its permissions, click Authorize with Provider again.
Paths: files and folders are addressed as disk:/folder/file.txt, the root is disk:/ and Trash entries are trash:/.... You can simply name a folder or file; the AI uses the exact names, including the extension.
Changes wait for your yes: creating folders, copying, moving or renaming, publishing and unpublishing, saving a file from a URL and restoring from the Trash change your Disk. The AI says what will happen and waits for your confirmation, and it overwrites an existing file only if you agree. yandex_disk_publish makes a file or folder readable by anyone with the link; yandex_disk_unpublish stops the link, and publishing again creates a new one.
Switched off at install: yandex_disk_delete. When an administrator turns it on, it moves items to the Trash, where yandex_disk_restore_from_trash brings them back. It deletes for good only when you ask for that explicitly.
No search: the Yandex Disk API has no search by name or content. To find a file, the AI lists the folder with yandex_disk_list_folder, pages through every file with yandex_disk_list_files (optionally only images, documents and so on) and compares names, or checks the most recent uploads with yandex_disk_list_last_uploaded.
File contents: the connector does not read or upload the bytes of a file. yandex_disk_get_download_link returns a temporary link you can open (a folder downloads as a zip), and yandex_disk_upload_from_url saves a file that is already on the internet. yandex_disk_get_public_resource reads any public Yandex Disk link, yours or someone else's.
Background operations: copying, moving, restoring or deleting large folders, and every upload from a URL, run in the background at Yandex. The AI checks progress with yandex_disk_get_operation_status until the operation has finished.
Common errors: 401 UnauthorizedError means the sign-in is missing, revoked or expired; authorize again. 403: the app lacks a permission from step 3 (for example cloud_api:disk.write for a change), 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 or its parent folder is missing. 423: the item is locked by another operation, or uploads are paused; try again later. 507: not enough free space on the Disk. 429: too many requests; wait and try again.
The connector does not read or upload file contents, edit custom properties, empty the Trash, share folders with specific people or change Yandex 360 admin settings.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Yandex Disktools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
yandex_disk_get_disk_info | Get the Disk's totals: total_space, used_space and trash_size in bytes, the owner (login, display_name), whether the account is paid, the… |
yandex_disk_list_folder | List what is inside one folder of the Disk (files and subfolders), one page at a time |
yandex_disk_get_resource | Get the details of one file or folder by its path (disk:/folder/file): name, type, size, mime_type, media_type, md5 and sha256, created and… |
yandex_disk_list_files | List every file on the Disk as one flat list, across all folders (folders themselves are not listed), optionally only certain kinds such as… |
yandex_disk_list_last_uploaded | List the files uploaded most recently, newest first, optionally only certain kinds such as images |
yandex_disk_get_download_link | Get a temporary download URL for a file or folder (a folder downloads as a zip archive) |
yandex_disk_list_public | List the files and folders the user has published (shared by public link) |
yandex_disk_get_public_resource | Read the details of a public Yandex Disk link, the user's own or anyone's: name, type, size, owner and, for a folder, its contents… |
yandex_disk_create_folder | Create a folder |
yandex_disk_copy | Copy a file or folder to a new path |
yandex_disk_move | Move or rename a file or folder |
yandex_disk_publish | Publish a file or folder: anyone with the link can then open and download it |
yandex_disk_unpublish | Stop sharing a published file or folder: its public link stops working (publishing again creates a new link) |
yandex_disk_upload_from_url | Save a file from a public internet URL onto the Disk |
yandex_disk_get_operation_status | Check a background operation started by upload from URL, copy, move, restore or delete: status is in-progress, success or failed |
yandex_disk_list_trash | List what is in the Trash |
yandex_disk_restore_from_trash | Restore an entry from the Trash to where it was deleted from (origin_path), optionally under a new name |
yandex_disk_delete | Delete a file or folder |
Example prompts
- "How much space is left on my Yandex Disk, and how big is the Trash?"
- "Which photos did I upload last week, and in which folders are they?"
- "Create the folder Clients/Acme in my Disk and move the Acme contract PDF from Downloads into it."
- "Make a public link for Presentations/Pitch.pdf and give it to me, then list everything else I have shared publicly."
FAQ
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
Was this guide helpful?