SkillFoxx

Type a name, a task or a service

Yandex Search.API MCP with Wordstat

Yandex Search.API MCP Server

An MCP server for Yandex's official Search.API: web, image, generative search and four Wordstat tools in one npm package

MCP server

Low risk

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

Why this level

  • All seven tools only read public search results and keyword demand via the official API
All reasons and checks
Russian stack

shufl9dka/yandex-searchapi-mcpAuthor:shufl9dka

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/yandex-search-api-mcp-server

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 --env 'FOLDER_ID=<FOLDER_ID value>' --env 'API_KEY=<your API_KEY>' yandex-searchapi -- npx -y yandex-searchapi-mcp

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

{
  "mcpServers": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

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": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

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":"yandex-searchapi","type":"stdio","command":"npx","args":["-y","yandex-searchapi-mcp"],"env":{"FOLDER_ID":"<FOLDER_ID value>","API_KEY":"<your API_KEY>"}}'

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

{
  "servers": {
    "yandex-searchapi": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add yandex-searchapi --env 'FOLDER_ID=<FOLDER_ID value>' --env 'API_KEY=<your API_KEY>' -- npx -y yandex-searchapi-mcp

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

[mcp_servers.yandex-searchapi]
command = "npx"
args = ["-y", "yandex-searchapi-mcp"]
env = { FOLDER_ID = "<FOLDER_ID value>", API_KEY = "<your API_KEY>" }

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

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

{
  "mcpServers": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

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

{
  "mcpServers": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

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

{
  "mcpServers": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "yandex-searchapi": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "yandex-searchapi-mcp"
      ],
      "environment": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

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

{
  "context_servers": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

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

{
  "mcpServers": {
    "yandex-searchapi": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-searchapi-mcp"
      ],
      "env": {
        "FOLDER_ID": "<FOLDER_ID value>",
        "API_KEY": "<your API_KEY>"
      }
    }
  }
}

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

Keys and settings

FOLDER_IDrequired
API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 9df0e62.

Text for your agent

Install with npm install yandex-searchapi-mcp, then add the server to your MCP client config with the FOLDER_ID and API_KEY of a Yandex Cloud service account.

Other ways from the author
npm install yandex-searchapi-mcp

Install the package from the npm registry.

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

What it does

The server provides seven tools over Search.API's REST endpoints: web_search, image_search and generative_search hit /v2/web/search, /v2/image/search and /v2/gen/search, while wordstat_get_top, wordstat_get_dynamics, wordstat_get_regions_distribution and wordstat_get_regions_tree cover the Wordstat REST surface. Web and image search decode rawData from Base64 and parse the XML into structured document groups; web search always runs in XML format. Tool inputs default to minimal to keep the model's context compact, while searchType is available everywhere and defaults to SEARCH_TYPE_COM.

Who it is for. For developers and marketers who want both search and Wordstat keyword demand in one MCP server on the official API.

Good fit when

  • You need both search and Wordstat keyword demand in one server
  • Web and image search should return structured document groups, not raw XML
  • A one-command npm install from a registered package works for you

Not a fit when

  • You need Yandex Webmaster or Direct access: the server only covers Search.API and Wordstat
  • You are not ready to set up a Yandex Cloud service account with a key and Folder ID

Example request

Find the top related queries for winter tires and show demand dynamics over the last month

Limitations

The FOLDER_ID and API_KEY variables of a Yandex Cloud service account are required. Web search is forced to XML format, with no other response format available. Wordstat access needs separate permission for that method in Yandex Cloud.

How to disable. Remove the yandex-searchapi entry from mcpServers in your client configuration.

MCP

Transport
stdio
Authentication
API key
Environment variables
API_KEY
required, secret		Yandex Cloud service-account key for Search.API
FOLDER_ID
required		Yandex Cloud folder ID

Security check

  • All seven tools only read public search results and keyword demand via the official API

README in short

The README lists all seven tools with their input and output fields, explains that the server only uses Search.API and Wordstat REST endpoints, shows npm install and an MCP client config example with FOLDER_ID and API_KEY variables.

FAQ

What format does web search return?

The server always requests XML (responseFormat FORMAT_XML) and parses it itself into structured document groups.

Does Wordstat need separate access?

Yes, Wordstat methods in Yandex Cloud usually require separate permission on the service account.

Official

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

SkillMedium riskRussian stackNo VPN needed12
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 needed2
Official

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

MCP serverMedium risk21.5K

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

PluginHigh risk17.9K
Foxx AIYandex Search.API MCP with Wordstat

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