Read-only Yandex Cloud MCP server
Yandex Cloud MCP Server
An unofficial read-only Yandex Cloud MCP server: VMs, networks, disks, and access at folder, cloud and org level
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- The server is read-only by design and does not change Yandex Cloud resources
Install
Manual install
uv sync && export YC_TOKEN="your_iam_token_here" && export YC_FOLDER_ID="your_folder_id_here" && uv run mcp_server.pyThe development run from the README.
This is third-party code. Review the repository files before installing.
What it does
The Python server gives read-only access to Yandex Cloud resources: full read coverage for Compute, VPC and Disks or Snapshots. It works at folder, cloud and organization level, with automatic scope detection and navigation hints. Authentication uses an IAM token and folder ID from environment variables, or interactively right in a Claude conversation. It can run via uv for development or as a Podman container for production.
Who it is for. For engineers who want to safely browse Yandex Cloud resources through an agent without the risk of changing anything.
Good fit when
- You want a quick look at VMs, networks or disks in Yandex Cloud
- You want an overview of resources at the whole-organization level, not just one folder
Not a fit when
- You need to create or change resources: the server is read-only
- You need the official Yandex Cloud server
Example request
Show all VMs and networks in my Yandex CloudLimitations
The project explicitly calls itself unofficial, maintained by one author, with no pushes for over a year. It needs a Yandex Cloud IAM token, which should be issued with minimal read-only rights.
How to disable. Stop the container or the uv run mcp_server.py process and remove the server from your MCP client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YC_TOKEN required, secret | Yandex Cloud IAM token |
| YC_FOLDER_ID required | The default Yandex Cloud folder ID |
Security check
- The server is read-only by design and does not change Yandex Cloud resources
README in short
The Russian README describes the server as an unofficial read-only Yandex Cloud MCP with multi-level access, smart scope navigation, and flexible authentication. It gives two run options: uv for development and Podman for production, a Claude AI Desktop config snippet, and example setup and usage phrases.
FAQ
Can the server change anything in the cloud?
No, the README explicitly states it covers only read operations of the Compute, VPC and Disks or Snapshots APIs.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
Agent Skills for Google products
Agent Skills for Google products and technologies
Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring