Yandex Cloud MCP Server
Related Servers
Alternatives to Yandex Cloud MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceRead-only MCP server for Yandex Cloud resources including VMs, networks, disks, and more, with support for cloud/organization level access.332-
- AlicenseAqualityFmaintenanceMCP server for Yandex GPT API enabling text generation, embeddings, classification, summarization, and tokenization.839 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for interacting with Yandex Cloud AI Studio, enabling chat, text generation, image generation, speech recognition/synthesis, embeddings, classification, search indexes, and AI agent creation with function calling.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives an AI agent controlled access to a Selectel cloud account: OpenStack cloud servers, S3 object storage, and account billing.1MIT
- AlicenseAqualityDmaintenanceMCP server for Yandex Games that enables searching the catalog, managing game drafts, uploading builds, and publishing games.10MIT
- AlicenseAqualityDmaintenanceMCP server for Yandex Metrika API, enabling reporting, counter management, goals, filters, and other operations via natural language.122MIT
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.