Yandex Cloud MCP Servers
Yandex Cloud's official MCP server set: documentation, search, app deployment, serverless functions, containers and a data catalog
Install
{
"mcpServers": {
"yandex-cloud-toolkit": {
"type": "stdio",
"command": "npx",
"args": [
"-y", "@yandex-cloud/mcp",
"-s", "toolkit"
]
}
}
}Replace toolkit with the server you need: docs, search, functions and others. Auth defaults to browser OAuth.
This is third-party code. Review the repository files before installing.
What it does
The repository documents Yandex Cloud servers that run from one npm package with a server selector or connect over Streamable HTTP to cloud endpoints. Toolkit deploys simple apps on Compute, VPC, IAM, Object Storage and Managed YDB. The documentation and search servers provide generative search over Yandex Cloud docs and Yandex web search. The serverless group manages functions, containers, triggers, workflows, API gateways and MCP gateways, and Data Catalog finds tables, views and dependency graphs.
Who it is for. For developers and DevOps engineers whose infrastructure runs on Yandex Cloud.
Good fit when
- You want the agent to deploy a service with a VM, bucket or YDB database
- You need precise answers from Yandex Cloud docs inside the IDE
- You need to manage serverless functions and containers from chat
Not a fit when
- Your infrastructure is in another cloud
- The agent must not get roles that can change resources in a production cloud
Example request
Deploy my service to Yandex Cloud with a public IP and create a bucket for static pagesLimitations
Most servers require Yandex Cloud auth and server-specific roles, such as editor or compute.admin for Toolkit. An IAM token for HTTP connections lasts at most 12 hours. The functions, triggers, workflows and gateway servers are marked preview. Resources created by the agent are billed as usual. The documentation server needs no auth.
How to disable. Remove the Yandex Cloud server blocks from your MCP client config and revoke granted roles or tokens.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Creates and changes billable cloud resources
- Operates with permissions to modify infrastructure
README in short
The English README explains the idea of managing cloud infrastructure through MCP and groups servers by purpose: deployment, search and knowledge, serverless and data platform. It describes two connection methods: the npm client over stdio with OAuth or Yandex Cloud CLI, and Streamable HTTP with an IAM token. Each server in the servers folder has its own README with sample prompts, config and tool list. Apache-2.0 license.
FAQ
How do I pick a server?
Pass the server name with -s: toolkit, docs, search, functions and others. The exact name is in each server's README.
What auth options are there?
Browser OAuth by default, a Yandex Cloud CLI profile via -p, or an IAM token in a header for HTTP connections.
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
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring
A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes