Yandex MCP Servers
Four single-file MCP servers for YandexGPT, text recognition, SpeechKit speech synthesis and Yandex search
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Tools generate text and speech and recognize images; they change no external accounts or payments
- Yandex Cloud API usage is billed by the provider
Install
Manual install
git clone https://github.com/minakovai/yandex-mcp-servers.git && cd yandex-mcp-servers && npm installThe README install; then launch the server you need via npm run start:gpt or node <file>.js.
This is third-party code. Review the repository files before installing.
What it does
A general-purpose version of the same collection as the author's openclaw-tools-collection, but not tied to a specific assistant. Four independent Node.js servers: yandexgpt-server provides YandexGPT text completion and chat, yandex-vision-server recognizes text and text blocks in images, yandex-speechkit-server synthesizes speech (voices alena, filipp, jane, omazh, zahar, ermil, marina) and recognizes short and long audio, and yandex-search-server searches the web, images and news via the aging Yandex Search XML API with a separate key.
Who it is for. For developers who want a simple starting example for connecting several Yandex Cloud services to an MCP client.
Good fit when
- You want a minimal single-file server for YandexGPT, OCR or SpeechKit with no extra tooling
- You already have Yandex Cloud keys and want a quick npm-based start
Not a fit when
- You need Yandex search via the current Yandex Cloud Search API: this uses the aging XML protocol
- You need tests, CI or a single wrapper around all four servers
Example request
Read this text aloud in the alena voice via yandex_ttsLimitations
The package is not published to npm; install by cloning. yandex-search-server uses a separate, aging Yandex Search XML API with a YANDEX_SEARCH_API_KEY that's harder to obtain than the modern Yandex Cloud Search API. Each server runs as its own process; there is no unified entry point. No tests or CI.
How to disable. Remove the relevant entry from your mcporter or MCP client config and stop the node process.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_FOLDER_ID required | Yandex Cloud folder ID. |
| YANDEXGPT_API_KEY required, secret | API key for the YandexGPT, Vision and SpeechKit servers. |
| YANDEX_SEARCH_API_KEY secret | A separate Yandex Search XML API key, only for the search server. |
Security check
- Tools generate text and speech and recognize images; they change no external accounts or payments
- Yandex Cloud API usage is billed by the provider
README in short
The Russian README describes each of the four servers in its own section with tools, a launch command and an mcporter call example, gives a general mcporter config add setup table for each server, and a section on obtaining Yandex Cloud and Yandex Search XML keys.
FAQ
Do all four servers use one key?
No, YandexGPT, Vision and SpeechKit use YANDEX_FOLDER_ID and YANDEXGPT_API_KEY, while search uses a separate YANDEX_SEARCH_API_KEY from yandex.com/dev/xml.
Which voices are available for TTS?
alena, filipp, jane, omazh, zahar, ermil, marina.
Related
Open-source personal AI assistant on your own machine: answers in Telegram, Slack, Discord and WhatsApp, extended with skills and plugins
A self-improving agent from Nous Research with a TUI, messaging gateway, cron jobs and skills it writes itself
An open source coding agent for the terminal and desktop with build and plan modes
Open prompt library with a Claude Code plugin, MCP server and CLI: search, fetch and improve prompts and skills from an agent