Yandex Cloud MCP: VMs and Object Storage
yandex-cloud-mcp
MCP server for basic Yandex Cloud operations: virtual machines, Object Storage buckets and serverless functions from an agent chat
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Can start and stop real virtual machines
- Invokes serverless functions with an arbitrary payload
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/yandex-cloud-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal
claude mcp add --transport stdio --env 'YANDEX_CLOUD_TOKEN=<your YANDEX_CLOUD_TOKEN>' --env 'YANDEX_CLOUD_FOLDER_ID=<YANDEX_CLOUD_FOLDER_ID value>' yandex-cloud -- npx -y @theyahia/yandex-cloud-mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"yandex-cloud","type":"stdio","command":"npx","args":["-y","@theyahia/yandex-cloud-mcp"],"env":{"YANDEX_CLOUD_TOKEN":"<your YANDEX_CLOUD_TOKEN>","YANDEX_CLOUD_FOLDER_ID":"<YANDEX_CLOUD_FOLDER_ID value>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"yandex-cloud": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add yandex-cloud --env 'YANDEX_CLOUD_TOKEN=<your YANDEX_CLOUD_TOKEN>' --env 'YANDEX_CLOUD_FOLDER_ID=<YANDEX_CLOUD_FOLDER_ID value>' -- npx -y @theyahia/yandex-cloud-mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.yandex-cloud]
command = "npx"
args = ["-y", "@theyahia/yandex-cloud-mcp"]
env = { YANDEX_CLOUD_TOKEN = "<your YANDEX_CLOUD_TOKEN>", YANDEX_CLOUD_FOLDER_ID = "<YANDEX_CLOUD_FOLDER_ID value>" }If the file already exists, append the block to the end.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"yandex-cloud": {
"type": "local",
"command": [
"npx",
"-y",
"@theyahia/yandex-cloud-mcp"
],
"environment": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"yandex-cloud": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-cloud-mcp"
],
"env": {
"YANDEX_CLOUD_TOKEN": "<your YANDEX_CLOUD_TOKEN>",
"YANDEX_CLOUD_FOLDER_ID": "<YANDEX_CLOUD_FOLDER_ID value>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_CLOUD_TOKENsecret, requiredYANDEX_CLOUD_FOLDER_IDrequired
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add the MCP server: claude mcp add yandex-cloud -e YANDEX_CLOUD_TOKEN=... -e YANDEX_CLOUD_FOLDER_ID=... -- npx -y @theyahia/yandex-cloud-mcp. Get the IAM token and folder id from console.cloud.yandex.ru.
Other ways from the author
claude mcp add yandex-cloud -e YANDEX_CLOUD_TOKEN=your-iam-token -e YANDEX_CLOUD_FOLDER_ID=your-folder-id -- npx -y @theyahia/yandex-cloud-mcpIAM token and folder id from the Yandex Cloud console.
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent eight tools over the Yandex Cloud API: list and fetch a VM, start and stop it, list Object Storage buckets, list serverless functions, invoke a function with an arbitrary payload, and check an async operation's status. Every request carries an IAM token and folder id from environment variables. The server is part of the author's WWmcp series of 46 small MCP servers, each installed as its own npm package.
Who it is for. For people who run a handful of VMs and functions in Yandex Cloud and want to control them with short agent commands instead of the console.
Good fit when
- You want to quickly start or stop a test VM
- You want to list buckets or functions in a folder without the console
- You want to invoke a serverless function with a test payload and check an operation's status
Not a fit when
- You need networking, disk, database cluster or billing management: none of that is here
- You need an official tool from Yandex Cloud itself
Example request
Show all VMs in my folder and start the one named test-vmLimitations
Only four areas are covered: Compute VM, Object Storage, Serverless Functions and operation status. No networking, disks, managed databases or billing. Needs an IAM token that must be refreshed manually; there is no auto-refresh. Community project, not a Yandex Cloud product.
How to disable. Run claude mcp remove yandex-cloud in Claude Code or delete the yandex-cloud block from your MCP client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_CLOUD_TOKEN required, secret | Yandex Cloud IAM token |
| YANDEX_CLOUD_FOLDER_ID required | Yandex Cloud folder id |
Security check
- Can start and stop real virtual machines
- Invokes serverless functions with an arbitrary payload
README in short
The README gives ready npx configs for Claude Desktop, Claude Code, VS Code and Cursor, a table of eight tools and Russian-language demo prompts. The server is named as part of WWmcp, the author's series of 46 MCP servers, under the MIT license.
FAQ
How long does the IAM token last?
Yandex Cloud IAM tokens are short-lived, and the README does not describe auto-refresh, so you reissue it via the console or the yc CLI yourself.
Can it manage disks or networks?
No, the server only covers VMs, Object Storage and serverless functions.
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