Skip to main content
Glama
nozikov

yandex-mcp

by nozikov

Related Servers

Alternatives to yandex-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects 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
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      22
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      7
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables pulling Yandex Webmaster data into Claude, including backlinks, queries, indexing, diagnostics, and CSV export, so users can analyze SEO metrics without paid tools.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to retrieve comprehensive analytics data from Yandex Metrika accounts, including traffic, content, e-commerce, and user demographics.
      64 npm
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues