yandex-mcp
Related Servers
Alternatives to yandex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to work with Yandex Webmaster, Direct, and Metrika data through natural language, including managing sites, sitemaps, recrawls, ad campaigns with write-safety guards, and pulling traffic, conversion, and ad statistics.MIT
- AlicenseBqualityBmaintenanceEnables AI agents to access Yandex Wordstat keyword research, trend dynamics, and regional analytics through typed read-only tools with strict schemas and safety controls.598 npmMIT

marketscore-seo-mcpofficial
AlicenseNot gradedqualityDmaintenanceConnects AI assistants to SEO data from Yandex Webmaster, Google Search Console, Yandex Metrica, and Topvisor, enabling natural language analysis of search performance, indexation, positions, and audits.MIT- AlicenseBqualityBmaintenanceEnables SEO and AI-search visibility analysis for Russian websites through Yandex APIs, including keyword research from Wordstat, live SERP results, position tracking with history, technical audits, content briefs, and checks of AI search citations.222MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to read Yandex Direct statistics and manage campaigns, ad groups, ads, keywords, bids, and other account settings locally on a single-user Windows PC.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query and fuse free SEO data from Google Search Console, Yandex Webmaster/Metrika, Bing/IndexNow, CrUX and PageSpeed Insights alongside its own site crawl, exposing read-only tools for search analytics, indexing triage, opportunity finding and weekly reporting. Supports scheduled email/Telegram delivery and CLI/skill surfaces over a shared SQLite history with explicit data-age and limitation metadata.2,280 PyPIApache 2.0
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose, helped by service prefixes (metrika_, webmaster_, direct_, wordstat_, yandex_). Within each service, the operations are well separated, such as summary vs. custom report vs. period comparison vs. counter listing. No overlapping tools cause meaningful misselection risk.
All tool names use consistent snake_case with a predictable service prefix followed by a noun or action. The pattern is clear across Metrika, Webmaster, Direct, Wordstat, and auth tools. There are no mixed conventions or vague naming styles.
The 15 tools are well-scoped for a multi-service Yandex integration, with only a few focused tools per service. Each tool appears to earn its place without excessive surface area. This falls comfortably in the appropriate range.
The server covers core read/analytics workflows across Metrika, Webmaster, Direct, Wordstat, and authentication, including one mutation for Webmaster recrawl. Minor gaps exist, such as Direct campaign management and possible auth token refresh/revoke operations, but the main agent workflows are covered.