yandex-tools-mcp
Five MCP servers for Wordstat, Search, Webmaster, Metrica and Direct, plus a Claude Code plugin with keyword and competitor skills
Install
claude --plugin-dir /path/to/yandex-tools-mcpRuns all five servers as a plugin with skills. Set keys as environment variables before launching.
This is third-party code. Review the repository files before installing.
What it does
A set of five separate npm packages gives the agent Yandex APIs. Wordstat shows popular queries, trends and regional distribution, Search returns results, Webmaster provides site indexing and query data, and Metrica gives traffic statistics. The Direct server reads campaigns, ad groups, ads, keywords, bids and reports, and also creates and changes campaigns, ads, keywords and bids. All packages can be installed as one Claude Code plugin that includes skills for keyword research and competitor SERP analysis.
Who it is for. For SEO and PPC specialists working with Yandex.
Good fit when
- You need Wordstat queries and volumes right in an agent chat
- You want to see which sites rank in Yandex for given queries
- You need a Direct campaign report or Metrica traffic data
Not a fit when
- You are not ready to give the agent a Direct OAuth token for a live account
- You need Audiences or other Yandex services not in the set
Example request
Use Wordstat to pull top queries for apartment renovation in Saint Petersburg and show whether demand grew over the past yearLimitations
Wordstat and Search need an API key and folder ID in Yandex Cloud, where these APIs are paid. Webmaster, Metrica and Direct use OAuth tokens, and Direct needs your own app with API access. The Direct server defaults to the sandbox and changes real campaigns only with YANDEX_DIRECT_LIVE=1.
How to disable. Remove the yandex-* blocks from the client MCP config or stop launching Claude Code with --plugin-dir, then revoke the OAuth tokens in Yandex ID settings.
MCP
- Transport
- stdio
- Authentication
- OAuth
| Environment variables | |
|---|---|
| YANDEX_SEARCH_API_KEY secret | Yandex Cloud API key for Search and Wordstat |
| YANDEX_FOLDER_ID | Yandex Cloud folder ID |
| YANDEX_WEBMASTER_TOKEN secret | Webmaster OAuth token |
| YANDEX_METRIKA_TOKEN secret | Metrica OAuth token |
| YANDEX_DIRECT_TOKEN secret | OAuth token with Direct API access |
| YANDEX_DIRECT_LIVE | Set to 1 to switch Direct from sandbox to the live account |
| YANDEX_DIRECT_LOGIN | Client login for agency accounts |
Security check
- In Direct live mode it creates campaigns and changes budgets and bids, spending real money
- Holds OAuth tokens and a Yandex Cloud key
README in short
The English and Russian README lists five packages with ready npx config blocks and required variables. It separately covers running all servers as a Claude Code plugin with two built-in skills. The Direct package README warns about real spending, explains getting an OAuth token and lists tools marked read or write. MIT licensed.
FAQ
Can the agent spend money in Direct?
Yes, if live mode is enabled with YANDEX_DIRECT_LIVE=1: tools create campaigns and change budgets and bids. Without it all changes go to the sandbox.
Can I install only Wordstat?
Yes, each server is a separate npm package with its own config block.
Related
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents
A Claude Code skill set for auditing sites for AI search: citability, AI crawler access, llms.txt, schema and reports
The experimental official Google Analytics 4 MCP server: reports, funnels and realtime data on request
Google Search Console MCP
Google Search Console MCP Server for SEOs
An MCP server for Google Search Console: queries and pages with clicks and positions, URL indexing checks, sitemaps and ready SEO skills