SSyncDev

Yandex Tools MCP Server

Five npm MCP servers for Yandex Wordstat, Search, Webmaster, Metrika and Direct, for SEO and ads work in the Russian market.

Local server

What is the Yandex Tools MCP Server?

Google-centric SEO tooling says little about search in Russia, where Yandex sets the terms. This collection fills that gap with five separate npm packages, each a small MCP server for one Yandex API. Together they make up the Yandex Tools MCP server set, and you can install all of them or only the one you need.

The five packages

Package Covers Credentials
yandex-wordstat-mcp Keyword research and search trends via the Wordstat v2 API on Yandex Cloud Search API key and folder ID
yandex-search-mcp Web search through the Yandex Search API Search API key and folder ID
yandex-webmaster-mcp Site indexing, analytics and SEO data from Webmaster OAuth token
yandex-metrika-mcp Traffic and web analytics from Metrika OAuth token
yandex-direct-mcp Campaigns, ads, keywords, bids and stats in Direct OAuth token

Wordstat and Search share one Yandex Cloud key and folder ID, which keeps setup shorter than it looks.

Wiring it into a client

Each package runs with npx -y <package>, so Node is the only local prerequisite. Add an entry per package to your client's mcpServers block and supply the matching environment variables. For Claude Code there is also a plugin route: export all five credentials in your shell, then start Claude Code with --plugin-dir pointing at a local clone. The plugin bundles two skills, yandex-keyword-research and yandex-competitive-analysis, which trigger on keyword and competitor questions.

Practical uses

  • Pull search volumes and trends before writing Russian-language content.
  • Check how a site is indexed and what queries bring traffic.
  • Compare Metrika traffic with Webmaster query data in one conversation.
  • Review or adjust Direct campaigns and bids.

Read before connecting Direct

Direct is the one package that spends money. It defaults to the sandbox, and only switches to the real account when YANDEX_DIRECT_LIVE=1 is set. Leave that unset until you are sure the agent's changes are what you want. Every package needs a Yandex account with access to the relevant service, and Wordstat and Search additionally need a Yandex Cloud setup. Per-tool names live in each package's own docs and are not listed here. Running from a local clone needs bun install first, or each server fails to start. Browse our other integrations, or the full category for related connectors.

How to install the Yandex Tools MCP Server

{
  "mcpServers": {
    "yandex-wordstat": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wordstat-mcp"
      ],
      "env": {
        "YANDEX_SEARCH_API_KEY": "your_api_key",
        "YANDEX_FOLDER_ID": "your_folder_id"
      }
    },
    "yandex-search": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-search-mcp"
      ],
      "env": {
        "YANDEX_SEARCH_API_KEY": "your_api_key",
        "YANDEX_FOLDER_ID": "your_folder_id"
      }
    },
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "your_oauth_token"
      }
    },
    "yandex-metrika": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-metrika-mcp"
      ],
      "env": {
        "YANDEX_METRIKA_TOKEN": "your_oauth_token"
      }
    },
    "yandex-direct": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-direct-mcp"
      ],
      "env": {
        "YANDEX_DIRECT_TOKEN": "your_oauth_token"
      }
    }
  }
}

Keep only the packages you need. Yandex Direct uses the sandbox unless YANDEX_DIRECT_LIVE=1 is set.

Configuration

VariableDescriptionRequired
YANDEX_SEARCH_API_KEYYandex Cloud Search API key, needed by the Search and Wordstat packages.Optional
YANDEX_FOLDER_IDYandex Cloud folder ID, needed by the Search and Wordstat packages.Optional
YANDEX_WEBMASTER_TOKENOAuth token for the Webmaster package.Optional
YANDEX_METRIKA_TOKENOAuth token for the Metrika package.Optional
YANDEX_DIRECT_TOKENOAuth token for the Direct package.Optional
YANDEX_DIRECT_LIVESet to 1 to make the Direct package use the real account instead of the sandbox.Optional

Frequently asked questions

No. Each Yandex API is a separate npm package run with npx, so you can add only the ones you need to your client config.