Yandex MCP
Five MCP servers for Yandex Search, Wordstat, Webmaster, Metrika and Direct, bundled as a Claude Code plugin with two skills
Install
/plugin marketplace add stufently/yandex-mcp
/plugin install yandex-mcp@stufentlyRequires Node.js 22 and Bun. Tokens are set separately via env.
This is third-party code. Review the repository files before installing.
What it does
The monorepo gives an agent access to Yandex APIs: Search results, Wordstat query volumes and trends, site data from Webmaster, Metrika reports and Direct campaigns. Servers can be enabled one at a time, each reading only its own environment variables. Direct tools read and change campaigns, keywords and bids, and irreversible operations require an explicit confirm: true. The plugin also ships skills for keyword research and competitor analysis in search results.
Who it is for. For SEO specialists and marketers working with Yandex who want reports and data through an agent.
Good fit when
- You need keyword research from Wordstat with trends and regions
- You need to find out why pages dropped out of Yandex search
- You need a Metrika traffic report or Direct spend report
Not a fit when
- You need Direct strictly read-only with no risk of changing campaigns
- You cannot install Bun and run servers from source
Example request
Show the Wordstat trend for «горящие туры» over two years and the regions with the highest interestLimitations
Packages are not published to npm yet, so servers run from a clone and need Node.js 22 and Bun. The author warns that unscoped npm packages with the same names belong to another publisher and must not be run with Yandex tokens. Search and Wordstat need a Yandex Cloud service account API key and folder ID; Webmaster, Metrika and Direct use OAuth tokens. Direct writes hit the live account with no dry-run; a sandbox is available for experiments.
How to disable. Remove the plugin with /plugin uninstall yandex-mcp@stufently or delete the server entries from your MCP config.
Security check
- Direct tools change live ad campaigns and bids, affecting ad spend
- Uses OAuth tokens with write access to Metrika, Webmaster and Direct
README in short
The README lists five packages and two install paths: a Claude Code plugin and running from source with a ready .mcp.json. It covers the OAuth flow for Webmaster and Metrika and how to mint a read-only Metrika token. It includes config examples for Claude Desktop, Cursor and other stdio clients, an environment variable table and sample prompts per server. MIT licensed.
FAQ
Can I install only Wordstat?
Yes. Servers without their variables fail on first use while the rest keep working. You can also add a single server by hand with claude mcp add.
Is Direct protected from accidental deletes?
Delete, update and bid tools require confirm: true. Adding, archiving and suspending run immediately because they can be reverted.
Related
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents
A CLI and agent skill for website SEO audits: technical SEO, Core Web Vitals, structured data, security and AI search readiness
A marketplace of 22 Claude Code plugins: Yandex Direct, Metrika, Webmaster, Wordstat, SEO crawling, publishing and research
Five MCP servers for Wordstat, Search, Webmaster, Metrica and Direct, plus a Claude Code plugin with keyword and competitor skills