Skip to main content
Glama
aryazansev

Yandex Delivery MCP

by aryazansev

Related Servers

Alternatives to Yandex Delivery MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Delivery B2B API, enabling natural language interaction to calculate delivery costs, create and manage express and platform delivery orders, track couriers, and handle pickup points.
      16
      71 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for the Yango Delivery B2B API, enabling price estimation, express-courier claim creation and confirmation, courier tracking, and recipient tracking links through natural language.
      13
      81 npm
      MIT
    • 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
      70 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Yandex Tracker API, enabling AI assistants to search, read, create, and edit issues, as well as manage comments, attachments, and links in Yandex Tracker.
      22 npm
      1
      MIT

    TDQS

    D1.8/5.0

    Scored across 21 tools

    Disambiguation3/5

    The tool set has several overlapping retrieval functions (e.g., get_claim_info, search_claims, get_bulk_info, get_claim_journal) and similar pricing tools (calculate_offers, check_price), which could confuse an agent without detailed descriptions. However, most tools are distinct actions on distinct resources.

    Naming Consistency4/5

    All tool names use snake_case and follow a verb_noun pattern (get_tracking_links, create_claim, accept_claim, etc.), which is consistent and readable. The only minor inconsistency is mixing singular and plural nouns (claim vs. claims, info vs. journal).

    Tool Count4/5

    With 21 tools, the server is slightly over the typical comfortable range but still reasonable for a comprehensive delivery management API covering claims, tracking, pricing, and delivery methods. Each tool appears to serve a distinct purpose, so the count is justified.

    Completeness4/5

    The tool surface covers the full claim lifecycle (create, edit, accept, cancel, return, search) and includes tracking, pricing, and delivery method operations, leaving few obvious gaps. Minor missing features like a dedicated 'delete' action are likely covered by cancel/return, so agents can achieve core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues