@scom82/yandex-search-mcp

An MCP server for the Yandex Cloud Search API v2: Wordstat and web search with file caching, date normalization and 429-retry handling

MCP server

Low risk

We rate an entry low when it mostly gives the agent instructions and reference material.

Why this level

  • Only reads query statistics and web search results, changes nothing
  • Synchronous web search is notably more expensive than async, so pick the mode by task volume
All reasons and checks
Russian stack

scom-82/yandex-search-mcp

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/scom82-yandex-search-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio scom82-yandex-search-mcp -- npx -y @scom82/yandex-search-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"scom82-yandex-search-mcp","type":"stdio","command":"npx","args":["-y","@scom82/yandex-search-mcp"]}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "scom82-yandex-search-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the servers key.

Run in a terminal

codex mcp add scom82-yandex-search-mcp -- npx -y @scom82/yandex-search-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.scom82-yandex-search-mcp]
command = "npx"
args = ["-y", "@scom82/yandex-search-mcp"]

If the file already exists, append the block to the end.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "scom82-yandex-search-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcp key.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "scom82-yandex-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/yandex-search-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit eeb47d1.

Text for your agent

Install the server with npx -y @scom82/yandex-search-mcp, add it to .mcp.json with YC_SEARCH_API_KEY and YC_FOLDER_ID, and call wordstat_regions_tree, which is free, to verify the connection.

Other ways from the author
npx -y @scom82/yandex-search-mcp

The README method; the package is published on npm.

This is third-party code. Review the repository files before installing.

What it does

The server covers five tools: four Wordstat methods (top related phrases with associations, dynamics over dates, regional distribution with an affinity index, and the free region tree) plus websearch_query, Yandex web search with a synchronous mode and an async mode roughly 16x cheaper. The server smooths over several API rough edges itself: int64 counts arriving as strings get parsed into numbers, plain ISO dates are automatically snapped to Wordstat's period boundaries, short enum values like monthly or desktop get the required prefix added, and web search results are decoded from base64 into clean JSON instead of XML with highlight tags. Responses are file-cached for 30 days for Wordstat and 1 day for web search.

Who it is for. For developers who want a reliable layer over the Yandex Cloud Search API with caching and protection from typical format errors.

Good fit when

  • You need both Wordstat and Yandex web search in one server
  • You don't want to pay twice for the same repeated request: there's a file cache
  • You need cheap batch web search: there's an async mode

Not a fit when

  • You're fine with the old yandex-mcp fork's api.wordstat.yandex.net methods: Yandex retired that host, which is exactly why this server exists
  • You don't need web search, only bare Wordstat without caching or normalization

Example request

Find the top related queries for "flower delivery" and show who ranks in Yandex search for that query

Limitations

You need YC_SEARCH_API_KEY and YC_FOLDER_ID for a service account with the search-api.webSearch.user role. Synchronous web search costs around 488 rubles per 1000 requests, async around 30.5 rubles. Generative Search is planned as a future phase (Phase 2) and is not implemented in this version. MIT license.

How to disable. Remove the yandex-search entry from .mcp.json, or run claude mcp remove yandex-search.

MCP

Transport
stdio
Authentication
API key
Environment variables
Environment variables
YC_SEARCH_API_KEY
required, secret
Yandex Cloud service account API key.
YC_FOLDER_ID
required
Folder ID, injected into every request body.

Security check

  • Only reads query statistics and web search results, changes nothing
  • Synchronous web search is notably more expensive than async, so pick the mode by task volume

README in short

The README explains the backstory, replacing the retired Wordstat host, gives a table of five tools, details the automatic format fixes (int64, dates, enum prefixes, base64 decoding), an environment variable table, and instructions for getting a service key in the Yandex Cloud console.

FAQ

Why did the old yandex-mcp's wordstat_* tools break?

Yandex retired the standalone api.wordstat.yandex.net host, so this server moved to the Yandex Cloud Search API v2 while keeping the same tool names.

Does async web search return the result immediately?

No, you poll /operations/{id}, but it costs roughly 16x less than the synchronous mode.

Official

Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution

SkillMedium riskRussian stackNo VPN needed12Repository stars
Editors’ pick

A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata

MCP serverMedium riskRussian stackNo VPN needed2Repository stars
Official

An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO

MCP serverMedium risk21.5KRepository stars

A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents

PluginHigh risk17.9KRepository stars
Foxx AI@scom82/yandex-search-mcp

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.