SkillFoxx

Type a name, a task or a service

Yandex Search MCP Server

Yandex's official MCP server for web search via Yandex Search API: results with sources and a generative answer

MCP serverMedium riskRussian stack

yandex/yandex-search-mcp-serverAuthor: Yandex

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.

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 sources

Limitations

Search API is paid and needs an API key with the yc.search-api.execute scope and the search-api.editor 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.

MCP

Transport
sse
Authentication
API key
Environment variables
SEARCH_API_KEY
required, secret		Yandex Search API key for local runs
FOLDER_ID
required		Yandex Cloud folder ID

Security check

  • Queries go to a paid cloud API
  • Requires a service account API key

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.

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.

Editors’ pick

CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP

CLIHigh risk114.6K
Editors’ pick

A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief

SkillHigh risk62K
Editors’ pick

The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces

MCP serverMedium risk51.9K
Editors’ pick

A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills

CLIHigh risk42.6K