yagames-mcp
Related Servers
Alternatives to yagames-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP server for managing Yandex Cloud infrastructure including Compute VMs, Object Storage, Serverless Functions, and Operations.813 npm1MIT
- AlicenseAqualityCmaintenanceMCP server for interacting with Yandex.Webmaster API to manage sites, retrieve search queries, and check indexing status. Requires an OAuth token.1357 npm5MIT
- AlicenseAqualityCmaintenanceMCP server for Yandex Disk that enables file and folder management, search, upload/download, publishing, and trash operations through natural language.22MIT
- AlicenseAqualityFmaintenanceMCP server for Yandex GPT API enabling text generation, embeddings, classification, summarization, and tokenization.836 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI assistants to interact with Yandex 360 organization services, currently supporting Yandex Wiki for reading, editing, and searching pages.24 PyPIMIT
- AlicenseAqualityAmaintenanceMCP server for the Yandex Webmaster API, enabling natural-language queries about site indexing, search queries, IKS, diagnostics, sitemaps, and external links, as well as actions like recrawling, from AI assistants such as Claude, Cursor, and Codex.2099 npmMIT
TDQS
Scored across 10 tools
Most tools target distinct actions in the catalog or developer lifecycle. Search and popular both return catalog games but differ by keyword versus ranking, and status versus list-my-games have different scopes. These are minor overlaps, not true duplicates.
All names share the consistent yagames- prefix and snake_case, but the action pattern is inconsistent: five use verb_noun like upload-build and create-draft, while others are bare verbs like search and publish, or nouns/adjectives like status, categories, and popular. This mixed convention is readable but not a uniform verb_noun scheme.
Ten tools is well-scoped for the server's dual purpose of browsing the Yandex Games catalog and managing a developer's game lifecycle. No obvious bloat or overly narrow set.
The developer lifecycle is well covered: draft creation/update, build upload, moderation submission, publishing, and status checks are all present, plus catalog browsing via search, popular, and categories. Minor gaps exist such as no delete/unpublish or detailed single-game get, but agents can complete the primary workflow.