Yandex Search MCP Server
Yandex's official MCP server for web search via Yandex Search API: results with sources and a generative answer
- 47 ★ on the repository
- Last commit
Extended access
Why this level
- Queries go to a paid cloud API
- Requires a service account API key
Install
- Works in
- Services
Manual install
{
"mcpServers": {
"yandexSearch": {
"type": "sse",
"url": "https://d5de9siimt9bkld7viic.emzafcgx.apigw.yandexcloud.net:3000/sse",
"headers": {
"ApiKey": "<your_api_key>",
"FolderId": "<your_folder_id>"
}
}
}
}The same block works for VS Code in .vscode/mcp.json.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Queries go to a paid cloud API
- Requires a service account API key
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent two tools: real-time web search with sources and search with a generative answer built by a Yandex model from the results. You can connect to Yandex's remote server over SSE with the API key and folder ID in headers, or run it locally with Docker, Podman or Python. It needs a Yandex Search API account and a service account with the right role.
Who it is for. For developers and researchers who need fresh search over the Russian-language web inside an agent.
Good fit when
- You need current web data, especially from Russian sources
- You want a short answer with links instead of a page list
- Western search APIs are not an option
Not a fit when
- You have no Yandex Cloud billing account
- You need search over private company documents
Example request
Use yandexSearch to find the latest changes to product labeling rules in Russia and link the sourcesMCP
- Transport
- sse
- Authentication
- API key
Environment variables
SEARCH_API_KEYrequired, secret- Yandex Search API key for local runs
FOLDER_IDrequired- Yandex Cloud folder ID
Limitations
Search API is paid and needs an API key with the yc.search-api.execute scope and the search-api.webSearch.user role on the service account. The remote server uses SSE, so clients without SSE need mcp-remote. Tool names differ between README sections. Last updated in March 2026; Yandex develops newer servers in the yandex-cloud/mcp repository.
How to disable. Remove the yandexSearch block from your MCP client config and revoke the API key in the Yandex Cloud console.
FAQ
How does it differ from search in yandex-cloud/mcp?
This is an earlier standalone server. In the Yandex Cloud set, search installs via an npm package with OAuth auth.
Can I run it without the remote server?
Yes, the README covers building a Docker image and running server.py with SEARCH_API_KEY and FOLDER_ID.
Discussion
No questions or reviews yet.
Related
All Yandex Cloud toolsYandex search MCP server in TypeScript
yandex-search-mcp
A TypeScript MCP server for the Yandex Search API with its own result parser and tests
Yandex search MCP on .NET with AOT compilation
Yandex Search MCP Server (.NET)
A .NET 10 Yandex search MCP server with native AOT compilation, page-to-Markdown conversion and regex search
An MCP server for the Yandex Cloud Search API v2: Wordstat and web search with file caching, date normalization and 429-retry handling
Yandex image search MCP
mcp-yandex-search-api
A Python MCP server for searching Yandex Images through the Yandex Search API
Yandex Cloud's official MCP server set: documentation, search, app deployment, serverless functions, containers and a data catalog
A ZAI.ONE MCP server bringing Direct, Metrika, search, Wordstat and Webmaster into one agent, with a setup wizard and opt-in write operations
README in short
The English README describes two search tools and how to get an API key and folder ID. The recommended route is the remote server, with step-by-step setup for Claude Desktop via mcp-remote and for Cursor and VS Code with sse type. For local runs it covers building a Docker or Podman container and running with Python, plus sample requests and troubleshooting tips.