Yandex Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YC_TOKEN | Yes | IAM token for Yandex Cloud authentication | |
| YC_FOLDER_ID | Yes | Folder ID for Yandex Cloud resources |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_credentialsC | Setup Yandex Cloud credentials for the session |
| get_credentials_statusA | Check current credentials status Returns: Status of configured credentials |
| clear_credentialsA | Clear stored credentials from session Returns: Confirmation message |
| list_virtual_machinesC | List all virtual machines |
| get_virtual_machine_configC | Get detailed VM configuration |
| list_vpc_networksC | List all VPC networks |
| list_vpc_subnetsC | List all VPC subnets |
| list_vpc_security_groupsC | List all security groups |
| get_security_group_detailsB | Get detailed security group configuration |
| list_storage_disksC | List all storage disks |
| get_disk_detailsC | Get detailed disk configuration |
| list_disk_snapshotsC | List all disk snapshots |
| get_snapshot_detailsC | Get detailed snapshot configuration |
| list_yandex_cloudsC | List all clouds in organization or all accessible clouds |
| get_cloud_details_infoC | Get detailed information about a specific cloud |
| list_yandex_foldersA | List all folders in specified cloud or all accessible folders |
| get_folder_details_infoC | Get detailed information about a specific folder |
| list_compute_imagesC | List all images in specified folder |
| get_image_configurationC | Get detailed configuration of a specific image |
| list_availability_zonesA | List all availability zones |
| get_zone_configurationC | Get detailed information about a specific zone |
| list_compute_disk_typesA | List all disk types in specified zone or all zones |
| get_disk_type_configurationC | Get detailed information about a specific disk type |
| get_network_configurationC | Get detailed configuration of a specific network |
| get_subnet_configurationB | Get detailed configuration of a specific subnet |
| list_vpc_route_tablesB | List all route tables in specified folder |
| get_route_table_configurationB | Get detailed configuration of a specific route table |
| list_vpc_addressesB | List all static IP addresses in specified folder |
| get_address_configurationB | Get detailed configuration of a specific static IP address |
| list_vpc_gatewaysC | List all gateways in specified folder |
| get_gateway_configurationC | Get detailed configuration of a specific gateway |
| get_yandex_organization_contextA | Get organization context with available clouds and folders hierarchy |
| suggest_query_scopeB | Suggest appropriate scope (folder/cloud/organization) for resource queries |
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 33 tools
Every tool targets a distinct resource type with a clear list/get distinction, so there is no overlap. Credential tools are also clearly separated by action.
All tools use consistent snake_case with verb_noun patterns (list_*, get_*, setup_*, clear_*), making the action and resource immediately obvious.
With 33 tools, the server exceeds the recommended range and feels bloated. Many list/get pairs could be consolidated or served via parameters.
The tool surface is entirely read-only, covering only list and get operations. There are no create, update, or delete operations, leaving significant gaps for actual cloud management.