Skip to main content
Glama
nikolaymokh-dev

yandex-business-mcp

by nikolaymokh-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to yandex-business-mcp

No user-submitted related servers found.

    Related Servers

    • kurerok-yandex-webmaster-mcp

      shutovdef-dotcom
      A
      license
      A
      quality
      D
      maintenance
      Local-first MCP server for Yandex Webmaster that exposes tools for SEO operations including search query analytics, sitemap management, indexing history, recrawl quota, and diagnostics.
      15
      MIT

    • yadirect-mcp

      Lermont
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that connects Yandex Direct advertising reports and safe campaign creation to AI agents, enabling natural-language analytics and protected campaign setup.
      8
      2
      MIT

    • yandex-market-mcp-ru

      ilyautov
      A
      license
      A
      quality
      A
      maintenance
      Yandex Market Partner API in your AI assistant: orders and returns, products and cards, prices and tariffs, reports, reviews and chats. 165 methods live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.
      26
      49 PyPI
      2
      MIT

    • Yandex Merchants MCP

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.
      13
      55 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct resources/actions (list/get/update/add branch, validate, diff, build), so an agent can usually choose correctly. The main ambiguity is ybiz_import_export, whose name suggests bidirectional import/export but whose description only documents importing an XML dump and saving a baseline. ybiz_status and ybiz_validate are related but clearly separated as summary vs actual validation.

    Naming Consistency4/5

    All names share the ybiz_ prefix and use snake_case, with clear verb_noun forms for the CRUD operations (list_branches, get_branch, update_branch, add_branch). The pattern is broken slightly by single-word nouns/verbs like status, validate, diff, and the compound import_export, but these still fit the tool's purpose and remain readable.

    Tool Count5/5

    Nine tools cover the full feed-management workflow without redundancy: inspection, branch CRUD, baseline import, validation, diff preview, and feed build. The count is well-scoped for the stated purpose and every tool earns a place.

    Completeness4/5

    The toolset covers the main lifecycle: read/add/update branches, validate, preview changes, and build the feed. There is no explicit delete-branch operation, but removal is indirectly handled through the diff/build flow with allow_close; updating network-level configuration is also not exposed, though it appears to be outside the feed-editing domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources