Yandex Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YANDEX_CLOUD_TOKEN | Yes | IAM-токен для аутентификации в Yandex Cloud | |
| YANDEX_CLOUD_FOLDER_ID | Yes | Идентификатор каталога (folder) в Yandex Cloud |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_instancesB | Список виртуальных машин (Compute) в каталоге Yandex Cloud. |
| get_instanceB | Получить информацию о виртуальной машине по ID. |
| start_instanceC | Запустить виртуальную машину. |
| stop_instanceC | Остановить виртуальную машину. |
| list_bucketsB | Список бакетов Object Storage в каталоге. |
| list_functionsB | Список serverless-функций в каталоге. |
| invoke_functionB | Вызвать serverless-функцию с payload. |
| get_operationB | Проверить статус асинхронной операции по ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool maps cleanly to a distinct resource and action: instance lifecycle (list/get/start/stop), bucket listing, function listing/invocation, and generic operation status. There is no meaningful overlap between any pair of tools.
All tools follow the same verb_noun snake_case pattern: list_instances, get_instance, start_instance, list_buckets, invoke_function, get_operation. The naming is predictable and easy to infer.
Eight tools is a reasonable, focused set for a Yandex Cloud server covering compute, storage, serverless, and async operations. Each tool serves a clear purpose without bloat.
The surface is notably incomplete: compute instances only support list/get/start/stop with no create or delete, Object Storage only lists buckets with no object or bucket management, and serverless functions only support list/invoke without create/update/delete. Agents would frequently hit dead ends when trying to perform common cloud operations.